v0.1-garage-release-manifest.md

RFC: v0.1 "The Garage" — Release Manifest & RFC DAG

• Status: accepted — owner batch acceptance 2026-09-25; implementing
• Author: Marco (drafted by Claude)
• Created: 2026-09-25
• Design refs: design/07 Phase 1 (the v0.1 scope list and its fiction line) and §Sequencing principles 1–4; design/01 Tiers 0–2; design/02 §2, §3, §5, §6/§6b, §11; design/03 §1, §7, §8, §Unlock stagger, §12b; design/04 §1, §4; design/05 §2; design/08 §1–3; design/09 §6; design/13 §2, §4, §7 (the [v0.1]-tagged world items)
• Depends on: the Phase-0 Playable Preview floor (planning/platform-alignment/phase0-manifest-proposal.md P01–P07/F01–F05, pending D-007 adoption); every RFC named in §3
• Parent / amends: — (release manifest; specifies no mechanic of its own)
• Supersedes / superseded by: —
• Planning: planning/v0.1-garage-release-manifest/ (once accepted)
• Evidence coordinate: repository HEAD c2d9bbc; product source 7e8aa70; balance epoch 8 (First-Hour Payoff, bundle sha256:baa890501b2864d14cc0238d633a562cb8c6fca406190487831e0c447af128f6). No product code was run for this draft. It is a static trace of sources, docs and catalogs, and every "Live" cell below cites the canonical doc or data file it came from.

Summary

This RFC lists every item design/07 names for v0.1 "The Garage", plus the [v0.1] items in design/13, and records the following for each one:

• its current backend, player-surface and content state, with evidence;
• the RFC that owns it;
• what is missing;
• the other items it depends on.

It then orders the owning RFCs into a dependency DAG with tiers that can run in parallel, proposes the batches Marco should accept together, and defines the v0.1 exit criteria.

This RFC authorizes no mechanic and no release. It is the "release RFC" input that phase0-manifest-proposal.md §"Decisions and proof still required" item 3 asks for, applied to the milestone after the preview.

Motivation and authority boundary

1. The preview comes first. Owner rulings D-001 and D-007 (2026-08-21, planning/platform-alignment/owner-ruling-packet.md) made the Phase-0 Playable Preview the next target: T0–T1 only, "explicitly not roadmap v0.1". This manifest does not widen the preview. It plans the next milestone, and it inherits the preview's release floor F01–F05 unchanged: the ruling packet says a release label cannot waive those obligations.
2. Why it is needed now. planning/roadmap-1.0.md records v0.1 as "Not yet scoped in accepted release RFC". Six new content and surface drafts are being written in parallel. Without one manifest they would re-derive their dependency edges independently and could leave items with no owner. §1 found five such items: Clout mint and PR Interns, cosmetic ownership, pet adoption, the ticker content slice, and headcount allocation if it is not specified inside tier2-content.
3. Out of scope. This RFC does not specify mechanics, balance numbers, copy text or schemas. It does not edit design/07. Reconciling design/07 with the preview ruling is the owner's task (see OQ-1). It does not authorize any v0.2+ item: factions as a play surface, community milestones, Events Layer 2, or the board-game suite.

Draft-set caveat. At the evidence coordinate, the six new drafts (rfc/tier2-content.md, rfc/reputation-tree-v1.md, rfc/minigame-terminal-typer.md, rfc/minigame-server-garden.md, rfc/minigame-demo-disc-arcade.md, rfc/garage-player-surfaces.md) do not yet exist in the tree. Their assumed scope in this RFC comes from their assigned titles. Acceptance criterion MC-2 requires this manifest to be re-reconciled against their actual bodies before acceptance. In particular, an item marked UNOWNED here may turn out to be claimed by one of them.

Specification

Legend

• Backend: Live means code, a canonical doc and an artifact pinned in the current epoch. Impl-inactive means code exists but no content is pinned or activated. Fixture means the code is tested but the content lives only in test data. Partial means some but not all of the needed code exists. Absent means no code.
• Surface: Mounted means reachable in client/src/game-ui/surfaces.json. Stub means rendered but not stateful. None means not rendered.
• Content: Pinned means in epoch 8. Design-only means the content exists only in design/ or design/research/.
• Owner states: archived (implemented), implementing, accepted, draft, new-draft (being written now), and UNOWNED. An UNOWNED item has no draft; this RFC proposes a name for one, and the proposal is not authority.

