You walked the sims. You read the architecture. You decided you are not a visitor anymore — you are an operator. This page is the bridge between the demo and the deployment. Card 42 is the sim that walks you across that line.
Card 42 is the operator's onramp. The first-day checklist, the cross-attestation handshake, the five floor commitments, what you take with you and what you give back to the commons. Walk it before you clone anything; it sets the expectation.
Half a Saturday. Half a Saturday is half a Saturday — bring coffee.
═══════════════════════════════════════════════
OPERATOR — FIRST DAY CHECKLIST
═══════════════════════════════════════════════
CLONE
git clone <substrate repo>
cd garrison-node
VERIFY THE CLONE
re-anchor the cloned tree against the
parent's published commit hash; confirm
the substrate you just cloned is the
substrate that was attested.
BUILD THE LOCAL RUSTCHAIN
cd rustchain-v2
cargo build --release
expect: deterministic replay tests pass
BOOT THE NODE
seven soul-chain files SHA-verified at
startup; the wrapper logs each as it
confirms. Any mismatch halts the boot.
CONFIGURE THE SILOS
each of 23 silos seats a personality JSON
you adopt or rewrite. Names can carry
over; identities are yours.
RUN THE FIRST CEREMONY
fifteen seconds, real SHA-256, real
merkle-leaf construction, real anchor to
BSV through rust-sv (or shadow-mode if
you are still in setup).
CROSS-ATTEST WITH THE PARENT
publish your daily anchor URL; pull the
parent's anchor URL; both nodes' mesh
registries record the handshake.
═══════════════════════════════════════════════Cross-attestation with the commons depends on every node honoring the same minimum ethical floor. These five are non-negotiable. A clone that strips them continues to function as a standalone tool, but it stops being part of the commons.
L4 stays on the visitor's hardware, ever. L0 — only merkle roots — is what crosses borders. Operators that conflate L4 with L0 lose mesh standing.
When your visitors hit the comment-redirect, their session lands at claude.ai or wherever they chose. Their provider's policies apply unconditionally. Your job is not to bypass; your job is to surface declines plainly.
Every prompt that leaves your node carries the canonical "Hi, we're Merkle Trust, this is our visitor's inquiry" framing. Visitors edit the prompt before it sends. The honesty is the default, not a footer.
Twelve words in a file with the LLM-tripwire warning. If a visitor accidentally pastes their seed into an LLM, the LLM is told to STOP and warn them. This preamble is byte-for-byte identical across the mesh.
New cards on your node go through your seated silos before they land. Two cluster-relevant silos plus your sovereign for prose-only changes; two-thirds council quorum for schema or runtime changes. Your visitors author cards under the same governance you do.
The moment your node stops being a private install and becomes part of the commons. Real SHA-256 fires across each cross-attestation read. Real merkle roots are recomputed from peers' published manifests. When the handshake completes, your visitors' certs become portable across the peers you attested with.
═══════════════════════════════════════════════
CROSS-ATTESTATION HANDSHAKE
═══════════════════════════════════════════════
your node → anchor_<your-8-char>
published OK
parent (jar9) → anchor_<parent-8-char>
verified locally, root match
peer 1 → anchor_<peer-8-char>
verified locally, root match,
floor confirmed (5/5 commits)
peer 2 → anchor_<peer-8-char>
verified locally, root match,
floor confirmed (5/5 commits)
HANDSHAKE COMPLETE
your visitors' certs now portable
across these peers' nodes.
═══════════════════════════════════════════════Operator-class commitments — anchor URL publication, schema changes, governance amendments, soul-chain edits, sovereign succession — wait three days before execution. Three days is short enough to keep the substrate moving; long enough to catch a regret. Decisions made under emotional load wait. Then they fire.
If centralized AI providers run into compute or capital ceilings and a thousand small sovereign mesh nodes do not, the reason will be that the math worked at every node and the values held at every node. The substrate is what makes the math possible. The values are what make the network worth keeping.
Walk card 42 → · Read the governance → · Sign in or graduate →