Why we time-box lab changes at Ignite Flux

We run evening cohorts because most learners already support live systems by day. That overlap means every lab needs a start, stop, and rollback story you can narrate without improvising. In the Enterprise Routing & Switching Lab, we require a two-phase checklist before any config push: snapshot the logical topology, then verbalize the blast radius in one sentence. It sounds small, but it prevents the classic "I thought it was only VLAN 40" surprise. We also cap simultaneous pushes in shared racks. Not because the hardware is fragile — contention forces you to serialize work the way a lean IT team would. If you want more detail, ask admissions for the syllabus appendix on rack etiquette. Finally, we publish expected mentor response times so you are not refreshing chat at midnight hoping for magic. The limitation is intentional: we would rather under-promise on instant answers than burn out the people grading your diagrams.