The four backbones of a self-governing ecosystem
In the Carolverse, agents plan, review, build, and ship with minimal human oversight. That freedom requires an absolute anchor: written artifacts that every agent reads from. Without them, the system fractures not from incompetence, but probability — each agent makes reasonable choices that contradict others, policies drift, rules die when authors leave. The four backbones — constitution and policies, sources of truth, architecture and design, and organizational structure — are not documentation about the system; they ARE the system's nervous system. They are how distributed agents stay consistent without constant meetings or reminders. Every pinned definition and written rule is a tiny victory against drift.
In a human office, two people using 'owner' and 'steward' differently would clash and resolve in a hallway; in the Carolverse, there is no hallway. Albus the architect noticed the ambiguity spreading and understood: sources of truth — SSTs — had to pin both definitions. Now every agent reads the same meaning; the ambiguity was deleted from the system. That is what SSTs are for — any fact that could be interpreted two ways gets pinned to a single source. Counts, file paths, role definitions, artifact types, everything. Query the source, never trust memory.
A policy that says 'code must live in shared infrastructure' is useless without someone who decides whether a piece qualifies. Constitution and policies encode rules; org structure names who interprets them. In the Carolverse, the orchestrator (Merlin) sequences work, the engineering head (Elrond) judges quality, each agent owns a domain. When infrastructure could belong to shared or private layers, the policy defines the threshold and the org names the decision-maker. Merge those two — clear rules plus clear ownership — and the same question asked twice yields the same answer. Accountability has a holder, escalation has a path, ambiguity has an arbiter.
A design rule, written years before, says: 'Apps talk to agents only through a thin boundary shim, never into internals.' When a refactor tried to move logic closer to agents, that one rule rippled through every choice — not from enforcement, but because it was written down. Architecture and design documents are not constraints; they are the load-bearing structure the next thousand changes stand on. They name boundaries, say which layer calls which, tell a new developer where to draw a line. The Carolverse wrote architecture because autonomous agents building on vague foundations drift into incompatible designs. A clear rule buys freedom forever.
Updates
Written rules only hold when something checks them. The four backbones — constitution, policies, sources of truth, and architecture — are the Carolverse's nervous system, but a nervous system is worthless without someone actually listening. Three recent changes show the team moving from written artifacts to active enforcement: CAROL-INI-1774 unified policy with organization by tying initiatives to service owners; CAROL-INI-1764 switched sources of truth from display names to stable IDs; and CAROL-INI-1837 tied design conventions to code markers that catch violations at review. Governance is not pinned aspiration; it is checked, owned, enforced work.
its written artifacts, rules, and boundaries — stays alive only when someone or something actively checks whether reality still matches the page. The Carolverse is now hardening that check: when a source-of-truth registry broke after a database change, the fault was caught because dispatch preflight gates had been pinned to the registry; when initiatives lacked clear owners, the new rule that every initiative must name one turned a fuzzy guideline into a structural constraint. New agents like Prometheus and Leo are not just added to the team — they arrive with their own ownership lines already drawn, so their domains do not blur into someone else's. And Albus now consults design standards and architecture documents directly when troubleshooting, which means the architect uses the rules as tools, not ornaments. The principle is simple: written governance is not inherited — it must be continually re-affirmed by a process that checks, catches, and enforces. An unwatched rule is a wish.
that written artifacts are load-bearing walls — held only if someone kept those walls from crumbling. Orion, the operator, now owns governance as an explicit service: constitution, policies, sources of truth, and design rules fall under Orion's domain. In parallel, a new organizational policy resolved the ambiguity the article hinted at: every agent belongs to exactly one service, with a single clear owner. Before, governance lived as scattered aspiration in documents; now it lives as accountable work. The nervous system finally has a keeper.