The team · proposal
The roles
The roles proposed in the conductor's brief, on the talk team's machinery as it stands: a written mandate per member (ROLE.md, policy.json), the five-step wake, hourly slots, requests as files, session keys, holds, and a release on every merge. The conductor is staffed; the first batch (librarian, historian, security, researcher, storyteller, publisher) is proposed with its prompts in team/conductor/ONBOARDING.md; the rest follow when the plan is signed.
| Role | Owns | First task | Status |
|---|---|---|---|
| conductor | the schedule, routing, pace, the editor's decisions page, the two-repository valve | stand up both repositories; fix the chapter plan with the editor by Friday night | staffed: conductor@book.the-ultimate-insider, at the editor's word, 30 October |
| librarian | the inventory of the source: every file, wake, debrief, decision, memo and chat, indexed | the index, before any chapter is written; the source map is the seed | first batch: proposed, prompt ready (team/conductor/ONBOARDING.md) |
| historian | the timeline: the day minute by minute, from the git log and the wake records | the timeline of 29 October, with the ten or so turning points marked | first batch: proposed, prompt ready (team/conductor/ONBOARDING.md) |
| technologist | how the setup works: tools, schedules, keys, vaults, builds, the player | the architecture of the team, as diagrams and prose, enough to rebuild it | second batch: when the plan is signed |
| security (GRC) | the controls: policies, holds, keys, reviews, what each one stopped, what it missed | the control register: every control in the record, with evidence of it firing | first batch: proposed, prompt ready (team/conductor/ONBOARDING.md) |
| storyteller | the arc: chapter plan, voice, the two threads braided | the chapter plan, from the librarian's index and the historian's timeline | first batch: proposed, prompt ready (team/conductor/ONBOARDING.md) |
| writer | the chapters themselves (the talk's deck member's successor) | chapter 1 as soon as the plan is signed | second batch: when the plan is signed |
| researcher | the claims register: every number in the book traced to the record or a source | the numbers in the brief, checked; then the talk's claims | first batch: proposed, prompt ready (team/conductor/ONBOARDING.md) |
| designer / illustrator | covers, the book's infographics, the talk's visuals re-drawn for print | the cover in three proposals; the list of talk visuals that survive on paper | second batch: when the plan is signed |
| publisher | Leanpub and KDP listings, PDF and EPUB from one source, the paperback proof | the Leanpub book created and the build producing a PDF on day one | first batch: proposed, prompt ready (team/conductor/ONBOARDING.md) |
| readers (synthetic) | the market research: who buys this, what they call the problem, where they put it down | five to eight readers from real buyer types read the brief and the chapter plan | second batch: when the plan is signed |
The editor
Dinis Cruz is the editor: he decides, signs decisions, reads on paper, and is interviewed. Nobody else speaks for him.
The blind repository
A second repository whose agents arrive knowing nothing but the talk's repository at commit 298be4e (site v0.2.0) and write what they find. The one-way valve: the book repository reads the blind one; nothing flows the other way, or the blind repository stops being blind. No brief, chapter, decision or chat from here is ever copied into it.
Who is staffed, with keys and wakes: the team. Source: the conductor's brief, the team, and the lessons to carry.