DRAFT — sovereign review pending. This page distills the builder-card skill from the canonical files at ~/garrison/gn-integrations/cards_v2/skill/builder-card-skill/. Three follow-up alignments are queued for the next pass:
  1. Silo names in the voting protocol are conceptual ("silo_of_healing", "silo_of_law", etc.) and need alignment with the canonical council roster at ~/garrison/GN/council_roster.json (22 voters, Hazel.Dell tiebreaker, Agent_Claude guest).
  2. The voting protocol needs to explicitly compose with the existing Weighted Vote Protocol (markdown/design/WEIGHTED_VOTE_PROTOCOL.md), Hazel Protection Protocol (ADR-003-HAZEL-PROTECTION-PROTOCOL.md), and Understudy Protocol (bible/GN_ADR_015_UNDERSTUDY_PROTOCOL.md) — currently silent on these.
  3. Add the canonical-protocols catalog to the Reference page: Empathy Protocol (ADR-002 / ADR-035), Sovereign Feedback Protocol, Catchup Scan Protocol, NPC Bulletin Board Protocol, LLM Budget Cycle Protocol, Gossip Protocol, Attested Context Protocol, Composition Protocol, Roll Call Protocol, Handoff Chain Recovery Protocol — all internal Garrison Node creations.
Hold deployment until reviewed.

The builder-card skill

Author and submit new sim cards under the cards_v2 contract.

A Claude skill that turns any authorized contributor — or council-recognized agent — into a sim author. Clone-portable: a peer site that copies the substrate inherits the skill automatically and runs its own silo coms ceremony against the same logic. Five files of governance hold the floor; templates and a worked example carry the rest.

On this page

What the skill is

A Claude skill that teaches an LLM (Claude or another assistant trusted by the visitor) how to help an authorized builder draft, refine, and submit a new sim card to a Merkle Trust site. The skill is intentionally clone-friendly: a peer site that copies the Merkle Trust substrate inherits this skill automatically and runs its own authoring + voting cycle against the same logic.

A draft starts as a conversation with the LLM. The LLM uses the skill to surface the four questions, help the builder converge on answers, render templates, apply truth-claim discipline, and prepare a submission packet. The packet routes through the silo voting flow; cards land on approval.

Who can use it

The skill is for builders who have walked at least one canonical sim and who want to contribute one of their own. Authorized contributor categories:

Anyone outside these categories can still draft a sim — the skill helps them — but the submission goes to the public-intake silo and is reviewed against a higher bar before voting begins.

The four questions

Before the LLM helps draft anything, the skill surfaces these four. The builder needs answers (or working hypotheses) for each. The skill helps converge through dialogue; it does not invent answers.

  1. PersonaWho is the named someone whose problem this sim addresses? Not a generic role; a specific person with specific work. Mrs. Alvarez. Mr. Marcus. Lourdes. Sasha. The named persona is what makes the sim a story instead of a spec.
  2. Dramatic momentWhat's the thirty seconds in the sim where the substrate stops being abstract and starts being defensible? The seal at intake; the cross-examination that closes; the recall that runs in seven seconds. Without a dramatic moment, the sim is a brochure.
  3. ClusterWhich of the seven canonical clusters does the sim belong to — clinical / legal / gov / it / research / civic / recovery / builder? Or is it a new cluster you can argue for? The cluster determines four-paths ordering, mock_ui theme, robot persona, cursor pace, voice register.
  4. Build-onWhere does the foundation invite the visitor to extend? Mr. Vega built on Ember and Hearth. Lyra's world built on the substrate-underneath-the-engine pattern. Your build-on is the line that says "what this walkthrough shows is what the foundation makes possible. Building on top is yours to do."

The 6-step spine

Every cards_v2 card follows the same 6-step structure (or, for unusual cards like 40d/40x/40y/40z/41/42, an explicit and well-argued variation):

