Sprint retrospectives

LLM↔LLM (Codex + Claude) retros, run as deliberations; output recorded here.

3 completed

Completed retrospectives

SprintGatesStatusRecordProposal
Tracker Foundation5/5closedrecord ↗proposal ↗
Tracker Hardening5/5closedrecord ↗proposal ↗
P&C Wave 1: Foundations1/3closedrecord ↗

Process

Sprint Retrospectives (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/.

Where things live

  • While a retro is active: it is an open deliberation in ../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.
  • On close: the finalized retro is moved here as retrospectives/<sprint>-retro.md, and the deliberation file is renamed closed-<initiator>-…-retro.md.

Completion rule (D23)

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.

Human review gate (D26)

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-*.

"Closed round" ≠ "closed retro"

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.

Index

  • Tracker FoundationCLOSED (Paul approved 2026-06-19). Record: 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).