The Debugging Floor
You are here · Protocol 38
Shift briefing · Debugging Floor
A mission result changes after refresh. The visible symptom could originate in state restoration, assessment order, or duplicate event handling.
Read before the shift. It tells you what is at stake, never how to do it.
What you practise
Diagnose an issue from a reproducible trace, isolate the cause, fix it, and prevent regression.
- Reproduction
- hypothesis
- logs
- root cause
- regression test
Break and repair Reproduce a failure, find its cause, repair it for good.
The facility for this shift
3 rooms, 5 stations, two hands.
- 01Reproduction BayReproduction station
- 02Trace RoomTrace wall · Hypothesis board
- 03Patch & Regression RoomPatch bench · Regression gate
Compromised Signal · sealed
Something in this shift will change, and the briefing will not tell you what. You find it from the evidence, or your after-action review shows you where it was.
How the shift is assessed
3 criteria · 0 to 6
Scored from what you did: the evidence you checked, the stations you operated, the artifacts you produced and the gates you passed. The criteria are revealed in your after-action review, not before.
Capabilities evidenced
- PerceptionNotices relevant signals, discrepancies, provenance, and system state.In 13 of 48
- ReasonModels dependencies, constraints, causal paths, and trade-offs.In 22 of 48
- ReliabilityTests, reproduces, validates, recovers, and produces consistent outcomes.In 39 of 48
Chamber III · Action Chamber
Build only what you can stand behind, and stop a release that is not safe.
Construct, integrate, evaluate, debug, secure, deploy, observe and responsibly operate AI-enabled systems.
Play Protocol 38 in first person, with the clock running.