RECORDED TESTNET RUN · FIXED FICTIONAL MATERIAL
Approve the next brief, not the entire conversation
An outside assistant needs an event announcement. The approved date changes. The old brief stops working; the corrected brief needs its own grant. This is a read-only replay of two original browser exports—not a new wallet operation or live AI model.
Watch 69-second working verifier demoWatch 70-second project pitch
Two original exports, one testnet run
The page was reloaded after the V2 grant receipt was recovered. Part 1 records Friday delivery and old-version denial; part 2 records Saturday delivery and revocation denial. Five confirmed transaction receipts in part 2 bind both segments to the same asset. The original files are not merged or rewritten.
- Network
- Monad Testnet · 10143
- Registry
- verifying…
- Part 1 SHA-256
- verifying…
- Part 2 SHA-256
- verifying…
- Model boundary
- NOT_MEASURED · deterministic template
Five confirmed state transactions
Read-only chain check not started. This checks transaction inclusion and success, not Agent B's off-chain counters.
What this does—and does not—show
- Only one client-confirmed brief item reaches the independent local recipient in each successful request. The private planning note and unapproved suggestion are not in the recorded context or announcement.
- Denied requests record one chain check and zero new envelope fetch, decryption, context assembly or gateway calls. Previously received plaintext cannot be recalled.
- The same test wallet signed owner and request operations; the recipient ran in a separate local process. This is not real-model quality, production security, user value or cross-organization adoption.
Download original part 1 · Download original part 2 · Evidence boundary