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 deleted packages/cli package.
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.