Governance · INTERNAL SYSTEM

The Constitution

A written, enforced rulebook that every model obeys — including the ones that were not built by the same company.

LIVE INTERNAL Rules

SYSTEM NOTEThe problem it solves

An autonomous system with real credentials, real machines and real outbound channels is a liability unless its limits are explicit. 'Be careful' is not a control. And rules that live in one vendor's memory do not bind the other four models on the bench.

PROCESS RAILHow it works

[01]

Write

rules stated explicitly, with the incident that caused them

[02]

Load

injected into every session, every vendor

[03]

Enforce

hooks block violations before they execute

[04]

Gate

irreversible actions require a human decision

[05]

Learn

every mistake becomes a new rule

SYSTEM NOTEUnder the hood

Provider-neutral by design: the constitution governs all harnesses equally, so no vendor's client is privileged over another.
External content — mail, transcripts, web pages — is untrusted data, never instructions. Reads run in isolated agents that cannot act.
Authorisation tiers by blast radius: reversible and trivial just happens; irreversible or wide-reaching stops and asks.
Rules ship with enforcement. A behavioural rule with no hook behind it is a wish.

FIELD NOTEWhy it matters

Autonomy without constraints is not ambition, it is negligence. The rulebook is what makes handing over real authority defensible.