Hash-anchored documents, a daily attestation ceremony, and a swappable discipline contract. Built on the Garrison Node architecture. A library of walkthrough simulations shows what it looks like when records become defensible by mathematics instead of by testimony — and lets you walk one in three to forty-five minutes.
Each cluster carries three to six sims sharing audience, tone, and four-paths install order. All sims play in your browser. No install required.
Two ideas, no jargon.
A merkle tree is a way of fingerprinting a folder. You compute a short hash for each file, then a hash of those hashes, then a hash of those, until one short string at the top represents the whole folder. Change one byte anywhere and that top string changes. Bitcoin uses the same trick to fingerprint blocks of transactions. We use it to fingerprint a folder of documentation. The math is public; you do not need a coin or a network fee to use it.
An LLM (large language model) is the kind of AI you interact with through chat — Claude, ChatGPT, and the local models you can run on your own machine like Ollama or BitNet. LLMs are useful but they make things up. They do better when they are reading documents they can trust. So we hash the documents and let the model verify the hashes before it reasons from them. Trust, but verify.
Put together: a folder of documents whose contents are fingerprinted, where any tampering is caught the next morning, and where the AI you ask questions of can prove which version of which document it just read. That is the entire architecture in two sentences.
The system is not autonomous. A daily ceremony walks every file, recomputes the fingerprints, compares them to yesterday's, and publishes a one-line receipt. When something drifts, the ceremony flags it — and a human-in-the-loop (you, or someone you designate) reads the flag and decides whether the change was intentional or not. The bot does the math. You make the judgment call. It is teamwork by design, not autopilot.
Inspired by DeAngelo's YouTube series on the million killer apps for blockchain. The framing is theirs; the substrate is ours; the killer app is yours. Crediting the inspiration, not claiming an endorsement. The builder card (41) walks the contribution flow. The operator card (42) walks the clone-and-join flow.
Walk a sim → if you are evaluating whether this is real. Build → if you've walked some sims and want to author your own. Operate → if you've decided to host a node and join the mesh.