# 11 — Build Order **pack** Map Your Case · draft-1 · 21 August 2026 **role** The v3 phases, in an order chosen by two rules: the genesis components are written before anything is programmed (the maps' finding), and every screen is tabletop-tested as a fixed mockup before it is built (the synthetic-readers programme's highest-value use). Every definition of done is a run or a check, not a feeling. --- ## The two ordering rules 1. **Documents before code.** Document 10's maps agree that this tool's scarce components are editorial — library curation, per-node dates, level-one prose, archetype property lists, the calibration record. Writing them is the critical path; the code around them is product-shaped. 2. **Tabletop before build.** A fixed hand-written mockup satisfies the fixed-artefact requirement completely, so every new screen gets a synthetic-reader round *before* implementation — a defect found there costs a file edit rather than a refactor. This is also the move the corpus already endorsed: a design published before it is built is the strongest available demonstration of the working method, and a published tabletop against an unbuilt page is that move one layer deeper. ## Phase 0 — Capture (this pack) Ship the pack itself; adopt or correct it via change control. **Done when:** the project lead has read 00–01 and 12, and the open decisions in 99 are assigned rather than ambient. ## Phase 1 — The library's debts Per-node dates (MC3); the five grant-ordered scenarios replacing the four v2 examples; the entry checker (stories L1/L3) as a script the site's validator runs. No new screens. **Done when:** every node carries its own date; the checker fails on a node missing tier/evidence/detail and on a fact-id rename; the five scenarios load. ## Phase 2 — Level one, tested before built Write the level-one landing as a fixed mockup (one screen, complete answer, plain language). Compose the first archetypes (property lists published, sources never). Set the first budgets (document 08's proposal stands until somebody with authority replaces it). Run the tabletop: every archetype, fixed comprehension question, spend recorded. Publish the run — including abandonments — in the run gallery with inline markers. Only then implement the screen. **Done when:** a published run record exists in which every reader either stated what the page told them within budget, or the abandonment produced a change, and the changed page's re-run is published beside it. ## Phase 3 — Sharing The fragment scheme of document 09: encoder that refuses non-identifiers, version pinning, the mismatch notice, the marked loaded state. **Done when:** stories S1–S3 pass as written; the network panel check (V8) still passes; and a link minted before a library change renders the notice after it. ## Phase 4 — The three sets The dashboard reframed as mandated / exercised / held. First on the visitor's claims (ticked capabilities); the transcript import only if and when MC-D7 is decided — it is the one feature in this pack that could breach P1 by accident, so it waits for its decision rather than prototyping around it. **Done when:** the three sets render distinctly; the middle set's concession copy is present; and nothing transcript-shaped exists anywhere in stored or shared state. ## Phase 5 — Variants, with humans Only now — after synthetic rounds have cleared the levels — recruit the few dozen real readers, visual variants first (the framing effect lives there), qualitative method: watch, ask for say-back, count nothing. **Done when:** each level passes the stopping rule with a real reader (*shown only this level, they say what they would do rather than that they would keep reading*), and the findings are published as findings, not percentages. ## What is deliberately not scheduled The vault path (durability without a backend's privacy cost), the machine scan, and the persona-simulation service of document 08's part two. The first two wait on registry-pack decisions 31/35; the third waits on a calibration record existing at all — building the service before the record is building the unfalsifiable version, and the record can only come from phases 2 and 5. ## The standing checks, every phase Same-origin (V8) re-run before every release; the model suite green; the no-free-text grep; the wording rules of document 06; and the release discipline this site already runs — version bump, regenerated pages, validator, live-hash check. --- This document is released under the Creative Commons Attribution 4.0 International licence (CC BY 4.0).