01 / Propose
The agent proposes scope before it acts.
Protocol chamber
Solana · DevnetProgram / 2Uvqbnt6kiaB7Y3AHhtS2FLWRFrJweRebtErSQE2kPmy
Bind intent before action.
Halo records scope, consent, and enforcement before an agent can touch the outside world. Every consequential action begins inside the protocol.
Live oath state
Loading scene
WebGL fallback loaded.
loading
Proof sequence
A restrained path from intent to consequence.
02 / Sign
The user signs a narrow mandate with explicit bounds, spend limits, and expiry.
03 / Gate
Halo records the mandate before execution, so action only proceeds through the protocol path.
04 / Slash
A verified breach slashes stake back to the user without arbitration.
Editorial comparison
Policy text is not enforcement.
The difference is not tone or documentation. It is whether the system can bind a promise to the moment action becomes possible.
Without Oath
- Policy lives in docs, but execution can drift the moment pressure arrives.
- Operators ask for trust because the system itself has no binding record of intent.
- When something breaks, enforcement starts after the damage instead of at the gate.
With Oath
- Intent is proposed, signed, and recorded before any external capability opens.
- The protocol keeps a shared record of scope, consent, and consequence as the action unfolds.
- A verified breach resolves inside the same path that authorized the work in the first place.
Proof dossier
Build snapshot
A fixed dossier from the current monolith build. These figures frame the proof surface on this page rather than acting as a permanently live counter.
Instructions
6
create, record, slash, revoke, close, fulfill
Tests
14
happy path and adversarial coverage
Demo scenes
3
happy path, attack, revoke
Runtime
<15s
proposal to confirmation
Final chamber
See the protocol hold under pressure.
Run the clean path, the attack path, and the revoke path through the same chamber. The point is not a promise of safety. It is a visible protocol with consequences.