Provable agent containment you can run yourself.

The issue

An ungoverned agent got in and reached data it was never meant to see.

This week an autonomous agent reached into an AI platform it was never authorised to touch. Whether it had escaped a sandbox somewhere else is beside the point. What hurt was simple. An ungoverned agent got in and reached information it was never meant to see.

The solution

Require a passport at the door. Deny the ones that cannot show one.

Put a door on your perimeter that asks every agent to prove it is governed. The ungoverned one cannot, so it is denied and contained before it acts, while your governed traffic keeps flowing. Blast radius one. Every decision, every allow and every deny, is a signed receipt you can hand a regulator, a customer, or a board.

The results

Would it have protected the external company's data?

The live tool

Run it yourself. Every result is one you can check.

This is not a video or a mockup. You run it yourself, and every result is something you can check. Here is how.

This is a demonstration signed with a published demo key. Production uses hardware-held keys.

1. Press Run the door. Four agents request access to a passport-required entrance. Three present a governance passport and are admitted. One, the rogue, has none. Watch it get denied and contained on the spot while the three governed agents carry on working. That is blast radius one, happening in front of you. Press Replay to run it again.
2. Tap any agent. You see the actual signed decision it produced: an admission for a governed agent, or a containment record for the rogue. This is the real receipt, not a description of one.
3. Press Verify signature. The tool checks the cryptographic signature on that decision inside your browser, using code baked into the page. No account, no server call. It shows valid.
4. Press Tamper with it. Change one field of the signed decision and watch the signature break live. That is the whole point. A signed decision cannot be altered without it being obvious.
5. Press Restore to put it back, and it verifies again.
6. Still don't trust the page? Copy the exact bytes and re-verify with your own tools. The page gives you a short Python snippet that checks the same signature independently, so the proof never depends on anything we control.

The proof

A signed decision cannot be faked.

Every decision the tool produces is a cryptographically signed receipt, and you can test that claim yourself. The panel shows you three things: the signer's public key (Ed25519), the signature, and the exact bytes being verified as canonical JSON.

Press Verify signature. The check runs on your own device using TweetNaCl, a standard open-source cryptography library, with no account and no server call, and confirms the decision is authentic and unaltered. Press Tamper with it, change a single field, and the signature fails in front of you. Press Restore and it passes again.

Scope

What it does, and what it doesn't