The mechanisms
Pullboard holds each rule with a mechanism: git hooks, frozen criteria, pinned commits and a second agent’s verdict. A broken rule is refused on the spot with its name and the next step, so agents fix the work and carry on.
Agentic Item Lifecycle (AILC)
A state machine, drawn from the code itself: each state an item can be in, every move between them, who may make it, and the refusal each wrong move raises at once.
Agentic Development Lifecycle (ADLC)
You included: you approve the spec, agents claim, build and submit in their lanes, and a second agent verifies before anything merges.
Four checkpoints
Each one refuses on the spot, with its rule’s name.
- At claimFrozen at claimNobody can soften the bar mid-build.
- At commitLanes and hooksAgents commit only inside their lane.
- At submitThe gate and the pinGreen tests to submit, then pinned in git.
- At verifyPeer verifiedThe builder never judges its own work.
Also enforced
Smaller rules, held the same way.
- LeasesA claim lasts two hours by default. A stalled one lapses, and the item frees itself.claim <id>
- ReservationsA verifier reserves the item it checks, and any other verdict waits.next --verify
- New work onlyA rejected commit can’t come back. The rework is committed first.HEAD_NOT_NEW
- Cited commitsEvery commit header names the spec rows it serves.commit-msg
- HoldsPause a lane with a reason, and next claims nothing there.hold <lane>
- DecisionsA question stays open until it’s answered. Only your calls reach you.--decision
Commands
Each one, with its flags and its refusals, in the docs.
npm i -g pullboard
pullboard help