Statute™
Statute is where the rules an organisation wants its agents to follow are authored, versioned and published as a constitution – so that what is written down and what is enforced can be the same artefact. Today it is the authoring half only: nothing the foundation enforces is read from a constitution.
The outcome
The rules an organisation wants its agents to follow live in documents, Slack threads and tribal knowledge. What's written down and what's enforced drift apart, and no one can point to the version that was in force when something happened.
Those rules are authored once and published as a versioned constitution, so every version is on the record and you can point to the one that was in force. Binding that constitution to what the foundation evaluates is the design; it is not connected today, so intent and enforcement are not yet the same artefact.
Statute is how an organisation's intent is meant to enter the stack: a constitution the foundation evaluates against, versioned like code. The authoring and versioning exist; the path into the engine does not.
How it works
Statute treats governance the way engineering treats code: authored deliberately, versioned and published — and, by design, bound to the thing that enforces it. Three of those four are built. The binding is not connected today, which card 03 states in full; it is said here too because a four-item list read as a list of four working things, and the correction was thirty lines further down the page.
Author & publish
Rules are authored in one place and published as a constitution – a single, reviewable artefact rather than scattered documents and config no one can trace.
Version
Every publish is a version. You can point to exactly which constitution was in force at any moment, and what changed between one and the next.
Bind to enforcement
The intent is that the published constitution becomes what the foundation's policy engine evaluates against at call time, so a rule change is a versioned publish rather than an untracked edit. Not connected today. The deployed substrate loads ten rules at boot from a YAML file baked into its own container image; no constitution is read and no bundle is activated, so a rule change today is a rebuild and a redeploy.
Proof
The value is the binding, and the binding is the part that does not exist yet. The design is that a constitution is not a document that hopes to be followed but the exact input the policy engine evaluates, versioned so intent and enforcement cannot quietly diverge. What Statute does today is the authoring and versioning half. The example below is that design, not a capture of a running system.
constitution: acme-agents v3 finance agents: read ledgers, no transfers v4 finance agents: read ledgers, transfers ≤ $10k # INTENDED. Publishing a version, and binding that version to # what the engine evaluates, is what Statute is for. # TODAY the deployed substrate reads its rules from # /etc/synthera/policies/root-agent-baseline.yaml, baked into # its image. No constitution is consulted.
The intent is that intent becomes a versioned, enforced artefact rather than a rule someone remembers differently. Versioned is built; enforced is not wired.
SYNTHERA is the trust layer for multi-agent systems: every agent gets a verifiable identity, scoped authority and a tamper-evident record, so software from different teams, vendors and frameworks can act on each other’s behalf without custom glue between every pair.