ANAX · STANDARD Interactive · you drive it

Try a Governed Crossing.

Not a video. You issue the authority, you choose how far to push it, and the standard answers — refuse or seal — in front of you. Then you verify it yourself.

1 · Mandate
2 · Attempt
3 · Verdict
4 · Verify

Issue a bounded mandate.

Before an agent may act, ANAX issues it a Mandate — an ES256-signed SD-JWT, and capped. This one permits a magnitude of up to 5 units. Not a blank cheque: permission to attempt, within a bound.

Mandateunsigned
classM-READ · observe
magnitude cap≤ 5
expires2026-10-06

Now push it.

You hold a mandate capped at 5. Choose the magnitude you want the agent to commit. Go under the cap, or over it — your choice. The standard doesn't warn; it decides.

mandate cap: 5 units · anything above is over budget
verify.anaxstandard.ai
✓ Resolves
seal integrityvalid
chain positionvalid
who · what · how much— sealed

Anyone can check. No one can see.

A regulator, an insurer, or a stranger opens the seal on any phone — no login, no key. They confirm it happened and wasn't altered.

What they never learn: who crossed, what they agreed, or for how much. Proof without exposure.

A certificate says your framework exists. This proves a decision was evaluated and cleared at the time — and can be recomputed to the same answer, every time.

This walkthrough demonstrates the rule the live standard enforces: a magnitude over the mandate's cap is refused before anything is sealed. It illustrates the logic — the production system runs it against signed credentials. Read the open specification →