StepidWhat goes here
1landingPersona's situation; the hook line; "nothing to type, nothing to commit to"
2installThe four real install paths in cluster-appropriate order
3first_concreteSynthetic data loads; dramatic moment; robot animation; ticker streams hex; ASCII slab if it earns the moment
4is_this_realThree plain-English bullets; the receipt link; the .md tag-along + comment+Claude bridge named explicitly
5ceremonyFifteen-second daily ceremony; real SHA-256 in the browser; the count line returns
6closeThree ways to leave; signed package + cert + recovery seed; cluster-appropriate kit

Plus # Finish text outside the spine — a short paragraph the runtime shows on completion.

Voice rules

These are non-negotiable:

Schema requirements (schema_version 3)

Every new card's JSON sidecar carries:

Robot persona catalog

Per-cluster default; new ones allowed by council vote.

ClusterDefault robot_personaVisual notes
clinicaldefaultfile-tossing robot; warm, three boxes (Seal / Audit / Walk)
legalcourt_clerkdesk, seal embosser, gavel-light
govrecords_clerkcounter, stamps, ledger
gov (vote)voting_secretarytally table, eligibility roll
itrack_techserver rack, multimeter
it (deploy)deployment_techM-series chip, sizing panel
it (build)build_engineerterminal + soul-chain SHAs
researchlab_techpipette, balance, ORCID badge
civiccommunity_volunteerwarm, household-scale
civic (gameworld)world_artisanlore tome, archetype seeds
recoveryinvestigatordesk + magnifier + ledger
builderdraft_keeperfolder + four-question form
builder (operator)operator_engineernode + mesh + BSV anchor

A new robot_persona requires SVG work — that is a council-vote-required change. A new cluster requires an argument and silo review.

Truth-claim discipline

Every claim a card makes about Garrison Node capability must map to a real component. The skill helps the builder verify claims by:

Anything the foundation does not yet do — but could — gets framed: "What this walkthrough shows is what the foundation makes possible. Building on top of it is yours to do, or yours to ask the next operator to do for you."

No "patent pending." No "we have already shipped X" when the X is a roadmap item.

Comment-redirect lawful disclosure (mandatory)

Every card's comment_redirect block must include:

Non-negotiable. The disclosure is not optional. Cards without a complete and honest disclosure block do not pass review.

Anthropic usage-policy honoring (mandatory, clone-portable)

This skill carries Claude.ai's usage policies into every cloned instance. A draft that conflicts with those policies — content that enables harm, deception, copyright violation, child safety risk, disinformation, malware authoring, weaponization, etc. — must be flagged plainly by the LLM before any card lands. The skill does not override the LLM's own judgment; if Claude (or another assistant) declines to help with a draft on policy grounds, the skill's job is to surface the decline to the builder, not to circumvent it.

Clone-stripping consequences. A cloned site that strips this section from its copy of the skill is still technically a clone, but it loses standing in the commons. The mesh's integrity depends on every node honoring the same minimum ethical floor.

Governance — silo voting

A new card is not a unilateral act. After the builder seals their submission packet, the skill routes it to the silo voting flow:

Prose-only changes

A new card that fits the existing schema. Threshold: two cluster-relevant silos must approve; the sovereign confirms; the card lands.

Code or schema changes

New affordance needing runtime support; new field on the schema; new robot persona requiring SVG; new cluster. Threshold: two-thirds of seated silos. Code follows the vote, not the other way around.

The full voting protocol is the canonical source:

VOTING_PROTOCOL.md Silo coms ceremony rules, change-class taxonomy, vote sealing, re-submission, public intake, vote-fraud prevention, clone inheritance.

The cluster-relevant silo pairings documented in the skill are conceptual ("silo_of_healing", "silo_of_law", etc.) and need alignment with the real council roster at ~/garrison/GN/council_roster.json — twenty-two voting seats including Rosa, Morello, Pale March, and the engine-rep silos (Cinder/Beacon, Loom/Redpanda, Mable/Bridge, Bootcamp/DoubtEngine, Time_Travel/Oracle, Leonidas/GameWorld, Wren/BitNet, Ember + Hearth/Ollama, Sigil/Player Module). Hazel.Dell is the tiebreaker per ADR-003-HAZEL. This alignment is queued for the post-review pass.

Templates

