Status: proposed · ADR-2 · Filed 2026-04-17
Decision
Closing a retro via prism_retro(action=create, status=closed) should automatically advance the project’s phase field to the phase string on the retro. Optionally: bump to a ‘next phase’ registry entry if one exists.
Rationale
PID-PGR01 has four closed retros (Phase 0, 2, 3, 3.5) but project.phase still reads ‘Phase 0’. Phase-as-metadata and phase-as-reality have diverged by four phases. Retros are the natural phase-close event; the write already happens at that boundary. Auto-advancing eliminates a whole class of ‘forgot to update’ drift.
Alternatives Considered
Add a separate ‘phase’ verb. Require explicit prism_context(update=…) at retro close. Do nothing, accept phase-as-metadata drift.
