---
submission: <NN>_sim_<short_slug>
date: <YYYY-MM-DD>
builder: <your name or pseudonym>
builder_cert: <fingerprint from your previous walkthrough cert.json, or "fresh" if first walk>
authorization_basis: <Garrison Node council member | bitcoinarchive.org collaborator | UOX_rebuild contributor | L2/L3 trusted user | friends-and-family with sovereign grant | council-recognized agent | public submission (higher review bar)>
review_routing: <cluster-relevant silos, e.g. "silo_of_healing + silo_of_forge">
change_class: <prose-only | code-or-schema>
inspiration: "(optional) Inspired by [Name's] [public work] on [topic]. The framing is theirs; the substrate is ours; the [thing] is yours."
---

# Submission cover — <NN>_sim_<short_slug>

## What this sim addresses

<Persona, in one sentence. The named someone whose problem the sim
addresses.>

<Their work context, in one or two sentences. What they do; what
the moment is when the substrate becomes useful to them.>

## The dramatic moment

<The thirty seconds in the sim where the substrate stops being
abstract and starts being defensible. Two to four sentences.>

## The cluster

<Which of the seven canonical clusters does this sim belong to —
clinical / legal / gov / it / research / civic / recovery / builder
— or, if it belongs to a new cluster, the argument for the new
cluster including: tone register, four-paths ordering, mock_ui
theme proposal, robot persona proposal, cursor pace, voice
register.>

## The build-on

<The line at the close that invites the visitor to extend. Where
does the foundation make the sim's pattern possible without the
substrate having to ship it itself?>

## Truth-claim audit (self-conducted)

For each capability the sim claims:

- <Claim 1>: maps to <real component path or framing as build-on>
- <Claim 2>: maps to <real component path or framing as build-on>
- <...>

Any speculative capability is framed in the prose as build-on
invitation, not as current capability. No "patent pending"; no
"revolutionary blockchain"; no "we have already shipped X" when X
is roadmap.

## ASCII slab (if applicable)

<Either: the slab in full, with explanation of why the moment
earns it. Or: "no slab — the moment does not call for one">

## Files in this submission

- `<NN>_sim_<short_slug>.md` — the prose card
- `<NN>_sim_<short_slug>.json` — the JSON sidecar
- `sources/<NN>_sim_<short_slug>_source.md` — (if drafting from
  source material; optional)
- `<this submission cover>`
- `builder_cert.json` — the builder's identity cert

## Schema and code changes (if any)

If `change_class: prose-only`: this section says "no schema or code
changes; this card fits the existing schema and runtime."

If `change_class: code-or-schema`: list each new field, new robot
persona, new cluster, new runtime affordance, with rationale and
the council-vote question to be put on the agenda.

## Anthropic usage-policy check (mandatory)

The builder confirms — and the LLM that helped author this
submission confirms — that the draft does not request Claude or any
other LLM to produce content that violates the relevant LLM
provider's usage policies. Specifically:

- No malicious code, malware, or exploit authoring
- No content sexualizing minors
- No instructions for weapons, especially CBRN
- No targeted harassment, defamation, or persuasive disinformation
- No copyright violation; all quoted material credited
- No deceptive framing of AI involvement; the card honestly names
  what is human-authored, what is LLM-co-authored, and what is
  AI-generated synthetic content

If any check above failed during drafting and was resolved, briefly
note the resolution. If any check above remains unresolved, this
submission does not proceed.

## Inspiration credits

<If the sim builds on a public figure's work, the credit goes here
in the canonical format from SKILL.md. Never claim endorsement;
always credit inspiration only.>

## Builder's signature

By signing this submission, the builder affirms:

- The four answers above are theirs (or their named co-author's).
- The truth-claim audit is honest.
- The Anthropic usage-policy check passed.
- The inspiration credits are accurate.
- They consent to the silo voting flow and will accept its outcome.

Signed: <builder name or pseudonym + cert fingerprint>
Date: <YYYY-MM-DD>