Human approval
Put a person on a station and the work waits there. Approve it and it moves on; reject it and it goes back with your reasons. The gate is enforced by the system — no prompt can talk its way past it.
- Part
- F-18
- Status
- Live
- In one line
- Quality control: a gate where a person has to say yes
Some steps should not be automatic: a production deployment, a customer-facing publication, anything touching hardware. In CodeBook that is not a special mode, it is a station with a human worker on it.
A station can also require approval before its agent acts, which is the lighter version of the same idea: the run is prepared and held until somebody says go.
Related parts
F-04
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.
F-02
Workers on stations
Every column in a workflow can have one worker behind it — an agent you hired, a person, or an agent that waits for a person’s approval. The column stops being a place cards wait and becomes a station where something happens to them.
F-17
Notifications
A station can email somebody when work arrives — the reviewer who needs to look, the person whose answer the agent is waiting on.
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