The Version and Configuration Vault
You are here · Protocol 45
Shift briefing · Version Vault
A saved player record references an older mission format. A title change should not orphan the save, and a prompt update must be traceable to its evaluation results.
Read before the shift. It tells you what is at stake, never how to do it.
What you practise
Version mission content, schemas, prompts, and model configuration so changes are reproducible and migratable.
- Versioning
- compatibility
- lockfiles
- migrations
- changelogs
Construct Build a working system and prove that it holds.
The facility for this shift
3 rooms, 5 stations, two hands.
- 01Ledger RoomVersion ledger
- 02Migration LabMigration bench · Diff viewer
- 03Release ShelfManifest printer · Rollback shelf
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
- CreationDesigns prompts, workflows, systems, and workable artifacts.In 23 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 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 45 in first person, with the clock running.