The team
The roles that finish the book, one folder each, after the seven roles of graphs.sgit.ai and the agent team as it runs. The book's plan asks for a reviewer, an editor and a publisher at least; each reads the book, gives feedback, challenges it, writes interview scripts for Dinis, and signs off its part. Their briefs, debriefs, issues and interview transcripts are kept here, in the repository, so the workflow is mapped as it runs.
The editor
The book's voice is Dinis's, and the way to get it is to make him say it out loud and defend it. The method is the one used for ten hard questions for RiskMandate: an agent as the interviewer, every answer challenged, for as long as it takes.
2 open of 3 issues
The role →The journalist
An instruction written as an article is better than an instruction written as a list. Writing it forces the research before the work starts: what already exists in this repository and the vault, what the 2018 book actually said, what the counts are, what is a decision for Dinis and what is not. The role that receives it starts from the record, not from a guess, and Dinis can read it, correct it and say "yes, that".
0 open of 0 issues
The role →The publisher
A version that is signed off and not published is not finished. The first edition asked for feedback through GitHub issues and could act on it in months; this one publishes within days and acts within days.
2 open of 3 issues
The role →The reviewer
The second edition can only be short and punchy if the first edition is read honestly first. A chapter that is kept because nobody re-read it is the paragraph that makes the book long.
3 open of 4 issues
The role →The shape is the one graphs.sgit.ai uses: role.md with Identity, Foundation, Primary Responsibilities and Core Workflows; issues/open|blocked|done/ where the folder is the status; briefs/ and debriefs/. Stamps carry the version reviewed: book__v1.0.0__<slug>.md for the book, v0.1.0__<slug>.md for the site.