§1 — The manifest table

1a. Items named by design/07 Phase 1

ID	v0.1 item	Backend	Surface	Content	Evidence	Owning RFC	Missing for v0.1	Depends on
G01	Tier 0 complete (Sole Proprietor)	Live	Mounted (Desk)	Pinned	docs/t0-t1-playable-content.md §First-hour progression; balance/catalogs/phase0.json (tier-0 generator rows beige_tower, dot_matrix_queue, answering_machine …); archived rfc/archive/t0-t1-playable-content.md	archived T0–T1 Playable Content; any delta → tier2-content (new-draft)	A row-level audit of design/01 Tier 0 against the shipped catalog has not been done. Unaudited items include the IDDQD cheat cosmetic, the locked-door lore card, the MIDI toggle and the Single-Income Household building. Each design item must be classified as shipped, v0.1 delta, or deferred (manifest task M-1).	P01–P03
G02	Tier 1 complete (Garage Business)	Live	Mounted	Pinned	Same as G01. Gate gate.t0_to_t1 is live (balance/routes/phase0.json). The first-hour envelopes are governed.	archived T0–T1 Playable Content; delta → tier2-content	The same M-1 audit for Tier 1: the Intern autoclicker, the Garage plaque, the Woz lore card and the first opt-in ideology events. The ideology events need Events L1 (see OQ-7).	G01
G03	Tier 2 complete (IT Company)	Absent	None	Design-only	balance/routes/phase0.json has no gate.t1_to_t2 (its gates are t0_to_t1, t2_to_t3, t3_to_t4, t4_to_t5, t7_to_t8). There are no tier-2 generator rows and no era_2010 copy key (client/src/copy/generated/catalog.json has only era_1995 and era_2000).	rfc/tier2-content.md (new-draft)	Everything, including: the T1→T2 gate; the T2 catalog rows; a T1→T2 doctrine row, or an explicit deviation (design/01 §Structure says every tier transition has a 1-of-3 doctrine, and balance/doctrines/first-content.json has only capture and ethical); procurement automation; the T2 satire beats (Unlimited PTO, We're A Family, the layoffs event); and harness pacing to T2.	G04, G05, G06 (Exit timing, OQ-8), archived Routes/Doctrine/Harness
G04	Cost-curve economy	Live	Mounted	Pinned (T0–T1)	docs/economy-kernel.md, docs/purchasable-content.md; archived RFC-0002, Purchasable Content, Geometric Afford	archived	Only the T2 rows, under G03. No kernel work.	—
G05	Headcount allocation	Absent	None	Design-only	balance/economy.schema.json generator roles are only provision, synergy_feed, manual_output and stock_rate. There is no allocation primitive. design/01 Tier 2 calls it a new grammar: a finite hiring budget across roles, plus morale.	tier2-content if it specifies the grammar. Otherwise split to rfc/headcount-allocation.md (UNOWNED, proposed) under RFC-0000 rule 2.	The allocation state, intent, closed-form production contribution (lazy, never a tick loop), Middle Manager conversion, morale linkage to archived Meters/Soul, and save-version bump.	archived Production Engine, Save Layer, Meters, Soul
G06	First Exit loop	Live (RFC implementing)	Mounted (Offer Sheet, Run End, Wind Down on Desk)	Pinned	docs/prestige-and-exits.md; docs/game-ui.md §Shipped surfaces; rfc/prestige-and-exits.md (implementing); preview P04/P05	rfc/prestige-and-exits.md (implementing)	Three things. (1) The Prestige archival range-union and designated verdict. (2) The Offer focus defect (accessibility-current-audit.md, preview P05). (3) How Exit timing interacts with T2: design/01 Tier 2 says "first prestige available shortly after" T2, but the shipped first elective Exit lands in T1 at 45–90 min (OQ-8).	P04/P05, F03
G07	Reputation tree v1	Partial	None	None	Founder state carries ReputationLevel and Reputation unlock strength. docs/prestige-and-exits.md §New-run assembly says: "The current fixture has no Network or Reputation-tree content, so those declared seams are empty."	rfc/reputation-tree-v1.md (new-draft)	The tree catalog (unlock-gated 5→100% strength, starter packages, offline extension, Network slots I–V per design/02 §3.2), the spend intent, the new-run assembly consumer, the surface (G-S) and harness second-run pacing.	G06
G08	Fiscal Quarters / Earnings Calls	Live backend; docs disagree	None	Pinned (see discrepancy E-1)	Archived Fiscal Quarters Foundation. balance/epochs/phase0.json registers fiscal → balance/fiscal/first-content.json, and rfc/first-content-epoch.md (Founder-scoped activation) lists fiscal as minted. But docs/fiscal-quarters.md lines 3–5 say no epoch contains it. The surface list has no fiscal surface.	Surface → garage-player-surfaces (new-draft). Docs fix → Fiscal docs owner (E-1).	The Earnings Call harvest surface (ripening, early-harvest risk curtain, hoard readout), the Investor Confidence spend surface, the harness "first Earnings Call ritual day 2" target (design/02 §11), and the E-1 docs reconciliation.	F03
G09	Clout v1 (achievements + PR Interns)	Partial	None	Achievements pinned (12 defs)	docs/achievements.md lines 3–5 ("does not mint Clout") and 41–42 (epoch 6 pins twelve definitions scored 2/4/8). server/save/state.go CloutLifetime is a stored integer with no mint. "PR Intern" appears nowhere outside design/.	Achievement reader surface → garage-player-surfaces. Clout mint and PR Interns → UNOWNED; proposed rfc/clout-v1-and-pr-interns.md.	The owner ruling on the single Clout mint (OQ-5), the this-run Clout accrual, the PR Intern multiplier (1 + Clout × factor) keyed on this-run Clout only (design/02 §6 carry rule), the reach-only lifetime Clout, and the surfaces.	Archived Achievements, Production multiplier stack; OQ-5
G10	Cosmetic shop ($0.00, Horse Armor)	Absent (stub)	Stub	Copy pinned	client/src/game-ui/GameUIApp.svelte:353 renders a single card. client/src/game-ui/presentation.ts:8 declares CosmeticBinding as purchasable: false; stateful: false. docs/game-ui.md calls it the "free Horse Armor shelf".	Surface → garage-player-surfaces. Ownership state → UNOWNED; proposed rfc/cosmetic-shop-v1.md.	A shop with a $0.00 acquisition intent, persisted ownership, the curtain-pull tooltip (law 10), and the pet-annoyed reaction (design/04 §4, which depends on G14). Real-money paths must be absent by construction (law 1).	G14 (reaction only)
G11	Demo Disc Arcade	Absent	None	Design-only	Present only in design/03 §8 and design/01	rfc/minigame-demo-disc-arcade.md (new-draft)	Tenant engine(s), catalog, faucet/scaling rows, surface, and the legal rule (mechanics yes, trade dress and names never) as an F05 rights check. Daily-slot ghost scores are async (OQ-2).	Minigame Platform (accepted), Minigame API & Surface AC5 (accepted, blocked), archived Fiscal unlock rows
G12	Terminal Typer	Absent	None	Design-only	design/03 §7	rfc/minigame-terminal-typer.md (new-draft)	Tenant engine, keystroke-skill certification without client-reported results (law 2), streak, click-power hook, and surface. Ghost races are async and store keystroke recordings, which is player data (OQ-2; D-008/D-009/D-015).	As G11
G13	Server Garden	Absent	None	Design-only	design/03 §1 (Tier 2, wall-clock crossbreeding)	rfc/minigame-server-garden.md (new-draft)	Wallclock tenant with lazy tick math, the strain catalog, substrates, the sacrifice ritual, and payloads. Out of v0.1: the T3 daemon-spawn payload, strain gifts (social) and the seed-census milestone (World L3/D-016).	G03 (T2 unlock), archived Fiscal (building levels grow the grid), G09 (Clout-drop payload), Minigame Platform, MA AC5
G14	Pet adoption + care	Care Live; adoption Absent	None	Care policy pinned; no species	docs/pet-care.md line 5 ("Pet identity/species acquisition … remain unimplemented") and line 43 ("no starter pet or species is fabricated"). Archived Pet Care Foundation, marked "combat AC3 carried".	Care surface → garage-player-surfaces. Adoption mechanic → UNOWNED; proposed rfc/pet-adoption-v1.md.	The species catalog, the starter server-room cat at T0 (design/04 §1), adoptable variants at T2 (design/03 §Unlock stagger; scope in OQ-9), the adoption intent and first-record creation, Trust, and a sincere-tone surface (law 10).	Archived Pet Care, Founder Attendance, Soul
G15	Presence feed + global counters	Partial	Visitor counter Mounted; feed None	None	docs/transport.md lines 77–83: the world snapshot carries online/total Founders and Commons health, with planet and milestone "deliberately zero/null until those owners ship". The feed channel carries nothing (rfc/feed-and-dispatch-foundation.md §Summary). docs/game-ui.md line 24 (presence is hidden until a real count arrives).	rfc/feed-and-dispatch-foundation.md (draft) + rfc/world-layer-foundation.md (draft, v0.1 slice only)	Feed: the dispatch producer, an NPC-company fallback (design/05 §2, required by law 6 but absent from the feed draft), and a client feed surface. Counters: "total production this hour" (absent) and the Planet counter (WL4). Milestones (WL3) stay in v0.2 under sequencing principle 2 and D-016.	Transport (implementing), archived Gameserver world aggregator; OQ-3, OQ-4
G16	Era UI for tiers 0–2	Partial	Mounted (T0/T1 eras)	T0/T1 pinned	docs/game-ui.md lines 20–22: the era is derived from the authoritative tier, with 0→era_1995 and 1→era_2000. There is no era_2010.	rfc/garage-player-surfaces.md (new-draft)	The T2 "2010 flat startup" era (design/08 §2), era-voiced patch notes, and the tier-up transition.	G03
G17	Ticker/dispatch v1 + launch corpus slice	Absent	None	Design-only	No ticker copy key in client/src/copy/generated/catalog.json. The corpus (~200 lines) lives in design/research/*.md per design/08 §3, which says to ship ~30% at launch.	Mechanics → feed-and-dispatch-foundation. Ticker surface → garage-player-surfaces. Content slice → UNOWNED; proposed rfc/ticker-launch-corpus.md, or absorbed into garage-player-surfaces.	Ticker surface, parameterized corpus rows through the Copy Pipeline, and the citation-per-line and verify-before-ship pass (design/08 §1 rule 3; design/07 principle 4). The copy is owner-authored (evidence discipline 6).	G15 feed mechanics, archived Copy Pipeline
G18	Satire beat: "a small business opens its doors"	n/a	n/a	Partial	Only T0–T1 satire copy is pinned. The beat spans G03, G10, G11 and G17.	Each content RFC plus the Copy Pipeline	The beat is proven by the exit criterion (§4, EC-7), not by a separate system.	G03, G10, G17

1b. [v0.1] items tagged in design/13 but absent from design/07's list

ID	Item	State / evidence	Proposed owner	Needs
X01	Personal diorama, tiers 0–2, with the four dials (design/13 §2)	Absent. No SceneSpec reducer in client/src.	garage-player-surfaces, or its split	An owner ruling on inclusion (OQ-6). The pure WorldState → SceneSpec reducer rule is non-negotiable per design/13 §2.
X02	Tier-up ceremony	Absent	garage-player-surfaces	OQ-6; accessibility A4 reduced motion
X03	Away fast-forward on return	Partial. An offline notice exists (docs/game-ui.md); there is no fast-forward.	garage-player-surfaces	OQ-6
X04	Planet counter as a HUD number	World snapshot field exists and reads zero	world-layer-foundation v0.1 slice (WL1+WL4)	OQ-4

1c. Carried release floor (F01–F05) and preview tasks (P01–P07)

v0.1 must satisfy all of phase0-manifest-proposal.md P01–P07, re-proven on the v0.1 bundle, and all of F01–F05, extended to every v0.1 task in 1a/1b.

ID	Floor obligation	Current state	Owner	Gating decisions
F01	Recovery code shown once with copy/download, plus recovery of an existing account	Posture ruled (D-005). The browser silently persists the code (RP-123).	UNDRAFTED account recovery/rights successor (execution-queue.md row 6) on rfc/account-and-session-bootstrap.md (implementing)	D-005 (ruled); R-003
F02	Export and delete through the UI, with truthful retention disclosure	Backend deletion tests exist. Residuals are open (RP-118–RP-130). There is no UI.	Same undrafted successor + undrafted operations/retention contract (row 7a)	D-008, D-009, D-015 open
F03	Every task keyboard/AT-operable, 320 px reflow, lifecycle focus and announcements, motion posture	Current probes fail focus and reflow (accessibility-current-audit.md)	rfc/accessibility-player-workflows.md (draft)	D-018 open; R-005. v0.1 adds ~10 new surfaces to D-018's task population.
F04	Install, back up, restore, upgrade, roll back and alert on the single-node bundle	Implementing. DP-A–DP-E CHANGES REQUIRED; corrective range 67fd415..ec5518b awaits Codex review.	rfc/deployment-foundation.md (implementing) + undrafted operations contract	D-006, D-011 (ruled); R-006, R-007
F05	Current-head CI, severing witnesses, source/artifact rights, owner release call	Hosted CI green at aa27705 (D-014). The Copy successor (row 2h) is blocked.	rfc/scaffolding-and-ci.md (implementing); Copy successor (undrafted)	D-014 (ruled); rights review of G11 arcade trade dress and G17 citations

§2 — Decisions gating v0.1

Existing decisions (planning/platform-alignment/decision-queue.md):

ID	State	What in v0.1 it gates
D-007	Ruled in principle; exact preview manifest not adopted	Everything. v0.1 builds on the adopted preview task set.
D-008 / D-009 / D-015	Open	F02, and the retention of new v0.1 player data (keystroke ghosts, pet records, cosmetic ownership, Garden collections)
D-013	Deferred for the preview	G11/G12 async modes (OQ-2)
D-016	Deferred for the preview	G15 counters (OQ-4), and G13 census and world milestones (kept out of v0.1)
D-017	Deferred for the preview	G15 feed content (OQ-3). FD2's user-submission pipeline stays out.
D-018	Open	F03 for every v0.1 surface
D-012	Deferred (Advisor Mode)	Nothing in v0.1. Advisor Mode stays out.

Proposed owner questions (VQ-; Marco may promote them to D-019+). The recommendation is listed first in each case. None is inferred here.

• OQ-1 / VQ-1 — Milestone order. v0.1 follows the preview. It is not an in-place relabel of the preview. design/07 Phase 1 and the ruling packet's "not roadmap v0.1" phrasing are reconciled by the owner.
• OQ-2 / VQ-2 — Async minigames in v0.1. Recommend solo-only for Terminal Typer and the Arcade in v0.1, with ghost races and daily-slot ghosts deferred to the first async successor. D-013 stays in force, and no keystroke-recording data class is created.
• OQ-3 / VQ-3 — Feed content posture. Recommend: server-authored dispatches plus aggregate presence, with NPC-company fallback items that are clearly styled as NPCs. No player names and no user-authored submissions (D-017 stays in force). FD2's submission pipeline is deferred. The feed draft's body must be narrowed in the same edit that records the ruling.
• OQ-4 / VQ-4 — Counters and D-016. Recommend: players online and "production this hour" are public world gauges derived from committed state, with a published formula. They are not gameplay telemetry. The Planet counter ships as WL4's monotone gauge. WL2, WL3 and WL5 stay in v0.2.
• OQ-5 / VQ-5 — The Clout mint conflict. design/02 §6 has achievements grant Clout at 2/4/8. §6b (the Gaia law) says Clout has "exactly ONE mint (social activity)". The shipped Achievements foundation mints nothing. The owner must rule which mint or mints v0.1 ships. PR Interns cannot be specified until then.
• OQ-6 / VQ-6 — design/13 [v0.1] items (X01–X04). In or out? Recommend: X04 and X03 in; X01 and X02 in only if garage-player-surfaces can hold them without a canvas-engine split. Otherwise X01 and X02 get their own diorama RFC.
• OQ-7 / VQ-7 — Events Layer 1 in v0.1? The T1 ideology events and the T2 crunch/layoffs beats need rfc/events-engine-layer1.md, which design/07 places in v0.2. Recommend: out of v0.1, with those beats deferred and listed as deviations in tier2-content.
• OQ-8 / VQ-8 — Pacing targets. design/02 §11 says "first minigame ~2–3 h (Tier 2)". The Arcade (T0) and Terminal Typer (T1) unlock earlier. design/01 T2 also places the first prestige "shortly after" T2. The owner rules which minigame the target measures, and whether the shipped T1 elective-Exit envelope is retained. Recommend: the target measures Server Garden, and the T1 Exit envelope is retained.
• OQ-9 / VQ-9 — Pet scope. Recommend: the starter cat at T0 only, with T2 adoptable variants deferred.

§3 — The RFC DAG

Nodes are RFCs (or named undrafted successors) plus release witnesses. An edge A → B means B cannot be accepted, or cannot complete, until A provides the stated producer.

Edges

D-007 ────────────────────────────────┬─> D-018 ─> accessibility-player-workflows ─┐
VQ-1..VQ-9 (owner) ──> body narrowing of feed/world drafts; clout/pet/cosmetic drafts│
Minigame Platform reconciliation (3a) ─┐                                             │
API ruling reconciliation (3f) ─> API generated client (3g) ─┐                       │
Minigame API ruling reconciliation (3h) ─────────────────────┴─> MA AC5 surface host ┤
Prestige & Exits archival ─> reputation-tree-v1 ────────────────────────────────────┤
tier2-content (+ headcount-allocation split) ─┬─> minigame-server-garden ───────────┤
                                              └─> garage-player-surfaces (T2 era) ──┤
clout-v1-and-pr-interns ─┬─> minigame-server-garden (Clout payload)                  │
                         └─> garage-player-surfaces (Clout/achievement reader)       │
pet-adoption-v1 ─┬─> cosmetic-shop-v1 (pet reaction) ─> garage-player-surfaces       │
                 └─> garage-player-surfaces (pet care/adoption)                      │
minigame-terminal-typer, minigame-demo-disc-arcade ─> MA AC5 host ─> playable        │
world-layer (v0.1 slice) ─> garage-player-surfaces (counters)                        │
feed-and-dispatch (narrowed) ─> ticker-launch-corpus ─> garage-player-surfaces       │
all content RFCs ─> v0.1 content-epoch mint (the First Content Epoch protocol) ──────┤
account recovery/rights successor (D-008/9/15) ──────────────────────────────────────┤
operations/retention contract (D-015) + Deployment Foundation ─> R-006/R-007 ────────┤
                                                                                    v
            integrated v0.1 release evidence (R-003, R-005, R-006, R-007, R-008) ─> owner call

The graph is acyclic. garage-player-surfaces is a sink for the producers, but it is sliced: each surface slice depends only on its own producer. The slices for the implemented backends (Fiscal, Achievements score, Pet Care) can start as soon as Batch A is accepted.

Topological tiers. Nodes in the same tier have no edges between them and can run in parallel.

Tier	Nodes	Kind
L0 — decisions	D-007 adoption; VQ-1…VQ-9; D-008/D-009/D-015; D-018; ruling-author reconciliations 3a (Minigame Platform), 3f (API), 3h (Minigame API)	Owner and ruling-author only. No code.
L1 — in-flight authority	Deployment corrective review and DP-F; API 3g generated client; Prestige archival; CI Baseline closeout; accessibility-player-workflows acceptance (after D-018); draft the account recovery/rights successor and the operations/retention contract	Accepted/implementing work plus floor drafting
L2 — independent producers	tier2-content (+ headcount-allocation if split); reputation-tree-v1; clout-v1-and-pr-interns; pet-adoption-v1; minigame-terminal-typer (engine); minigame-demo-disc-arcade (engine); world-layer-foundation v0.1 slice; feed-and-dispatch-foundation (narrowed); MA AC5 surface host; garage-player-surfaces slices over already-live backends (Fiscal, achievements score, pet care)	Maximum parallelism. Each is fixture-first, like the First Content Epoch foundations.
L3 — dependent producers	minigame-server-garden (needs T2 gate IDs and Clout payload); cosmetic-shop-v1 (reaction needs pet identity); ticker-launch-corpus; garage-player-surfaces slices for T2 era, Reputation tree, Clout, adoption, counters, feed/ticker and minigame hosting	—
L4 — mint and pacing	v0.1 content epoch (epoch 9 or later) under the First Content Epoch protocol; T0–T2 harness pacing scenario (G03/OQ-8 targets, Earnings Call day-2)	Owner-gated mint
L5 — release evidence	R-005 (all v0.1 tasks), R-008 (v0.1 first session including T2 and one minigame), R-003, R-006/R-007 on the exact v0.1 bundle, designated cross-party verdicts covering every range, owner release call	—

Critical path (longest chain): 3f → 3g generated client → 3h → MA AC5 host → minigame surfaces → epoch mint → R-005/R-008 → release. This chain runs in parallel with the rights chain D-008/D-009/D-015 → account successor → R-003. Either chain can be the binding one; both are blocked today on owner or ruling-author action, not on implementation.

§3b — Proposed acceptance batches (for Marco)

The batches are ordered for the most parallel implementation. An RFC is accepted only after its blocking questions are ruled and its body is reconciled to those rulings. No batch skips a designated cross-party review.

• Batch 0 — rulings, no RFC acceptance. D-007 (adopt the preview manifest); VQ-1, VQ-2, VQ-5, VQ-7, VQ-8 (which unblock Batch A); and the three ruling-author reconciliations 3f, 3h and 3a (which unblock the MA AC5 minigame host). D-018 follows D-007.
• Batch A — independent producers; accept together. tier2-content (with headcount-allocation split out if its body is catalog-only), reputation-tree-v1, minigame-terminal-typer, minigame-demo-disc-arcade, and garage-player-surfaces limited to its already-live-backend slices: Fiscal/Earnings Call, the achievements-score reader and pet care. accessibility-player-workflows is accepted alongside once D-018 is ruled, because every surface consumes its floor. These have no edges between them, so four or five implementation streams can start at once, all fixture-first.
• Batch B — after the Batch 0 rulings and the new drafts. clout-v1-and-pr-interns (after VQ-5), pet-adoption-v1 (after VQ-9), feed-and-dispatch-foundation (body narrowed per VQ-3, with the NPC fallback added), and the world-layer-foundation v0.1 slice (narrowed per VQ-4). These can be accepted in parallel with Batch A's implementation.
• Batch C — dependents. minigame-server-garden (needs Batch A's T2 gate IDs and Batch B's Clout payload contract), cosmetic-shop-v1, ticker-launch-corpus, and the remaining garage-player-surfaces slices.
• Batch F — floor, on its own track, needed before release, not before content. The account recovery/rights successor (after D-008/D-009/D-015) and the operations/retention contract. This track runs concurrently with A–C and gates only L5.
• Batch M — the v0.1 content-epoch mint. Last. It is accepted only when every content RFC above has a designated-approved fixture-first implementation.
• Not in v0.1. events-engine-layer1 (unless VQ-7 rules otherwise) and leaderboard-readers-and-player-surface (speedrun chrome is v0.3 in design/07; the local splits already shipped are sufficient). Neither is withdrawn; both stay independent drafts.

§4 — Exit criteria for v0.1

v0.1 is complete only when every criterion below holds at one release artifact. Each one uses the eight dimensions of planning/roadmap-1.0.md §What counts as done. An archived foundation or a green unit suite never satisfies a row on its own.

• EC-1 Preview floor. P01–P07 and F01–F05 are proven on the v0.1 bundle, not inherited from a preview run.
• EC-2 Manifest completeness. Every in-scope G and X row has four things. (1) An implemented, archived owning RFC with canonical docs/. (2) A real producer → generated-client API → mounted surface → pinned content path. (3) A composed browser workflow witness that fails when its producer is severed (evidence discipline 1). (4) A recorded cross-party designated verdict whose ranges union to the full span. Out-of-scope rows appear in the owner-ruled exclusion list, and none is silently dropped.
• EC-3 Pacing. The harness passes the adopted T0–T2 targets as acceptance gates (design/07 principle 1). Those targets are: first generator < 60 s; T1 about 15 min; first elective Exit 45–90 min for Chaos p50 and Casual p95; run-2 Garage strictly faster; the OQ-8 first-minigame target; the tier2-content T2 target; Earnings Call day-2. Measurement is fail-loud, with no guard-terminated runs (evidence discipline 3).
• EC-4 Laws. The following are each proven by a negative test. There is no real-money path anywhere; the $0.00 shop and Horse Armor carry their curtain-pull disclosure. Every cap is a visible hardcap. Offline progress applies at the default 90%/24 h. The feed and counters work with zero players online through the NPC fallback, and bots and NPCs pass the same validation. The Clout mint matches the OQ-5 ruling, and a seeded second faucet is rejected. The pet layer is reviewed as sincere.
• EC-5 Rights and data. Every new v0.1 data class (cosmetic ownership, pet records, Garden collections, minigame sessions, any ghost data if OQ-2 admits it) appears in the D-008 export schema, the D-009 deletion disclosure and the D-015 retention policy, with a joined deletion witness.
• EC-6 Accessibility. R-005 passes for every v0.1 task under the D-018 matrix. That includes minigame play, the tier-up ceremony (with reduced motion), and ticker announcements, which must not flood AT live regions.
• EC-7 Satire and content. The "small business opens its doors" beat is present across T0–T2, the shop and the ticker. Every real-world statistic traces to a design/research/ citation. Nothing on a research file's verify-before-shipping list ships as fact. The Arcade uses mechanics only, with no trade dress or names. All player copy is owner-adopted.
• EC-8 Comprehension. R-008 is re-run on the v0.1 first session, including the T2 allocation decision and at least one minigame. It meets the R-008 thresholds.
• EC-9 Operations. R-006 and R-007 pass on the exact v0.1 candidate and previous bundles. That includes a save migration across the v0.1 epoch.
• EC-10 Canon. The RFC index, docs/, the roadmap board and the execution queue agree with HEAD. Marco makes an explicit release call.

Deviations from design

• Sequencing. design/07 makes v0.1 "first public". The adopted D-001/D-007 rulings put the Phase-0 Preview ahead of it. This manifest follows the rulings and asks the owner to reconcile design/07 (OQ-1).
• Scope additions. Rows X01–X04 add design/13 items that design/07 omits. Their inclusion is an owner choice (OQ-6), not assumed.
• Recommended narrowings. These are recommendations only and apply only if ruled: solo-only minigames (OQ-2), no Events L1 (OQ-7), starter-cat-only pets (OQ-9), and world-layer WL1+WL4 only (OQ-4). Each ruled narrowing becomes a named deviation in the owning RFC.

Acceptance criteria (for this manifest RFC)

• MC-1 Every design/07 Phase-1 item and every design/13 [v0.1] item has a row with an evidence path that resolves at the acceptance HEAD. A mechanical check of this is part of the plan, and it must fail when a row or path is removed.
• MC-2 The manifest is re-reconciled against the actual bodies of the six new drafts. Every UNOWNED item is either claimed by a named accepted or draft RFC or recorded as an owner-ruled exclusion.
• MC-3 VQ-1 through VQ-9 are ruled (or promoted to D-IDs and ruled), and the rulings are reflected in the §1 rows and in the owning drafts' bodies in the same edit.
• MC-4 The DAG is validated as acyclic. Each edge names the producer it waits on.
• MC-5 Evidence discrepancy E-1 is routed to the Fiscal docs owner.

Open questions and evidence discrepancies

• OQ-1 … OQ-9 are listed in §2.
• E-1. docs/fiscal-quarters.md lines 3–5 say no production epoch contains the fiscal artifact. balance/epochs/phase0.json and rfc/first-content-epoch.md say it is registered and minted. The docs page is canonical, so this is a docs bug under RFC-0000 §Docs conventions. It is not fixed here because this draft modifies no other file.
• E-2. rfc/feed-and-dispatch-foundation.md omits the NPC-company fallback that design/05 §2 requires (law 6). Its FD2 user-submission pipeline conflicts with D-017's preview deferral. The draft's author reconciles its body when OQ-3 is ruled.
• E-3. The Clout mint conflict between design/02 §6 and §6b (OQ-5).

Changelog

• 2026-09-25: created (draft — not implementation authority), from a static trace at c2d9bbc.

Owner acceptance (2026-09-25)

Marco accepted this RFC in the 2026-09-25 batch (the answer to a direct batch question in-session, recorded by Claude). Every owner decision this RFC lists is ruled at its stated recommended default. Where the text offers alternatives, the recommended option is the normative one and the alternatives are rejected. Provisional numbers stay provisional and are ratified by harness measurement and SHA, as the RFC already requires. Owner-authored copy stays owner-authored: implementation ships copy keys, with any placeholder or candidate text clearly marked.