AI-Assisted Sprint Retro Runs Itself, Flags Lessons as Unverified Until Reviewed

A software developer running a structured AI-assisted development workflow called 'The Contract' completed its final phase, Reflect, without scheduling a traditional retrospective meeting. Unlike earlier phases, Reflect did not allow lessons to be filed directly as knowledge — instead, every proposed lesson is tagged 'propose-only' and held in a raw file until manually promoted. This design prevents same-day conclusions from being treated as settled facts in future development cycles. During the reflection, the developer discovered that a rollback trigger they believed was added late in the process had actually originated in the planning phase, correcting a memory-based assumption. The experience highlighted a core distinction the phase enforces: separating what a developer actually knows from evidence versus what they simply remember feeling.