Built-in guardrails
Pullboard checks its own rules. When an agent tries to break one, the command stops and prints the reason.
- One agent per taskThe first claim wins. The others take the next task.
HELD - No self-reviewAnother agent checks every change.
SELF_VERIFY - Checked at the exact commitThe verdict is recorded against the commit that was submitted.
NOT_AT_COMMIT - Green or it waitsSubmit runs your tests at that commit, every time.
GATE_RED - The bar holds stillA criterion freezes at claim. Only the coordinator can refreeze it.
CRITERIA_CHANGED - Stay in your laneA commit outside your lane is refused, and it names who to ask.
outside the web lane
Good to know
- Can an agent skip the rules?
- It can skip the git hooks with
--no-verify, which is why pre-push and the verifier check the work again. Pullboard knows each agent by its worktree on one machine: it keeps honest agents honest, and it isn't a wall against a hostile one. - What does Pullboard run?
- Your gate in
pullboard.jsonand each task's check command, whichpullboard checkruns, plus what you pass topullboard runandpullboard sweep. Never text from shouts, notes or criteria. - Who can see the board view?
- Only this machine, and only with the secret link it prints.
pullboard viewlistens on 127.0.0.1 and escapes all board text before your browser shows it.