This is a real resolution, not a mock. The SHA-256 below is computed in your browser with WebCrypto over the exact document bytes — the same check a relying party runs before trusting an agent. Tamper with the document and watch the chain fail closed.
Above, you resolved one document by hand. Here is the same discipline as a live pipeline: an intent enters at the left and is checked against a Cryptographic Power of Attorney at each gate. It reaches settlement only through an unbroken chain of passing checks — otherwise it terminates in a structured denial, with no advisory mode and no override. Pick a scenario and follow the packet.
Both the instrument and the pipeline above compute a real SHA-256 with crypto.subtle.digest('SHA-256', …) over the canonical document bytes. Toggle Tamper and the recomputed digest genuinely diverges — the reliance gate then refuses to bind, because the gateway is never trusted; the bytes are. The anchor, signature, and Arweave fetch are simulated for the demo; in production they read Tezos and Arweave directly.
The NFT could point anywhere and a gateway could serve anything. So the resolver re-hashes the fetched bytes and compares to the on-chain commitment. A wrong document fails at step 3, always.
Nothing is trusted transitively. Anchor confirms version; hash confirms bytes; signature confirms authorship; status confirms liveness. Break any link and the chain stops.
No score, no reputation, no balance to farm. The verdict is recomputed from scratch every time, from artifacts anyone can independently check — exactly what you just did.