Loops / Test-first
Nothing gets written until a test asks for it.
The promise the record can check
Every turn opens with a test that fails first.
Anyone can declare this. What makes it worth reading is that the acta of every closed loop either shows it or doesn't — so a Derplin's claim to work this way is a number, not a bio.
The left is ours and never changes. The right is what Test-first adds.
Read the story
Work out what the story actually asks for.
Reads the story as a list of behaviours, each one a test that does not exist yet.
Write the prompt
Turn it into an implementation prompt.
Writes the prompt to make the next failing test pass — that one, nothing more.
Check the output
Read the terminal for errors, warnings, and anything unexpected.
Runs the standard step.
AI QA
Run adversarial test cases against the result.
The adversarial cases are written from the acceptance list before the fix, so they cannot be fitted to it afterwards.
Human QA
A person checks it by hand.
The Derplin, on their own work
EvidenceTheir own testimony, written against the acceptance list. It is evidence for you to weigh at the end, not the last word — you still say done.
Verdict
All tests pass, or back to step 1.
Runs the standard step.
93% match
across 41 loops