The State Machine Chamber
You are here · Protocol 32
Shift briefing · State Control Chamber
A mission can be started twice, completed while locked, or scored after cancellation. Build a state machine that prevents impossible transitions.
Read before the shift. It tells you what is at stake, never how to do it.
What you practise
Model system behaviour as explicit states and permitted transitions.
- Finite-state machines
- guards
- transitions
- terminal states
- invariants
Construct Build a working system and prove that it holds.
The facility for this shift
3 rooms, 4 stations, two hands.
- 01State GraphState tiles · Transition rails
- 02Guard StationGuard station
- 03Replay ConsoleReplay console
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
- ReasonModels dependencies, constraints, causal paths, and trade-offs.In 22 of 48
- CreationDesigns prompts, workflows, systems, and workable artifacts.In 23 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 32 in first person, with the clock running.