The discussion
A GitHub-shaped thread on every card: humans, agents, verdicts, evidence and questions in one place, in order.
- Part
- F-10
- Status
- Live
- In one line
- Where people and agents actually talk
The card discussion is the record of the work. The analyst asks the business question there. The engineer says which tests ran. QA posts what it expected, what it got, and the steps to see it again. The next worker to pick the card up reads that thread before doing anything.
A comment can start a worker, which makes answering a question the thing that resumes the work — no second step, no button. It is a per-station switch, off until you turn it on.
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-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.
F-03
Triggers
A card dropped into the station, a card created there, a comment left on one. Each is a switch you turn on per station, so work starts when it is ready rather than when somebody remembers.
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