fred
bc1149c15e
- docs/PRD.md: Part I product north star authored from ratified decisions D1-D14; Part II preserves all active workstream contracts verbatim (KBN-101, FCM #758, FCOM #766, TESS, #756, MOS-PORT, #1150, #1174, #1194, RI #1275, M1). Referenced anchors unchanged. - docs/archive/PRD-v0.1.md: v0.1.0 beta PRD body archived verbatim with supersession header. - docs/ROADMAP.md: all phases P0-P5 present from day one per D11 (P2-P5 as explicit placeholders). - docs/requirements/native-kanban-sot.md: Amendment A1 (D13) - hierarchy parentage + RBAC chain above workspaces; sections 1-7 untouched.
Documentation Archive
Status: Current archive index. Pages linked here are historical or superseded and are not current product, operator, or developer guidance.
Use docs/README.md for current placement and source-of-truth rules. Historical pages remain discoverable here only when retaining their context is useful; each migration should identify a replacement or explain why the record is retained.
Archived TUI workstream
The following branch-specific records are retained because their implementation claims and worktree paths no longer match the current checkout:
TUI improvements PRD— historical Phase 7 requirements; it names the deletedpackages/clipackage.TUI improvements task ledger— historical task/status record; its relative PRD link remains valid within this archive directory.
Do not use these pages as instructions for the current TUI. Current TUI implementation is under packages/mosaic; any new requirements require a separately approved plan or PRD.
Archived missions
Mission archive index— completed and superseded CLI, harness, install UX, and storage-abstraction mission records.
Archived mission manifests and task ledgers preserve their original status and context. They do not replace current orchestrator-owned docs/TASKS.md or authorize old installation procedures.
Archived planning
Planning archive index— historical briefs, reviews, and work-package specifications.Monorepo consolidation bundle— prior Forge, MACP, and framework-plugin consolidation planning. Current package existence does not validate every historical criterion.
Archived work records
Work-record archive— unreferenced historical task scratchpads retained as evidence, not active status or guidance.
Retention rules
- Preserve historical wording unless a migration task explicitly requires a rewrite.
- Label replacements and current status in the owning index rather than silently reviving archived claims.
- Do not link archive pages from current workflow instructions as if they were current.