Repository navigation
docs: the production-readiness roadmap, adversarially audited - #79
Merged
Merged
Conversation
The comparison plan (#73, #75, #76, #77) and its follow-up (#78) closed; this is the plan for what the family's plans and ledgers still carry open, sequenced into twelve weeks in three blocks, with "production-ready" defined as a thirteen-row checklist per engine so the verdict can be checked rather than believed. Drafted and then audited by two independent adversarial reviews (one against the trees' facts and settled decisions, one against engineering judgement). The audit changed the draft materially: the book's bridge chapters are done (#68), so they are off the list; rational has no cross-engine validation by design (scipy and decimate.h are its legs); TSan runs async only; four host compilers and three QEMU targets, not the draft's counts; the +1.9 % M55 ratio23_q15_eco drift is ab8fea3's stated move, not a DspTap bump, and the chain rows sit +926/+1,102; the hardware block never ran bridge or rational on silicon; nothing builds with -fno-exceptions; TSan has never seen the converter with two threads; no footprint, stack or worst-single-call figure exists; Setup 1's "< 1 ppm" criterion tests the counting, not the servo, and cheap USB dongles may not own a crystal; the timestamp servo is a four-to-five-week extension, not an overload, and must not be frozen in the release that adds it; "C ABIs frozen" needs a reconciled NULL model, an extension rule, SOVERSION and a compat test. Section 7 holds the six decisions the maintainer takes before week 1, each with a recommendation. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01G3HxzEGiZp7jStoMuYNuBK
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this changes
Adds
docs/ROADMAP.md: the plan for what the family's plans and ledgers still carry open after the comparison plan (#73, #75, #76, #77) and its follow-up (#78), sequenced into twelve weeks in three blocks (contracts and hygiene; the hardware campaign; the 1.0 shape), with "production-ready" defined as a thirteen-row checklist per engine. The root README'sdocs/line names it.Why
The open items are scattered across
PLAN.md,async/PLAN.md§4,async/docs/PERFORMANCE.md"Known debt",async/docs/HARDWARE_TESTING.md,bridge/PLAN.md§9 anddocs/AUDIT_2026-10_PLAN.md, with no sequence and no stated bar. The roadmap gives both, so the production-readiness verdict can be checked row by row rather than believed.The draft was adversarially audited by two independent reviews before it was written down (one against the trees' facts and settled decisions, one against engineering judgement); the commit message lists what the audit changed. Section 7 holds the six decisions the maintainer takes before week 1, each with a recommendation; the maintainer's answers are folded in as "decided" on this PR before it merges.
Verification
Prose only: no code, no build. Every tree fact in section 1 was checked against
mainat c120bc9 (v0.6.0). The A1 numbers (rational's thirteen streaming rows, per target) are the local harness's reading againstrational/bench/baselines.json, which reproducesbridge's andasync's M55 rows exactly; they are re-measured in the A1 PR before anything is re-recorded.Notes for the reviewer
🤖 Generated with Claude Code
https://claude.ai/code/session_016GKzq1VSdcMYCRMhddiMaf
Generated by Claude Code