AIR
Proof Lab
StartEcosystem
Explore (579)Live Systems (52)Pricing
Log InGet API Key✓ Verify It Yourself

Independent Replay · Tokenize the World

Reconstructable token state, verifiable offline. It does not score software or controls maturity against a rubric — that is HICS.

Definition

Replay is the independent reconstruction and re-verification of what an agent did: it rebuilds the agent's entire view of the world at the moment it acted — what it saw, what authority it had, what policies were in force — from the signed bundle, then re-checks it offline and renders a verdict, trusting no one. Replay is a supporting expression of Verification, which renders the independent verdict on an artifact.

Why this exists: institutional truth should not depend on a surviving vendor. The verifier runs locally so that, years later with no operator in the room, any party can reconstruct the decision from the receipt and re-verify it.

Replay does not produce the evidence it replays — that is H33-74, which produces the signed record. It does not record or monitor (HATS), and it does not govern the decision (Agent-008). A passing replay means the run reproduces and validates against the signed record — not that the underlying decision was correct, secure, or compliant.

Note: the interactive scene below runs a real local WASM verifier against a fixture bundle; the specific names, amounts and timestamps it shows are an illustrative scenario, not a live production transaction.

Scene 2 of 2 · Independent Replay
waiting · awaiting reconstruction
Independent Replay

A $50M tokenized treasury transfer happened at Acme Treasury Fund. Production logs say everything is fine.

You’re about to watch an independent verifier — running in your browser, with nothing from us — reconstruct what actually happened. The cast:

Carolhuman · treasury approver
Agent ZEROautonomous AI · FHE compliance review
Dianaautomation · transfer agent
Bobinstitutional investor
bundletokenize-the-world-fraud-bundle-v0.2.json
size
SHA3-256
verifierh33-replay-verify v0.4.0 · WASM
networkzero calls after page load
one button · no keyboard input required
↻ replay this scene
When to use replay
Use it when

A third party must confirm on whose authority a tokenized-asset action was taken, and what the agent saw, without trusting the operator — audit, dispute, regulatory review, or long-horizon adjudication after the counterparties are gone.

Do not use it to

Decide whether an action should have been allowed (governance, Agent-008), produce the record (H33-74), or monitor the environment (HATS).

Boundary

A passing replay means the run reproduces and validates against the signed bundle — not that the decision was correct. In this scene replay renders a FAIL because authority was revoked before the action: replay reports what happened, whether or not it was authorized.

The questions replay answers
What is replay here?

Independent reconstruction plus re-verification that renders a verdict: it rebuilds what happened from the signed bundle and re-checks it offline, trusting no one. A supporting expression of Verification.

What does it not do?

It does not PRODUCE the evidence being replayed (H33-74), record or monitor (HATS), or govern the decision (Agent-008).

How is it different from H33-74?

H33-74 PRODUCES the signed record when the agent acts. Replay / Verification RE-CHECKS that record afterward and renders the verdict. One writes the evidence; the other independently reads and validates it.

What does a passing replay mean — and not mean?

It means the run REPRODUCES from the signed bundle and VALIDATES against it. It does not mean the underlying decision was correct, secure, or compliant — that judgment is governance (Agent-008).

When should I use it?

When a third party must confirm exactly what a tokenized-asset decision saw and on whose authority it acted — without trusting the operator, even after every counterparty is gone.