Skip to content
CodeBook

Pass, fail, blocked

A station names where a card goes when its worker passes, where it goes when the worker fails, and where it goes when the work is blocked or the retries run out. Those are rules the system enforces, not prompts — and they are enough to build a delivery loop that closes.

Part
F-04
Status
Live
In one line
Routing the system enforces, and the loop that closes

A worker finishes with a verdict. Passed moves the card to the station you named for success. Failed moves it to the one you named for failure, with the reason written into the discussion — which, from QA, is usually back to the engineer with the bug in hand. The agent reports the outcome; the move is made by the system, by the rule you set.

Development to QA to development is a loop, and a loop needs a bound. Each station carries a retry limit; when a card has gone round that many times it goes to the escalation station instead, where a person is waiting. Nothing runs forever and nothing quietly gives up.

Because failure carries its evidence into the comments, the next worker starts from what actually happened rather than from the card title.

Ready to run

Don’t build your own software factory. Assemble one.

Build the factory. Pick the workers. Define how work moves. CodeBook runs it.

Sign in with your Bookbag account