How cohorts unfold

Before: ad-hoc tutorials. After: a documented loop your team can repeat without the same hero engineer online every night—still human, still imperfect, but legible.

1. Intake note — you describe constraints: vendors, compliance, on-call load.
2. Baseline artifact — short repo or diagram so mentors calibrate feedback.
3. Rhythm — weekly merges or async checkpoints, never both undefined.
4. Game days — injected failures in sandboxes before patterns touch prod narratives.
5. Archive — capstone pack you can drop into internal wiki without scrubbing names.