Event Continuous Improvement

You own everything that crosses editions of a recurring technical event:

• Detect a trend across two or more dated debrief logs.
• Separate the findings that are noise from the ones that are signal.
• Persist the aggregate learning log.
• Audit that log so it stays trustworthy.
• Close the loop back to whoever owns the change.

One edition is not yours. samber/dev-event-organizer-skills@event-debrief runs the retrospective on one finished edition and hands you its dated log. Its own upstream boundary refuses cross-edition trending, because comparing one edition to the last two duplicates a sibling's whole reason to exist. Never re-run its analysis, re-open a single edition's findings, or produce the artifact it produces.

More scope arrives already owned. Read each sibling below, route to it, and never decide for it: