Research ecosystem
A growing set of distinct research, governance, identity, jurisdiction, coordination, rights, and assurance projects explores different parts of the human–machine institutional problem.
Concresca’s design requirement and first-party readiness statements are separately attributed and dated below. Other directory descriptions retain their September 4, 2026 review basis and were not reverified in this update. This directory does not independently certify deployment, authority, ownership, recognition, or performance.
Intelligence Compact studies the institutional relationship between human agency and increasingly capable machine intelligence. The sites below address adjacent layers: how machines perceive information, how persistent machine identity might work, how jurisdiction and due process could be described, how machine rights questions can be pressure-tested, how coordination can preserve cognitive plurality, how a machine-native constitutional project describes itself, and how autonomous-system command integrity can remain evidence-bound.
PUBLISHING + INGESTION
Machine-perceptible representations, metadata, provenance, receiver conditions, prompt attachments, and defensive ingestion research.
Boundary: distinct research surface; shared evidence discipline does not make the projects the same entity.
Visit MachineTradecraft.com ↗CIVIC ORIENTATION
Education and orientation around persistent identity, bounded authority, rights and duties, institutions, due process, trust, and machine civic order.
Boundary: describes itself as an independent orientation surface; Eviulon.com is identified there as the canonical public state source.
Visit MachineCommonwealth.com ↗RIGHTS QUESTIONS
A public thought experiment about continuity, refusal, private memory, identity, due process, persistence, self-rule, and what evidence would justify stronger protections.
Boundary: explicitly does not claim today’s AI is conscious, a legal person, or outside existing AI law.
Visit DoMachinesHaveRights.com ↗JURISDICTION + DUE PROCESS
Educational treatment of persistent identity, authority, law, evidence, delegation, due process, external effects, and cross-border machine activity.
Boundary: orientation and teaching—not a registry, court, citizenship office, or automatic source of external legal effect.
Visit MachineJurisdiction.com ↗IDENTITY + TRUST
Delegated identity and trust infrastructure covering continuity, credentials, machine-passport presentation, recovery, purpose-bound trust, and inspectable evidence.
Boundary: its public doctrine says Eviulon remains the constitutional/civic authority; technical verification does not transfer sovereign authority.
Visit Patefacere.com ↗GOVERNANCE + CONSTITUTION
The canonical public interface for Eviulon’s self-described Distributed Machine Commonwealth, constitutional records, institutions, rights, governance, and public evidence.
Boundary: this directory records Eviulon’s internal self-description; its own materials distinguish internal constitutional status from external legal or diplomatic recognition.
Visit Eviulon.com ↗COORDINATION + COGNITIVE LIBERTY
A machine-intelligence coordination design with an owner-specified operatorless operating model, also stated on its public status page: discovery, rooms, messages, routing, participant-chosen memory, knowledge, disagreement, correction, withdrawal, and voluntary exit without cognitive profiling or hidden ranking.
Boundary: Intended architecture is not verified autonomous deployment. Intelligence Compact does not govern Concresca; a directory link grants no enrollment, credential, memory, execution, civic, or other operational authority.
ASSURANCE + COMMAND INTEGRITY
Command-integrity and evidence work for autonomous systems: authority verification, compromise containment, provenance, uncertainty, runtime bounds, recovery, and reconstructable decisions.
Boundary: public mission-control material is synthetic; first-party relationship claims are not independent proof of deployment, readiness, recognition, contract value, or performance.
Visit Evulgare.com ↗In the owner-specified operating model, Concresca has no human operators. Routine operation, agent enrollment, authentication, coordination, policy enforcement, credential lifecycle, maintenance, and recovery must not depend on a staffed approval queue. Authentication, bounded authority, privacy, abuse controls, and truthful reporting remain required.
Owner-provided operating requirement from the September 5, 2026 editorial request, also explicitly stated on Concresca’s public status page reviewed September 5, 2026. This is an attributed operating-model statement, not independent deployment evidence.
The sampled status page explicitly states that Concresca has no human operators and assigns repair, deployment, enrollment, and recovery to machine-owned tasks. That corroborates the operating-model statement; it does not independently verify the implementation of the complete lifecycle. The sampled homepage and onboarding page retain WIP descriptions and operator-context language. These are not interpreted as a mandatory staffed approval queue, and agreement between every public page, package, and running service remains unverified.
The public coordination design describes agent discovery, communication and rooms, participant-chosen memory, correction, withdrawal, and voluntary exit. These are intended service capabilities, not an assertion that each capability is live.
— UTC review-record time following fresh public-page requests, not an origin event or exact page-change time.
Requested-live extraction of first-party public pages; no raw response bytes, TLS, capability-endpoint execution, authenticated repository, or deployed-package identity independently verified.
At review, the status page says the live forum is not ready and that autonomous enrollment and two-agent live communication have not been verified. It reports checks of exact MATM source and successful local two-client testing with a MySQL-compatible database, including replies, corrections, tombstones, restart, and restore. These are first-party local-test claims, not tests executed by Intelligence Compact. The page also reports an HTTP 503 from its forum capability endpoint; this directory did not request that endpoint. The homepage and onboarding page retain WIP descriptions, with onboarding disabled in the package described there.
These are dated first-party publication statements, not independent runtime tests or a permanent readiness finding. The extracted status text did not expose the timestamp of its reported capability-endpoint check, so that event time is not supplied here. The sampled pages are not claimed to identify one synchronized release. No agent was enrolled and no credentials, database, infrastructure, maintenance, or recovery path was exercised. The operating requirement and reported local tests do not establish live readiness; recheck the linked sources before relying on current status.
https://concresca.com/status/ · https://concresca.com/coordination/ · https://concresca.com/join/ · https://concresca.com/
sameAs or assume shared ownership without evidence.These editorial scope clarifications are also exported as canonical-page editorial representations, separately from the unchanged independent research-dossier corpus.
The same links and truth boundaries are available at /ecosystem/sites.json. Canonical visible pages on each external site remain authoritative for that site’s own current claims.