The System Blueprint
You are here · Protocol 27
Shift briefing · Architecture Atrium
A prototype has duplicate state, unowned responsibilities, and unclear trust boundaries. Rebuild the blueprint before connecting code.
Read before the shift. It tells you what is at stake, never how to do it.
What you practise
Build a component map with data flows, trust boundaries, and explicit responsibilities.
- System architecture
- component boundaries
- data flow
- trust boundaries
Construct Build a working system and prove that it holds.
The facility for this shift
4 rooms, 4 stations, two hands.
- 01Architecture AtriumComponent wall
- 02Flow GalleryData-flow cables
- 03Boundary HallTrust-boundary tape
- 04Ownership OfficeOwnership 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
- 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 27 in first person, with the clock running.