Interactive Labs
Change one assumption, predict the consequence, then inspect the model boundary. These are small, transparent experiments—not hidden scores, equipment selectors or engineering deliverables.
A transparent experiment deck
Each lab starts with a prediction, exposes a small set of inputs and keeps its result type visible. Calculated outputs follow documented arithmetic from the values on the page. Illustrative outputs explain direction, path or dependency inside a deliberately simplified teaching model. Neither label means measured site performance.
Open the model card inside a lab before interpreting its result. It states the modeled boundary, assumptions, exclusions, source trail and version. The catalog does not rank technologies, generate a hidden green score, certify topology or replace site engineering.
How to use a lab
- Predict which output should change before touching a control.
- Manipulate one visible assumption and inspect the result on the same boundary.
- Stress the model with density, loss or failure until a documented constraint binds.
- Debrief what changed, what remained outside the boundary and which real evidence would be required before acting.
PUE Boundary
Build an annualized facility-energy stack and see exactly which supporting loads move the estimated PUE.
Prediction cue: Before moving a control, predict whether the ratio and total facility energy will move together—or in different directions.
Power Path
Choose a topology, remove components and watch which complete paths still reach a dual-corded rack.
Prediction cue: Name the component whose loss will remove both labelled feeds before you open anything.
Thermal Evolution
Evolve one conceptual rack row and make bypass, recirculation, density and a failed cooling unit visible.
Prediction cue: Choose the change you expect to reduce mixing most, then test it before increasing cooling capacity.
Cooling Heat Path
Follow the heat rather than assuming rear-door, direct-to-chip or immersion defines the whole plant boundary.
Prediction cue: Estimate how much room-air heat remains after changing liquid capture, before reading the calculated split.
Availability Budget
See how a small percentage difference becomes a sharply smaller annual unavailability allowance.
Prediction cue: Predict the order-of-magnitude change in downtime when another nine is added to the target.
Rack Density
Change load and rack count, then challenge the average with the constraints it leaves out.
Prediction cue: Predict whether adding empty racks changes actual equipment heat or only the displayed average.
Alarm Triage
Inspect three authored alarm examples and decide whether each one supports a real operator action.
Prediction cue: Choose which alarm lacks enough context to support action before opening its triage result.
Packet Path
Trace endpoint access, representative fabric lanes and one shared meet-me-room boundary without pretending to size a real network.
Prediction cue: Predict whether the selected failure removes local workload connectivity, external reach, or both.
Fire Layer Sequence
Inspect the dependency order of generic protection layers before entering the deeper Design Pro cause-and-effect capstone.
Prediction cue: Before stepping forward, name what must happen between early detection and a physical suppression action.
From isolated mechanism to system design
The full Academy lessons explain the language and mechanism around each experiment. Playbook cards compare solution families and expose their source and review state. Design Pro capstones combine several systems into editable scenarios with local snapshots and separate consequence registers. No layer silently mutates a live game save.