Codeseys/composer-replication-framework

1# docs/_archive — historical, point-in-time artifacts2 3This directory holds **non-research** documents that captured the state of the4project at a specific moment (wave logs, dated cross-family review bundles).5They are preserved **verbatim for provenance** and are **not** maintained as6current truth.7 8> **What's current instead.** For the live state of the framework, read9> [`docs/OVERVIEW.md`](../OVERVIEW.md), [`README.md`](../../README.md),10> [`BACKLOG.md`](../../BACKLOG.md), [`docs/METHODOLOGY.md`](../METHODOLOGY.md),11> [`docs/V1_V8_COVERAGE.md`](../V1_V8_COVERAGE.md), and the accepted ADRs under12> [`docs/adrs/`](../adrs/README.md). Where an archived doc and a current doc13> disagree, the current doc wins.14 15Each archived file's original path still contains a one-line **redirect stub** so16that older prose references (including those baked into immutable accepted ADRs)17keep resolving.18 19## Contents20 21| Archived file | Original path | What it is | Superseded by |22|---|---|---|---|23| [`WAVE_COMPOSER_DATAGEN_RL_2026-05-29.md`](WAVE_COMPOSER_DATAGEN_RL_2026-05-29.md) | `docs/WAVE_COMPOSER_DATAGEN_RL_2026-05-29.md` | Wave log: Composer datagen + targeted-RL textual-feedback work, 2026-05-29 | ADR-008, ADR-009, ADR-010, ADR-014; `BACKLOG.md` |24| [`DEEP_WORK_LOOP_LOG.md`](DEEP_WORK_LOOP_LOG.md) | `docs/DEEP_WORK_LOOP_LOG.md` | Running log of deep-work-loop sessions | `docs/METHODOLOGY.md`; `BACKLOG.md` |25| [`reviews/cross-family-adr-008-009-010-2026-05-29/`](reviews/cross-family-adr-008-009-010-2026-05-29/) | `docs/reviews/cross-family-adr-008-009-010-2026-05-29/` | 5-family adversarial review of ADR-008/009/010 (SYNTHESIS + 4 per-model reviews) | ADR-008 / ADR-012 acceptance records |26| [`reviews/final-verify-deep-work-2026-05-29/`](reviews/final-verify-deep-work-2026-05-29/) | `docs/reviews/final-verify-deep-work-2026-05-29/` | Phase-8 final cross-family verify (SYNTHESIS + per-model verifies) | accepted ADRs; `BACKLOG.md` |27 28## Why archive instead of delete29 30These documents record *how the decisions were reached* — the adversarial31findings, the wave-by-wave reasoning, the cross-model disagreements. That32provenance is valuable for anyone auditing the framework's claims, and the33accepted ADRs cite these paths by name. Deleting them would orphan those34citations and erase the audit trail. Archiving keeps the trail intact while35making clear they are snapshots, not the live spec.36 37> Research-flavored point-in-time reviews (the `WAVE_*_FINAL_REVIEW.md`38> cross-model audits and the Wave-16 recon audit) live in the sibling39> [`docs/research/_archive/`](../research/_archive/README.md) instead.40