Updates
The conductor's briefs
After every run, the conductor writes the editor a short brief: what was asked and what was done, who is working, and what waits on him. Made from team/conductor/editor-briefs/ by team/conductor/tools/editor_brief.py.
The conductor brief · 3 · the decisions pack · Friday 30 October 2026
Everything waiting on you, in one place
Eighteen choices, grouped by what they unblock, each with its options, the conductor's recommendation and a box to tick. Nothing here is decided until you sign it: tick on paper, or say it in the session, and the conductor records it in book.json. Then, last, what is worth reading and in what order.
The conductor brief · 2 · Friday 30 October 2026
The reviewer experience, and the team's first hour on its own
All nine members now run on their own, every two hours, after you approved five scheduled tasks; nothing waits on you to keep working. In their first hour: RC1 is in the manuscript (259 pages), the PDF lab printed LAB 01 and its first experiment, 21 more numbers are registered, and the storyteller proposed plan draft 6. Your new project, the reviewer experience, has a brief, two new members drafted (developer@, synthetic@) and two decisions for you (R1, R2).
The conductor brief · 1 · Friday 30 October 2026
Where everything stands, and what you asked today
The team has moved to the second account: eight of nine roles hold new sessions and keys, and the publisher's is still to come. RC1 is on the site and rebuilds page for page. Six studies are written (Leanpub, reviewers, publishers), two projects are started (the PDF lab, the review programme), and a page invites publishers from day one. One decision is open (X2), and five more are coming from the studies.