Artifact: Learning-Norm Institutionalization — Rotating Tech Talks

A recurring team ritual designed to survive its founding manager leaving -- exercises co-19. Everline and every name here are fictional; every detail is an illustrative, constructed example.

The ritual: a 20-minute rotating tech-talk slot in the team's existing biweekly all-hands, already on the calendar -- no new meeting created.

The mechanism that keeps it running without its original owner: facilitation ownership is tied to the same rotation calendar the postmortem-facilitator duty already uses, not to Priya personally scheduling speakers each time. Whoever is up on the rotation picks their own topic (a recent design decision, a postmortem's root cause, a tool they learned) and the calendar entry itself, not a person, is what triggers the next talk. If Priya left tomorrow, the calendar keeps generating the next slot and the next name on the rotation regardless.