Harbor migration arc
A platform engineer used the AWS Intensive Lab scenario bank to rehearse failover language their panel actually used—no numeric outcome claims, just calmer explanations under time.
This page collects the three things learners ask for first: when cohorts land, what labs actually feel like, and how peers describe the arc—not income promises, not stock-style dashboards.
Labs open with a one-page brief: actors, constraints, and what “done” means. You sketch in the shared whiteboard tool, upload a static export, and receive line comments—not numeric scoreboards. We rotate reviewers so you hear more than one voice on the same drawing.
Diagram
Abstract flow: brief → diagram → critique → revision (illustrative).
A platform engineer used the AWS Intensive Lab scenario bank to rehearse failover language their panel actually used—no numeric outcome claims, just calmer explanations under time.
Evening Azure sprint graduates asked for slower async captions; we shipped caption pacing notes in the next catalog revision.
A logistics IT team reused the ADR template from the enterprise cohort internally—operational reuse, not a headline metric.