Active implementation specifications. Process: 0000-rfc-process.md. New RFCs start from
template.md; descriptive names are preferred over global sequence numbers.
| RFC | Status | Parent |
|---|---|---|
| RFC-0000: The RFC Process | accepted | — |
| Balance Harness Dispatch Integrity | withdrawn — premise refuted | Balance Harness Foundation |
| CI Baseline | implementing | — |
| Reputation Harness Observability | draft — RP-634 fixture profile and existing CI artifact floor; not implementation authority | Harness Observability / CI Baseline / Reputation Tree v1 |
| Kernel History Guard Integrity | draft — RP-131, owner choice pending; not implementation authority | Run Genesis & Replay KV-1 / CI Baseline |
| Numeric Diagnostic Exponent Limits | draft — RP-663 beyond-int64 diagnostic exception proposed; normative review/adoption pending; not implementation authority | Numeric Core / Numeric Core Boundary Hardening |
| Exact Represented Aggregation | draft — RP-664 exact operation, pinned exceptions and producer/capacity cutover proposed; normative review/adoption and workload proof pending; not implementation authority | Deterministic Decimal Aggregation / Economy / Commons / Harness |
| Account & Session Bootstrap | implementing | Save Layer |
| Account Recovery Player Flow | draft — D-005 posture ruled; player flow, local credential migration and copy proposed, not implementation authority | Account / archived Game UI / API Foundation |
| Browser Session Renewal & Recovery | draft — RP-048/RP-234 consumer diagnosed; policy/API/browser gates unaccepted | Account / Transport / API Foundation / archived Game UI |
| Game UI First-read Failure & Recovery | draft — RP-342 measured; startup precedence/retry/copy unaccepted; not implementation authority | Garage Player Surfaces / archived Game UI / API Foundation / Account |
| Monotonic Founder Attendance | draft — RP-365 reproduced; D-024 shared-clock boundary unruled | Founder Attendance / Pet Care & Adoption / Garden / Minigame Platform |
| WebSocket Transport & Fan-out | implementing | Production Engine / Client Shell / Account Bootstrap |
| Leaderboards & Balance Epochs | implementing | Production Engine / Gate Predicates / Prestige |
| Leaderboard Readers & Player Surface | draft — not implementation authority | Leaderboards / API Foundation / Game UI / Route Registry |
| Prestige & Exits | implementing | Production Engine / Save Layer / Account Bootstrap |
| API Foundation | accepted — C1–C20 ruled; implementing | Account API / Transport / Gameserver Composition |
| Artifact Schema Ownership & Kernel-neutral Delivery | draft — Route companion and exact reviewed descriptor-only scope proposed; not implementation authority | API C17/C18 / Route C2 / Kernel History Guard Integrity |
| Typed Dictionaries in API Schemas | draft — RP-391, preserve-receipt option proposed; owner choice/review pending | API Foundation C17 / existing intent receipts |
| Explicit Integer Token Encoding in API Schemas | draft — RP-566; measured representation proposal, adoption/review pending; not implementation authority | API Foundation C17/C18 / relevance owner grammar |
| Original Artifact Bytes in Catalog Transport | draft — RP-597/RP-598; owner lexical boundary and exact-byte recovery proposed, not implementation authority | API Foundation C12/C17/C18 / artifact owners |
| Bodiless Responses in the API Registry | draft — RP-483, existing204/304 representation proposed; owner adoption/review pending | API Foundation C19 / Account lifecycle / public caching |
| Minigame Platform Foundation | accepted — C1–C40 ruled; implementing | Gameserver Composition / Founder Attendance / Combat |
| Combat Shared Data & Arithmetic | implementing | — |
| Combat — Duel Engine | draft | Combat Shared Data |
| Combat — Lane Engine | draft | Combat Shared Data |
| Combat — Bots & Integration | draft | Combat engines / Account Bootstrap |
| Commons Onboarding & Governance | draft — dependency foundations available; ballot/cohort contracts still unclosed (RP-529; readiness) | Commons Compact |
| World Layer Foundation | draft | Commons / Production / Save |
| Feed & Dispatch Foundation | draft | Transport / Production / Clout |
| Events Engine — Layer 1 | draft | Production / Save / Meters |
| Minigame & Recovery API + Surface | accepted — MA-C1–C15 ruled; implementing | API Foundation / Minigame Platform (accepted, implementing) / Soul / UI Foundation |
| Minigame Tenant HTTP Bindings | draft — engineering specification ready for normative review; adoption/parent bodies/review and Typer author holds remain; not implementation authority | API Foundation C2 / Minigame API / Terminal Typer TT-PA4 / Deployment DP5 |
| Permits & the T3→T4 Gate | promoted in reviewed epoch 6; archival pending | Economy Kernel / Route Registry / First Content Epoch |
| First Content Epoch | epoch 6 minted and designated-approved; dependent archival in progress | ALL fixture-first content foundations |
| Deployment Foundation | implementing — accepted at cd102d7 |
Gameserver / Client / Account / API / CI / operations |
| Current Release Authority & Interrupted Transitions | draft — RP-558/DESIGN-GAP10; proposal, pinned-engine mechanical evidence/adoption/review pending; not acceptance-ready | Deployment DP5 / operator ledger / R-006 |
| Backup Protection Metadata Binding | draft — RP-505 signed-v2/authenticated-legacy-copy proposal; adoption/review pending | Deployment DP6 / retention |
| Accessibility of Player Workflows | draft — current Game UI failures measured; owner task/AT matrix pending | UI Foundation / Game UI Screens; later surface RFCs consume its acceptance floor |
| v0.1 "The Garage" — Release Manifest & RFC DAG | accepted 2026-09-25 (recommended defaults); implementing | design/07 Phase 1 |
| Reputation Tree v1 | accepted 2026-09-25 (recommended defaults); implementing | Prestige & Exits / Leaderboards & Epochs |
| Minigame — Terminal Typer | accepted 2026-09-25 (recommended defaults); implementing | Minigame Platform / Minigame API & Surface |
| Minigame — Demo Disc Arcade | accepted 2026-09-25 (recommended defaults); implementing | Minigame Platform / Minigame API & Surface |
| Minigame — Arcade Pinball | draft — not implementation authority; owner-requested addition (not in design/03), OD-P1–P15 | Demo Disc Arcade / Minigame Platform |
| Tier 2 Content — IT Company | accepted 2026-09-25 (recommended defaults; seat source OD-1 held); implementing | Economy Kernel / Routes / Balance Harness |
| Minigame — Server Garden | accepted 2026-09-25 (recommended defaults); implementing | Minigame Platform / Fiscal / Tier 2 |
| Garage Player Surfaces | accepted 2026-09-25 (recommended defaults); implementing | Game UI Screens / Fiscal / Achievements / Meters / Pet / Active Play / Minigame API |
| Clout v1 & PR Interns | accepted 2026-09-25 (recommended defaults); implementing | Achievements / Economy Kernel |
| Production Accrual Conservation | draft — operation-local proposal; caller/compatibility closure and adoption/review pending | Production Engine / Clout / Save Layer |
| Accrual-aware Harness Search | draft — producer/consumer scope split; caller/boundary/dispatch closure and adoption/review pending | Production Accrual Conservation / Relevance R10–R11 / first-hour and content diagnostics |
| Cosmetic Shop v1 — Horse Armor | accepted 2026-09-25 (recommended defaults); implementing | Game UI / Save Layer / Pet |
| Pet Adoption v1 | accepted 2026-09-25 (recommended defaults); implementing | Pet Care / Save Layer / Game UI |
| Ticker Launch Corpus | accepted 2026-09-25 (recommended defaults; blocked on Feed VQ-3); implementing | Feed & Dispatch / Copy Pipeline |
| Headcount Allocation | accepted 2026-09-25 (recommended defaults; seat source OD-1 held); implementing | Economy Kernel / Tier 2 Content |
Current handoff: planning/platform-alignment/execution-queue.md
— the evidence-derived READY/BLOCKED queue at HEAD. The older July batch manifest is history,
not current authorization.
Coverage map: planning/archive/coverage-map/ preserves the
2026-08-05 historical sweep as a frozen, noncanonical snapshot. Use the platform-alignment
capability and active-RFC audits for current status.
Implemented behavior lives in docs/; these frozen RFCs are historical specifications.
Phase-0 contract status (reconciled 2026-08-05 against the coverage-map sweep): the contracts previously listed here as "not yet drafted" — Layer-1 events engine, doctrine intents, Compute Credit spend, game-UI screens, deployment — now all exist as draft RFCs (in the Active table above; drafted 2026-08-03). Remaining structural notes: Prestige & Exits owns the reset; Leaderboards owns board binding; doctrine intents must define doctrine-pick ordering before same-boundary doctrine routes can ship. Later named work: an outcome-sensitive near-cap Guild reserved-credit regression before either a nonzero stock-consumption modifier or multi-worker clearing topology ships.
The still-uncontracted (design-only) systems were counted as ~28 in the 2026-08-05 coverage
sweep (individual minigames, monetization-satire content, narrative, tiers 2–8). Its internal
planning/archive/coverage-map/gap-backlog.md
retains the historical dependency analysis as a tracked, frozen snapshot. Do not treat either its
count or queue as current authority.
RFC-0002's re-scope to the Economy Kernel correctly narrowed it to what was implementable. The remaining deferred decisions retain named successors so defaults are not chosen silently during later implementation:
| Deferred decision | Origin | Named owner | Why it matters |
|---|---|---|---|
| Leaderboard/ranking order keys — ✅ resolved in Leaderboards & Balance Epochs D1 (exact integer/time keys; magnitude ties remain ties) | RFC-0002 draft D4 | owned | 12-digit quantization makes runs differing below the 12th digit indistinguishable, in a game framed around world records |
Minimum visible increment — ✅ resolved in Client Shell & Sim Loop D3 (interpolate at full precision, sub-unit accumulation, cap shows reason_key) |
RFC-0002 draft D6 | owned | A frozen number with no explanation is indistinguishable from a bug, and design/00 forbids unexplained caps |
| Client reconciliation policy — ✅ resolved in Client Shell & Sim Loop D2 (bend continuous, snap discrete with receipts, story-not-error for gaps) | was a design/06 table cell |
owned | The most player-visible consequence of RFC-0001's whole numeric contract |