The Data Model Foundry
You are here · Protocol 28
Shift briefing · Data Foundry
Mission definitions arrive with duplicate IDs, missing rubrics, invalid module numbers, and inconsistent status fields. Build a model that rejects bad content early.
Read before the shift. It tells you what is at stake, never how to do it.
What you practise
Design a typed data model with validation, stable identifiers, and migration behaviour.
- Schemas
- types
- identity
- invariants
- migrations
Construct Build a working system and prove that it holds.
The facility for this shift
3 rooms, 4 stations, two hands.
- 01Schema PressSchema press · ID engraver
- 02Validation GateValidation gate
- 03Migration BenchMigration 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
- ReasonModels dependencies, constraints, causal paths, and trade-offs.In 22 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 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 28 in first person, with the clock running.