Prompt Iteration Lab
You are here · Protocol 17
Shift briefing · Prompt Test Lab
A prompt was changed five times and nobody knows which edit helped. Rebuild a controlled test setup and improve the output with evidence.
Read before the shift. It tells you what is at stake, never how to do it.
What you practise
Improve an AI-assisted workflow by running controlled iterations and comparing evidence.
- Experiment design
- baselines
- variables
- version comparison
Experiment Change one thing, run it again, compare on evidence.
The facility for this shift
3 rooms, 4 stations, two hands.
- 01Run LabRun rack · Version cards
- 02Evaluation RoomEvaluation gauge
- 03Release RoomRelease locker
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 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 17 in first person, with the clock running.