The Integration Circuit
You are here · Protocol 24
Shift briefing · Integration Circuit Bay
A customer record must move between two systems with different field names and error semantics. Wire the bridge without losing meaning or treating failure as success.
Read before the shift. It tells you what is at stake, never how to do it.
What you practise
Connect components with explicit contracts, data mapping, and failure-aware API handling.
- API contracts
- request/response
- schema mapping
- status codes
Construct Build a working system and prove that it holds.
The facility for this shift
3 rooms, 4 stations, two hands.
- 01Request TerminalRequest terminal
- 02Mapping BoardMapping board
- 03Response & Test BayResponse light panel · Test bench
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
- CreationDesigns prompts, workflows, systems, and workable artifacts.In 23 of 48
- ReliabilityTests, reproduces, validates, recovers, and produces consistent outcomes.In 39 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 24 in first person, with the clock running.