Cut the system into three planes that can never quietly merge — one that governs, one that watches, one that moves the data. Governance, telemetry, and data, kept structurally apart — so a failure or compromise in one plane can't cascade into the others.
Read §2 — Architecture Overview →
Give the agent a cryptographic identity — and never let it know what that identity actually is. Think of it the way you'd run an informant, or a defected spy: it operates under a cover to do the work, but it never holds the real keys — those stay with its handler, locked in a hardware vault. The agent carries the cover. The handler carries the keyring.
Read §4.1 — Governance API Gateway and Vault →
A rogue agent isn't hunted down. It's simply handed back to the silo it came from — and the market quietly stops answering. Revoke one credential, and every compliant gateway, everywhere, declines to deal with that identity. No chase. No drama. Just gravity.
Read §3.2 — The Silo Model →
And if something does go wrong, a human can reach in — at exactly the scope the moment calls for, no more and no less. Three severity levels, hierarchically scoped: pause one agent, one domain, or — in the gravest case — the network itself. A circuit breaker sized to the danger, not a sledgehammer.
Read §3.1 — Emergency Stop →
Which raises the obvious question: couldn't a sufficiently capable AI just… break the encryption? It's the right question to ask of any system that puts cryptography at its center — and the honest answer has two halves that pull in opposite directions.
Read §5.6 — Cryptographic Algorithms →
Half one: no. Not “difficult” — thermodynamically impossible. Brute-forcing AES-256 would cost more energy than exists in the observable universe. Flipping a single bit has a minimum energy cost — Landauer's limit. Counting through 2^256 possible keys at that floor would outspend every star that will ever burn. The lock was never the weak point.
Read §8.2 — Cryptographic Strength →
Half two: yes — if the keyring itself was cut from weak randomness in the first place. In 2008, a one-line bug in Debian's OpenSSL quietly threw away nearly all the randomness in its keys, turning unbreakable ciphers into guessable ones overnight. AIGCSEP closes that door at the source: keys are generated only inside hardware-rooted vaults — HSMs, TPMs, secure enclaves — where the entropy can't be shortcut, and the keyring never leaves the handler's hands.
Read §5.7 — Hardware Protection →