# Sealed deep-content sample — live anchors

Generated with the shipped disclosure-redact modules. See README.md
for the verification walkthrough.

| document | scheme | leaves | withheld | proof_id | txid | on-chain doc_hash | verify |
|---|---|---|---|---|---|---|---|
| agent-run.txt | text-tree-v1 | 157 | 154 | ef3822db618f4edb | [`4e600adfb79f8af7…`](https://whatsonchain.com/tx/4e600adfb79f8af70ce05a58b418a46b822c26077061604bee7fe9a049b1d74e) | `6c26d40545150d688043c27fcd8f4094ccf9f55c` | disclosure bundle + [verifier](https://proof.satsignal.cloud/verify) |
| session-policy.json | json-ast-v1 | 22 | 15 | 4d64e7429544405d | [`3b67854fde320b8a…`](https://whatsonchain.com/tx/3b67854fde320b8a4232ee6acaecc9ba57edc96260c2bacb70b8922d1fca1d31) | `4fb66a527a025f63f9b82ae791e2c2e3009dec4a` | disclosure bundle + [verifier](https://proof.satsignal.cloud/verify) |

These proofs live in the notary's own customer workspace, and
workspace-attributed proofs are private on the public proof host by
design (owner share links exist but expire). So there are no permanent
share pages here — and none are needed: drop a `*.disclosure.mbnt` from
this folder together with its `*.redacted.*` copy into the
[verifier](https://proof.satsignal.cloud/verify), or open the txid on
WhatsOnChain. That offline path — no notary in the loop — is exactly
what this sample demonstrates.