graphs.sgit.ai → the second edition → the team
The team
Seven roles, one folder each, defined in brief 40. Every role carries its own role.md, its actions, and its briefs and debriefs — the work environment an agent is spun up into.
Why this exists, and it is not throughput. It is judgement. The founder’s reason, in the memo: “it was very powerful when you have agents advocating for certain things, who have specific centres of gravity.” One generalist asked a hard question gives one answer shaped by whatever it read last. Seven roles with declared centres of gravity disagree in useful ways, and a decision made against disagreement is worth more than one made against silence. Isolation is the second reason and it is practical: a role spun up on its own carries only its own context.
| Role | Centre of gravity | What it is for |
|---|---|---|
| Role: Librarian | Nothing is lost, and everything is findable | Keeps the registers agreeing with each other: the briefs, the methods, the lexicon, the dev packs, the decisions and their amendments, and the names of things. actions: index a new artefact |
| Role: Researcher | No claim without an anchor | Answers questions from the closed local corpus and refuses to answer from anywhere else. Owns the anchors, and the honesty of a section that yields nothing. actions: answer a question from the corpus · map a book |
| Role: Writer | A reader who stops early still gets a whole book | Owns the chapter markdown, and nothing else. Computes or quotes every number that enters the prose. actions: revise a chapter |
| Role: Editor | The book's voice, and what it refuses to claim | Reads as a reader rather than an author. Owns structure, voice, and the refusals that travel with every idea this estate publishes. actions: scope a structural change to a book |
| Role: Developer | The scaffolding is more important than the code | A developer for THIS stack: no bundler, 24 Python generators, a projection chain, and a frozen first edition that fails the build if a byte moves. actions: build a tool |
| Role: QA | A gate anyone can silence is not a gate | Owns the suites and the release gate, and the standard of evidence for a claim that something works. Carries the estate's known hole: prose has no freshness gate. actions: turn an invariant into a gate |
| Role: Publisher | A version is a promise to a reader | Owns two clocks and the rule that keeps them apart: the site's version moves every push, a book's version moves only when its content does. actions: release a new version of a book |
Every role here is customised to this estate. Brief 40 is explicit: “It’s not just a writer. It’s a writer for this type of book… It’s not just a developer — it’s a developer focusing on the JavaScript stack that we have, the CI pipeline that we have.” A role definition that would read the same in any repository has failed this brief.
The team arrived late, and the books must say so. From the same memo: “It’s important to say that they don’t start here. In fact, look at the situation. I’m only introducing these now, not in the beginning.” One person and one agent wrote three books before this folder existed. The team is what the work grew into, not what it started as, and any chapter presenting it as a starting condition is wrong.
The shape of a role folder
v2/team/<role>/
role.md Identity, Foundation, Primary Responsibilities, Core Workflows
actions/ one file per thing the role can be asked to do, each naming
its inputs, its output and its done test
briefs/ what the role was asked — vX.Y.Z__<slug>.md
debriefs/ what it did and what it learnt — vX.Y.Z__<slug>.mdbriefs/ and debriefs/ start empty. They are the work environment, and they fill as a role is used; an empty debriefs/ is an honest statement that the role has not run yet. Outputs are stamped with the site version at the time of writing, so a debrief can be placed against the release history without opening it.
The definition itself carries four sections, and the first two are where the work is. Identity gives the role’s core mission, its central claim (the thing it can be held to) and its not responsible for (the boundary that stops it drifting into another role’s territory). Foundation gives the principles it works under, each with the reason it exists here — most were learnt by getting something wrong. Then the responsibilities, naming real paths, and the workflows as numbered steps.
Where this shape came from. The founder pointed at an existing team: “we already have good definitions and good examples from other projects, especially the Send project.” That is the-cyber-boardroom/SGraph-AI__App__Send, whose team folder carries seventeen roles under the same discipline. Inherited, because it is proven: the identity table with its central claim and its boundary, the principles table, the numbered workflows, and version-stamped outputs. Not inherited, because this is a different job: its seventeen roles (AppSec, DevOps, GRC, a DPO — which a three-book publishing estate does not need), its issues filesystem, and its Wardley tier folders that split roles by evolution stage. Brief 40 names two audiences in those terms but does not ask for the roles to be split that way. Kept from brief 40 over Send’s convention: the file is
role.md, lowercase, because the memo says so directly.📄 The rest of this page is rendered from the raw markdown, which is the source of truth.