Summary
Implement categorical retrospectives as described in semiotic-project-management §3.7: reviewing whether the system’s categories still fit, not just whether processes worked.
Motivation
Retrospectives are specified in semiotic-project-management but have never been conducted. The spec defines three review dimensions: semantic (do categories fit?), syntactic (do operators cover the work?), and fusion (are there redundant operations?). Zero retrospectives have been done.
Steps
- Define retrospective trigger (cycle boundary or monthly cadence).
- Create a retrospective template (what questions to ask, where to record answers).
- Conduct first retrospective on the current session’s work.
- Record findings as a text or decision record.
- Act on at least one finding.
Done when
- Retrospective template exists
- At least one retrospective conducted and recorded
- At least one finding acted on
Dependencies
- Plan 0023 (cycle workflow) — retrospectives happen at cycle boundaries
Log
2026-03-08 — Created from gap analysis. Retrospectives are one of 12 researched PM practices with zero application.