For visitors who'd rather read than walk.
# The geek-panel special — under the hood
You're an engineer evaluating the substrate's engineering decisions.
You don't need a persona; the cards for everyone else are framed
around their work. This card is framed around the engine.
The hook: the substrate is real, and if you want to contribute, you
are walking into a system whose engineering decisions are reasoned,
whose voting is real, whose attestation works, and whose
contribution flow rewards sustained quality.
For an engineer evaluating, the order is GitHub-first, mesh-second.
Clone the substrate, read the cards, run the verification scripts.
Subscribe to a regional operator or paste the markdown into your LLM
if you want to evaluate without committing to local infrastructure.
The substrate uses blockchain in three places. Not "everywhere as a
buzzword" — three places, each load-bearing for a specific reason.
Local rustchain (rustchain-v2, forked from Scottcjn/Rustchain).
The per-Garrison-Node attestation chain. Each node's records seal
to its own local chain first. Replay from any anchored point
produces the same state. Files: GN/ws/ws3_forge/rustchain-v2/
including src/contract.rs, src/attestation.rs, src/sentry.rs,src/ring_buffer.rs. Cards: 24_chain_*, 34_rcv2_*.
BSV anchor (rust-sv). Local rustchain anchors periodically to
Bitcoin SV via rust-sv. The double-anchor pattern: a chain
failure on either side does not collapse the integrity argument.
Cards: 34_rcv2_bsv_*.
Beacon-skill signing surface. ed25519 + HMAC-SHA256 over the
substrate's own internal events. Cards: 23_bridges_beacon_*,
23_bridges_beacon_skill_dispatcher.md.
```
═══════════════════════════════════════════════
THREE PLACES BLOCKCHAIN IS USED
═══════════════════════════════════════════════
rustchain-v2 → per-node attestation
(replay deterministic)
rust-sv → BSV double-anchor
(fork resilience)
beacon → ed25519 + HMAC-SHA256
(event signing)
Each is load-bearing for a specific reason.
None of them is "blockchain for blockchain's sake."
═══════════════════════════════════════════════
```
The 23 silos. Twenty-three software agents, twenty-three lore
archetypes, paired by design. Each agent has a personality,
responsibilities, and a place in the council. The pairing is real
in code — silos/<name>/active_personality.json ties an agent to
its archetype. Cards: 27_npc_garrison_local.md;
GN/silos/morello_m/.
Morello and time travel. Replay-from-any-anchored-point is the
property that makes attestation defensible. The morello layer is
where this property is enforced — every event is timestamped,
hashed, and ordered such that replay produces identical state.
Cards: 25_ecosystem_garrison_cycle_state.md, 19_under_the_hood.md.
DuckDB cube. The substrate uses DuckDB for analytical queries
across the chain. Inference-Identity Ranking (iir) — a derived
metric — runs on the cube. The choice of DuckDB over a heavier
analytical engine is deliberate: portability, embeddability, no
external service dependency.
Voting layer and contribution flow. The contribution flow is
real voting; council members weigh in on substantive changes; the
record of votes is sealed and auditable. Sustained quality —
contributions sustained over time, not single bursts — is what
counts. Cards: 16_doer_onramp.md; 11_discipline_ceremony.md.
The .md button puts the engine-internals summary into your
tag-along bundle, including the three-places slab. Comment field
routes a specific architecture question to your own claude.ai
session.
For an engineer, the ceremony shape is the contribution flow itself.
A first PR is the first ceremony. The card explains the ladder:
- First contribution: the contributor's identity is attested at
first-PR-merge by the maintainer. CLA-equivalent step is implicit
in the merge.
- Sustained quality: the contribution flow rewards the
contributor whose work shows up in commits, in voting, in
discipline-ceremony participation, week after week.
- Voting weight: earned, not granted. Sustained contribution
earns a seat in council voting. The vote record is on chain;
weights are reproducible.
Real crypto.subtle.digest runs in the engineer's browser when
they read this card and the cursor halts at the contribution-flow
diagram. The seven-file soul chain is there to verify if they want
to.
The most useful close for an engineer is to bookmark
16_doer_onramp.md and 11_discipline_ceremony.md. Plan the first PR
for the following weekend.
The package, the cert, the recovery seed all ride along. The cert
becomes the engineer's identity for the way back — the substrate
recognizes them next time they show up at a PR review.
<!-- finish_text -->
That was the geek-panel special. The substrate is real; the
engineering decisions are reasoned; the voting is real; attestation
works; and the contribution flow rewards sustained quality. The
full card lists each architectural decision with the file
references, the ADRs that recorded them, and a
sustained-contribution prediction that's yours to test.