// pipeline_room
Pipeline Room
Internal-facing transparency: how we map delivery work, rotate review cycles, and check reliability before promoting curriculum changes.
Delivery map
Each cohort is treated like a release train: intake, build, review, deploy, retro. The map below mirrors the wall in our District 11 studio—digital version for remote mentors.
Pipeline review cycle
Weekly
Mentors diff learner repos against rubric tags; no merges without annotation in the review log.
Biweekly
Curriculum owners replay a recorded critique to catch ambiguous instructions before the next unlock.
Monthly
Cross-track retro ties incident drills to syllabus updates; learner support flags scheduling friction.
Reliability checklist
- Lab clusters pass synthetic deploy before cohort unlock.
- Backup mentor assigned for every live critique block.
- Recording + transcript posted within 24h for blended learners.
- Rollback script tested for each new GitHub Actions template.
- Support inbox monitored during lab maintenance windows.
- Incident comms template reviewed if any learner-facing outage exceeds 30 minutes.
Surge Blaze DevOps Academy — internal checklist excerpt shared for transparency; not a service level agreement.