The Automation Loop
You are here · Protocol 25
Shift briefing · Automation Control Room
A scheduled automation issues duplicate refunds when a retry occurs. Rebuild it so repeated delivery cannot repeat a harmful side effect.
Read before the shift. It tells you what is at stake, never how to do it.
What you practise
Design an automation with safe triggers, idempotency, approval gates, and rollback.
- Trigger/action
- idempotency
- approval
- rollback
- repeat safety
Construct Build a working system and prove that it holds.
The facility for this shift
3 rooms, 4 stations, two hands.
- 01Automation FloorTrigger console · Action station
- 02Approval GateApproval gate
- 03Rollback PanelRollback panel
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
- 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 II · The Operator
You set the direction. Tools do the work, and you test what they return.
Turn goals into workflows, allocate work, test outputs, retrieve sources, automate safely and make decisions under pressure.
Play Protocol 25 in first person, with the clock running.