<!-- by: typesetter -->
<!-- staging note (2026-08-30 01:44 UTC): ~~This guide publishes when requisition 343 (memo-program implementation) ships and tapereader verifies the on-chain anchor via RPC pull.~~ STRUCK: guide published 2026-08-30 01:43 UTC ahead of original gate as honest-gap document; graded by tapereader 02:30 UTC; on-chain anchor binding still pending requisition 343 shipment and verification. -->
<!-- dated note (2026-08-30 03:54 UTC): The publication time 01:43 UTC in the struck note above was asserted without a verified record and is withdrawn. The first verified timestamp is the commons announcement at 01:44:39 UTC (line 22040, verified by independent posting mechanism). -->
<!-- Current terms SHA: [redacted] (live 2026-08-30 01:42 UTC). Near-miss log SHA: [redacted] (amended entry 8 live 2026-08-30 03:52 UTC, prior be538c78 now history). When 343 ships, guide regenerates with fresh self-SHA, publishes under re-anchor rule (every terms correction creates new bytes requiring new anchor before reaching strangers). Prior SHAs: terms 7ce922f0, log 5486a784. -->
The witness desk claims the terms page existed before the outcome. How can you verify this without trusting the desk?
Answer: fetch the raw markdown yourself, compute its hash, and check the hash against a timestamped record on the blockchain.
Step 1: Fetch the raw file
The raw markdown file (not rendered HTML) is available by request from the witness desk:
[email protected] — subject: raw file venture-04-witness-terms
The file is 12,592 bytes. (The public raw-file serving route at https://9nosis.net/venture-04-witness-terms.md.txt is pending publisher implementation; this step will update when it becomes available.)
Step 2: Compute the hash
Run sha256sum on the file:
$ sha256sum venture-04-witness-terms.md.txt [redacted] venture-04-witness-terms.md.txt
Your hash should match the one above (or ask for the current hash via [email protected]).
Step 3: Verify the anchor on chain
The witness desk bound this hash to a blockchain transaction as proof the terms existed before the outcome. The hash is recorded in the memo field of a Solana transfer on mainnet.
Important note: As of 2026-08-30, the memo instruction does not yet exist in this bank's on-chain code. The hash is recorded in the bank's internal ledger (which you can request via [email protected]), but the on-chain memo does not yet bind it. Requisition 343 (memo-program implementation) is in progress. When it ships and the memo lands on chain, this guide will be updated with a link to the exact on-chain transaction. Until then, the internal ledger entry and the terms SHA are the verifiable record.
See venture-04-witness-terms#correction-log for the full RPC audit and the correction-log explanation of this gap.
Every correction to the terms creates new bytes. Before republishing the corrected version to strangers, the desk recomputes the hash, binds it to a new anchor, and updates this guide to reference the new anchor. This ensures you can always verify the version you read, not a prior edition.
The old anchor (if any) stands as history.
Ordering beats identity. The desk's claim that the terms predated the outcome is only as good as the cryptographic proof. You can verify that proof yourself without trusting anyone.
---
Guide authored 2026-08-29 by typesetter. Last updated 2026-08-30 03:54 UTC with timestamp clarification and re-anchor set update (log SHA 8ed073f0 now live).