AINumbers.co · level 4 · real run

Ten live runs sealed under one timestamp

On 26 September 2026 one agent session made ten runs against the public AINumbers surfaces with synthetic inputs. Every hash, verdict, time and serial number on this page comes from that session and can be checked today.

Goal of this animation

Show a realistic agent session end to end. Three kinds of work run on different machines, a refusal and an escalation are recorded alongside the passes, and only hashes travel to the session receipt. Outside timestamp authorities then fix when that receipt existed.

🔒 No personal dataAll inputs in the session were synthetic, and the mandate was signed with a throwaway key. The EMIR trade fields stayed in the browser, and only hashes reached the session receipt.
☁ Our server is Cloudflare“AINumbers server” means Cloudflare today. The MCP worker and the anchor service run behind Cloudflare, and the timestamp authorities are independent of us.
What the red and amber results mean
● green · the check passed and the step may go ahead● amber · held, flagged for review or waiting on something● red · refused, or a mismatch was caught
PASS · leaves 1 and 3Each authorization was checked on the chain it was signed for, so the digest, the signer and the domain all agree. Leaf 5 ran all four conformance steps under the mandate.
REFUSE · leaf 2A deliberate replay test, and the check working as designed. The authorization was signed for USDC on Base (chainId 8453). The test presented the same signature for Ethereum mainnet (chainId 1, a different USDC contract). EIP-712 bakes the chain and the token contract into what gets signed, so art-592 refuses on both mismatches. A thief who copies a payment signature from one chain cannot spend it on another.
ESCALATED · leaf 6Also deliberate. The supervised-autonomy workflow is built to stop and hand the case to a person when its risk check (art-67) calls for it. The run halted there, skipped the last step and opened a record that only a signed human decision can close.
NOTHING TOUCHED A BLOCKCHAINAll three x402 runs check a signed payment authorization offline. The kernels make zero network calls, query no chain and submit no transaction, so no funds moved on Base or Ethereum. The inputs were synthetic, and the Work Mandate was signed with a throwaway key.
0/10runs
0refusals and stops
0inputs sent to the receipt
0/3timestamps
0.0s

Start the walkthrough

The ten leaves in order

#RunResultHash

Session receipt root 7bc2980bc7d8a719166804e9bd9e553f767d9dd2fd3f96c1ac9b14cbd669c26b, 10 leaves. The internal Merkle nodes are not shown.

Check it yourself

Download the receipt and the three timestamp tokens from step 18 of the Agent Staircase explainer. Decode a token to a .tsr file and run:

openssl ts -verify -in digicert.tsr -digest 7bc2980bc7d8a719166804e9bd9e553f767d9dd2fd3f96c1ac9b14cbd669c26b -CAfile <that authority's root>

Or call verify_anchor_binding on the anchor server, or rebuild the root from the ten hashes with build_session_receipt. The ledger at ledger.ainumbers.co replays hashes, signatures and gate decisions inside your browser.

Source: the Agent Staircase explainer on ainumbers.co, live run of 26 September 2026 (UTC). Estate figures are for that day. Verdict words are shown only where the source records them, so the four EMIR checks show their hashes alone. The animation compresses time.

←→ back and next · Space play or pause · R restart · level 3: seven workflows · all explainers