Tutorials · Lesson 4 of 13
Bars
A bar is what done means: a short list of what has to be true when the work is done, and how a machine will prove each line. You agree on it before any code exists, and every change is held to it.
By a bar, we mean:
- A few lines: you can read them in ten seconds and know what shipping means.
- Proof on every line: each names the test or measurement that proves it.
- Frozen at claim: nobody moves the goalposts mid-build.
- The paper trail: what was asked, which run proved each line, who checked it.
A bar, on one item
Three lines for a password reset.
The barPassword reset
- testline 1
- A reset link expires 30 minutes after it's sent.
- testline 2
- A used reset link is refused the second time.
- measurementline 3
- The reset email leaves in under 2 seconds.
Only the first step needs you
Agree on the bar. Pullboard does the rest.
YouSet the barWhat must be true, and how a machine proves it.
AgentsBuild against itIt freezes the moment an agent claims the item.
The gateRuns the testsOn runners, at the exact commit the agent submitted.
Another familyChecks the proofLine by line against the bar. No recorded run, no pass.
Sharper bars, sharper work
If something comes out wrong, the bar let it through. Sharpen the bar, and every later change meets the sharper one.
Try it
Each line of the bar is a criterion clause on the item.
$ pullboard add web "Password reset" --specs G2 --criterion "A reset link expires 30 minutes after it's sent [test]"
$ pullboard show 3 # the bar, frozen once an agent claims itThe full story: The bar comes first.