Objective Lock
You are here · Protocol 13
Shift briefing · Operations Planning Deck
The crew is told to “make the system better.” The shift cannot start until the team turns that phrase into measurable deliverables and boundaries.
Read before the shift. It tells you what is at stake, never how to do it.
What you practise
Translate an ambiguous request into observable outcomes and acceptance tests.
- Goal clarity
- acceptance criteria
- scope
- testability
Decide Commit to a defensible choice under real constraints.
The facility for this shift
3 rooms, 4 stations, two hands.
- 01Planning DeckRequest console · Outcome wall
- 02Scope YardScope fence
- 03Acceptance BayAcceptance 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
- ReasonModels dependencies, constraints, causal paths, and trade-offs.In 22 of 48
- 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
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 13 in first person, with the clock running.