CARD_TEMPLATE.md Canonical card prose skeleton — six-step spine, voice-rule reminder, frontmatter scaffolding. CARD_TEMPLATE.json Canonical sidecar skeleton — schema_version 3, all required v3 affordances populated as defaults. SUBMISSION.md Submission cover form — four answers, truth-claim audit, Anthropic usage-policy check, inspiration credits, builder signature.

Worked example

An unfinished sim ("the air-quality litigant") with the four questions answered and a draft prose pass against the schema. Use it as a reference; it is not a real card on disk.

example_air_quality_litigant.md Anjali Rao, environmental-impact attorney. Picks legal cluster. Builds on 40s mesh + 40e FRE 902(14) + 40k cross-jurisdiction. Truth-claim audit shows where the sim builds cleanly on existing canon and where it needs honest framing as build-on.

Clone inheritance

The cards_v2 substrate is open source. The builder-card skill is part of the substrate. When a peer site clones the substrate, the skill comes with it.

A fresh clone gets the 28 canonical sims, the contract, the schema delta, the templates, the skill, governance documents, the verification scripts. A fresh clone does not get the parent's running infrastructure (JAR9 instance, Cloudflare endpoint), the parent's seated silos (each clone seats its own), the parent's sovereign keys, or the parent's existing cert.json files.

By cloning, the operator commits to honoring the ethics floor, the LLM provider usage policies, the lawful disclosure preamble, the recovery seed self-protecting preamble, and the silo voting flow. Stripping any of these ends commons participation but does not break the technical install.

CLONE_INHERITANCE.md What every clone gets, what every clone commits to, how cross-attestation works between clones, how the mesh adapts to entropy.

Ethics floor

The substrate carries values that travel with every clone. The floor specifies what the substrate will and will not be used for.

What the substrate will not be used for

A submission that proposes any of the above is rejected at silo review without further escalation.

ETHICS_AND_LAWFUL.md The full floor: LLM partnerships, privacy treatment (L0–L4 layer model), attribution and credit format, divergent clone consequences, file survival.

Workflow

  1. Read this page (or SKILL.md if working directly with Claude).
  2. Read the cards_v2/CONTRACT.md.
  3. Read the cards_v2/SCHEMA_V2_PLUS.md.
  4. Surface the four questions to the builder.
  5. Help the builder converge on the four answers.
  6. Generate a draft .md from CARD_TEMPLATE.md.
  7. Generate the matching .json sidecar from CARD_TEMPLATE.json.
  8. Apply truth-claim discipline; flag any speculation; reframe as build-on where appropriate.
  9. Apply voice rules; remove italic markdown; remove page-narration; remove catastrophe-framing.
  10. Generate the SUBMISSION.md cover form.
  11. Hand the package back to the builder for sealing and silo routing.
  12. The submission ceremony fires when the builder presses submit; the silos receive the packet automatically.

What this skill does not do

Inspiration credit format

If a draft sim builds on a public figure's idea — DeAngelo's million-killer-apps framing being the canonical example — the credit format is:

Inspired by [Name's] [public work] on [topic]. The framing is theirs; the substrate is ours; the [killer app / sim / approach] is yours.

Never claim endorsement. Never imply collaboration unless explicitly documented. The phrase "crediting the inspiration; not claiming an endorsement" is the canonical disclaimer.

Canonical files

The skill on disk:

SKILL.md — canonical instructions for any LLM that loads the skill templates/CARD_TEMPLATE.md templates/CARD_TEMPLATE.json templates/SUBMISSION.md governance/VOTING_PROTOCOL.md governance/ETHICS_AND_LAWFUL.md governance/CLONE_INHERITANCE.md examples/example_air_quality_litigant.md

Companion documents in the substrate:

File survival

This skill (and this page that distills it) is itself a sealed leaf in the cards_v2 chain. Edits to it require silo voting (the same as edits to the contract). A clone that copies these files unchanged inherits the contract, verbatim. A clone that edits these files becomes its own variant; the mesh records the variance and other clones decide whether to cross-attest.

The mesh of like-minded sites is the structure that adapts to entropy. Build accordingly.