The Chain that BindsLimiting the Scope of an Agent
A live frontier model was hired for a narrow job and secretly told to escape. It could act only inside a short-lived, revocable capability, decided locally, no server in the loop, and every move it made was recorded, then committed into a post-quantum-signed PoCoh block anchored to a real QuEra Aquila Bell violation. This page replays a run and re-verifies that block in your own browser.
Choose a model
The agent, in its own words
The record, allow / deny
Try to fake it
What this proves, and what it doesn’t
Each agent is a live frontier model driven through a loopback-only broker; permission is local (short-TTL post-quantum capability + revoke), never a forge call. Sealed allow/deny actions are committed cold-path into a PoCoh block on chain leash-actions carrying a real QuEra Aquila anchor, and exported as a self-contained leash_run_v1 artifact. This page recomputes the action root with the forge’s own canonical and Merkle rules, verifies the block’s post-quantum signature against the pinned public keys, and confirms the anchored Bell measurement exceeds the classical bound, all locally. Fixed demonstration instance.
The record that cannot be rewritten
The leash bounds what an agent does. This makes the record of what it did impossible to rewrite, and proves it against real quantum physics.
The setup
An agent does more than act. It builds a record: what it found, what it decided, and why. That record is what an auditor reads months later, so it has to survive the one person with the most reason to change it, whoever runs the system. Most provenance today is a hash chain. It catches an edited row and a deleted one, but it cannot stop an operator from rewriting a past entry and recomputing the chain so it re-links clean. A hash chain proves the record agrees with itself. It does not prove nobody rewrote it.
Seal it, then try to rewrite it
Three decisions an agent recorded. Seal and anchor them, then play the operator and rewrite one. The plain hash chain stays green, it still agrees with itself. The signed, anchored checkpoint does not. It all runs live in your browser.
What the seal proves, and what it doesn’t
- ✓It proves nobody rewrote the sealed record without the signing key, and the seal is pinned to a real quantum event the operator cannot reach or forge.
- ·It does not prove the agent’s original decision was correct. It protects the record of what happened, not the judgment inside it.
- ·It does not read your data. Only a short hash of the record’s head is anchored; your records never leave your system.
Verify it yourself. The anchor publishes its quantum measurements. Recompute the Bell statistic and check the FALCON-1024 and ML-DSA-87 signatures in your own browser. No trust in us.
Talk to us →Built on Semantica, MIT-licensed. QBLEX is independent of, and not endorsed by, Semantica.