Reinforcement Learning
Transformers
English
post-training
distillation
agentic-coding
composer-2.5
cursor
kimi-k2
grpo
dapo
diloco
openenv
trl
verl
research
methodology
Instructions to use Codeseys/composer-replication-framework with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Transformers
How to use Codeseys/composer-replication-framework with Transformers:
# Load model directly from transformers import AutoModel model = AutoModel.from_pretrained("Codeseys/composer-replication-framework", dtype="auto") - Notebooks
- Google Colab
- Kaggle
| # docs/research/_archive — historical research reviews | |
| This directory holds **research-flavored, point-in-time** documents: the | |
| cross-model adversarial wave reviews and recon audits that critiqued the | |
| framework at a specific commit. They are preserved **verbatim for provenance** | |
| and are **not** maintained as current truth. | |
| > **What's current instead.** For live research/methodology, read | |
| > [`docs/METHODOLOGY.md`](../../METHODOLOGY.md), the standing reconnaissance and | |
| > landscape notes still in [`docs/research/`](../), and the accepted ADRs under | |
| > [`docs/adrs/`](../../adrs/README.md). For the live framework state, see | |
| > [`docs/OVERVIEW.md`](../../OVERVIEW.md) and [`BACKLOG.md`](../../../BACKLOG.md). | |
| > Where an archived review and a current doc disagree, the current doc wins. | |
| Each archived `WAVE_*_FINAL_REVIEW.md` file's original path under | |
| `docs/research/` still contains a one-line **redirect stub** so older prose | |
| references (e.g. ADR-007's citation of Wave-13 "Finding 2") keep resolving. | |
| ## Contents | |
| | Archived file | Original path | What it is | Superseded by | | |
| |---|---|---|---| | |
| | [`WAVE_7_10_FINAL_REVIEW.md`](WAVE_7_10_FINAL_REVIEW.md) | `docs/research/WAVE_7_10_FINAL_REVIEW.md` | Cross-model adversarial check of Waves 7–10 | `docs/METHODOLOGY.md`; `docs/V1_V8_COVERAGE.md` | | |
| | [`WAVE_13_FINAL_REVIEW.md`](WAVE_13_FINAL_REVIEW.md) | `docs/research/WAVE_13_FINAL_REVIEW.md` | Wave 13 adversarial cross-model review (ADR-007 cites Finding 2) | ADR-007; `BACKLOG.md` | | |
| | [`WAVE_14_FINAL_REVIEW.md`](WAVE_14_FINAL_REVIEW.md) | `docs/research/WAVE_14_FINAL_REVIEW.md` | Wave 14 adversarial cross-model review | `docs/TROUBLESHOOTING.md`; `BACKLOG.md` | | |
| | [`WAVE_15_FINAL_REVIEW.md`](WAVE_15_FINAL_REVIEW.md) | `docs/research/WAVE_15_FINAL_REVIEW.md` | Wave 15 multi-angle self-critique + fix wave | `docs/V1_V8_COVERAGE.md`; `BACKLOG.md` | | |
| | [`WAVE_16_RECON_AUDIT.md`](WAVE_16_RECON_AUDIT.md) | (already archived here) | Wave 16 reconnaissance audit of the recon/landscape docs | the recon/landscape docs it audited | | |
| ## Why archive instead of delete | |
| These reviews are the framework's adversarial audit trail — they record which | |
| claims were challenged, which were fixed, and which were left open. Several | |
| accepted ADRs cite them by path. Archiving (rather than deleting) preserves the | |
| provenance and keeps those citations resolvable, while signalling that the | |
| reviews are snapshots superseded by the current methodology and coverage docs. | |
| > Non-research point-in-time artifacts (wave logs, the dated cross-family / | |
| > final-verify review bundles) live in the sibling | |
| > [`docs/_archive/`](../../_archive/README.md) instead. | |