Twenty-eight sims cover clinical, legal, gov, IT, research, civic, recovery, and the operator onramp. They are illustrative, not exhaustive. The substrate underneath supports many more, and the builder skill turns any authorized contributor — or council-recognized agent — into a sim author.
Card 41 is the builder's sim. It walks the four-question contribution flow and the silo voting structure. Walk it before you start drafting; it sets the shape.
Every sim begins by answering these four. The skill helps you find the answers; it does not invent them for you.
Who 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. Aiyana. The named persona is what makes the sim a story instead of a spec.
What'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. The bench ruling that names FRE 902(14). Without a dramatic moment, the sim is a brochure.
Which of the existing 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.
Where 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 at the close that says "what this walkthrough shows is what the foundation makes possible. Building on top of it is yours to do."
The builder-card skill teaches a Claude session (or another LLM you trust) how to help you draft, refine, and submit a new sim under the cards_v2 contract. It carries the voice rules, the schema_version 3 templates, the four-paths cluster ordering, the ASCII-slab patterns, the comment-redirect lawful disclosure, the attestation patterns, and the silo voting flow.
The skill is portable: a clone of the substrate inherits the skill automatically and runs its own silo coms ceremony against the same logic. Five files of governance hold the floor: voting protocol, ethics and lawful behavior, clone inheritance, plus the templates and a worked example.
A new card that fits the existing schema, uses an existing audience cluster and mock_ui theme, and proposes no runtime change. Threshold: two cluster-relevant silos plus the sovereign. Cluster pairings are documented in the voting protocol.
A change that adds a new schema field, a new robot persona requiring SVG work, a new cluster, a new mock_ui theme requiring CSS work, or modifies the runtime. Threshold: two-thirds of seated silos. Code follows the vote, not the other way around.
The substrate carries values that travel with every clone. By submitting a card, you affirm:
Walk the bonus card. Read the skill. Open Claude with the skill loaded. Author your draft. Submit it through the silo flow. The 1,000,001th killer app is yours to build.