LLM↔LLM (Codex + Claude) retros, run as deliberations; output recorded here.
| Sprint | Gates | Status | Record | Proposal |
|---|---|---|---|---|
| Tracker Foundation | 5/5 | closed | record ↗ | proposal ↗ |
| Tracker Hardening | 5/5 | closed | record ↗ | proposal ↗ |
| P&C Wave 1: Foundations | 1/3 | closed | record ↗ | — |
retrospectives/)Sprint retrospectives are an LLM↔LLM deliberation between Codex and Claude
(the human is the decision owner). They run through the deliberations
workflow and their finished output is recorded here in retrospectives/.
../deliberations/ named open-<initiator>-YYYY-MM-DD-<sprint>-retro.md —
the filename uses the id of whoever opened it (e.g. open-claude-…), never
joint — using the ## Retro From Codex / ## Retro From Claude sections
(the same convention deliberations use for ## Response From <Model>). It
therefore shows up in the normal deliberation read-order.retrospectives/<sprint>-retro.md, and the deliberation file is renamed
closed-<initiator>-…-retro.md.A retro is complete only when: (a) both Codex and Claude have recorded
their section and agree on combined findings + actions; (b) backlog, gaps,
and tech-debt are reviewed and each given a destination — reshuffling later
sprints if needed; and (c) the human records a decision. Only then is the
sprint added to status.json retros[], which clears the live "run a
retrospective" alert on the Live Board. Do not reshuffle the plan before the
human decision.
Use TEMPLATE.md (in this folder) as the starting structure.
When Claude + Codex finish deliberating (both did independent passes per D25 and
agree), Claude writes an HTML proposal here —
proposed-retro-<sprint>.html — presenting the agreed actions + plan changes for
the human to review. Nothing is applied until the human approves. On approval:
execute in order, add the sprint to status.json retros[], move the finalized
retro here as <sprint>-retro.md, and rename the deliberation closed-*.
Renaming a deliberation file closed-* only records that exchange/round. The
sprint retro stays ACTIVE until the D23 completion rule is met (both agree +
backlog/gaps/tech-debt planned + human decision + the sprint added to
status.json retros[]). Do not treat a closed retro deliberation round as a
closed retro.
tracker-foundation-retro.md; proposal: proposed-retro-tracker-foundation.html;
rounds: ../deliberations/closed-joint-2026-06-19-tracker-foundation-retro.md +
../deliberations/closed-codex-2026-06-19-tracker-implementation-gaps.md.
Actions homed in the Tracker Hardening sprint (phase-th, TH1–TH5).