Last reconciled: 2026-02-20
This document is the "don't panic" map for readers who open older design/migration specs and see ambitious target lists.
Use these as source of truth for current status and active backlog:
bd status/bd readydocs/execution-plan/STATUS.mddocs/execution-plan/TASK-REGISTRY.mddocs/execution-plan/WORKBOARD.md
| Document | Role in lineage | How to read checklist lines |
|---|---|---|
docs/implementation-roadmap.md |
Original sequencing model for rlm-core + formal verification rollout | [historical target] = archived target from planning era, not active backlog |
docs/unified-rlm-library-design.md |
Foundational architecture intent and phase plan | [historical target] = archival design target |
docs/lean-formal-verification-design.md |
Lean/spec-agent system design intent | [historical target] = archival acceptance target |
docs/migration-spec-rlm-claude-code.md |
Migration target-state design plus later reality adjustments | [historical target] = original migration target; see migration reality and Beads for actual achieved scope |
docs/migration-spec-recurse.md |
recurse migration planning artifact | [historical target] = archived phase exit target; authoritative outcome is tracked in Beads and execution-plan status |
Not every unchecked box means "unfinished engineering work."
docs/troubleshooting/diagnostics-checklist.mdis intentionally a blank incident-response form.- It uses unchecked boxes by design and should not be interpreted as implementation debt.
Where historical target state exceeds currently exposed APIs (for example full Python-orchestrator replacement surfaces not exposed in bindings), status is intentionally documented as out-of-scope/deferred in the migration specs and execution-plan records, not silently treated as complete.