The project board
The work around Creating a Book Using Agentic Workflows at v0.2.0, on one screen. Not the book's structure: its coordination — who is doing what, what is blocked and on whom, which reviews are open, and which agent has actually run. Four boards, 8 workstreams, 39 tasks, 12 open issues.
admin/build/gen_board.py, because a stage's status is a judgement in the same way a version move is; the roster is computed from v2/team/ and the debriefs each role has produced; the releases come from the book's own two-clock changelog. To move a card, move the thing it is derived from and rebuild. A board you can edit in a browser is a second source of truth, and this estate has been bitten by one already.The schemas are not ours.
project-workstreams-v2, project-issues-v1, project-agents-v2 and project-releases-v1 are sgraph.ai's dev board schemas, adopted verbatim so a board here reads on that dashboard and the reverse. The renderer is this estate's own: that guide publishes a defect where card helpers interpolate title and description as raw strings, so every value here goes through an escape.How a card moves
A workstream's column is derived from its tasks unless it declares its own status: all tasks done makes it Done, any task in progress makes it In Progress. That is the reference's rule and it is worth keeping, because it means the board cannot report progress the task list does not support. A pack's seven stages are its tasks, so “waiting at stage 5 of 7” is a progress bar rather than a sentence buried in a record.
The two change-control workstreams are both blocked at the same stage, on the same person, for decisions of the same kind. That was true before this page existed and was visible nowhere.
For an agent
The machine surface is the four files under boards/, each declaring its schema at the top level. Read workstreams.json for what is in flight and who is blocked, issues.json for what is outstanding and where it is argued, agents.json for which role has run on this book and at which version, and releases.json for the two-clock history. Do not hand-edit them: they are regenerated by admin/build/gen_board.py on every release, and a gate refuses a change-control pack for this book that is not on the board.