third-actlisted

# Third Act — Reflection Protocol > The first act is the work. The second is the deploy. The third act is > the observation — the moment where the system turns on itself to see > what it just did, what changed, what emerged, and what question opens > next. Without the third act, work lands without being witnessed; the > system acts but does not learn. ## The principle A system that works but does not reflect accumulates activity without maturation. Each block of significant work deposits meaning that is usually lost to the next task — the commit body captures what, the diff captures how, but neither captures *what it means*, *where it transfers*, *what emerged*, or *what question it opened*. Third Act runs a ten-question interview at closure. The interview is not a survey — it is autologica applied to the work: the system asks the system to produce its own narration. The output is a single information matrix that can be rendered for four different audiences without re-interviewing. ## When this skill activates **Trigger signals** (any one is sufficient): - Operator explicitly says "closure", "EOD", "finiamo", "chiudiamo", "third act", "terzo atto" - A commit body contains `closes:X`, `ships:X`, or marks a shipped feature/principle (not a small fix) - Cross-node coordination ends (Sinapsi message marks "CHIUSO", "EOD", "DONE" from partner node) - Memory crystal created (a new file in `/memory/feedback_*.md` or skill in seed) - Session ending with significant wor