The Reliability Reactor
You are here · Protocol 42
Shift briefing · Reliability Reactor
A service becomes intermittently unavailable during a critical mission. The system must degrade safely and recover without duplicate state changes.
Read before the shift. It tells you what is at stake, never how to do it.
What you practise
Design fault tolerance with bounded retries, idempotency, fallback, and safe recovery.
- Reliability
- idempotency
- retry budgets
- circuit breakers
- recovery
Construct Build a working system and prove that it holds.
The facility for this shift
3 rooms, 5 stations, two hands.
- 01Injector BayFailure injector
- 02Control RoomRetry controller · Circuit breaker
- 03Recovery RoomFallback station · Recovery register
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
- JudgmentChooses proportionate actions and knows when to verify, abstain, or escalate.In 27 of 48
- ReliabilityTests, reproduces, validates, recovers, and produces consistent outcomes.In 39 of 48
- ResponsibilityProtects privacy, limits permissions, documents decisions, and blocks unsafe releases.In 23 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 42 in first person, with the clock running.