graphs.sgit.ai → Reviews

The reviews

The book is reviewed the way code is reviewed, minus the server: feedback arrives in whatever form the reviewer has (a voice memo, numbered screenshots with comments, a document), is normalised into a review with numbered items, and the agent's first response is comments and proposals, never edits. The conversation agrees or declines items; each agreed item lands in a release; and the version diff view shows the exact delta each review produced. The whole exchange is kept as JSON, one file per review: a pull request with no server, linked to the version it reviewed so that later drift is detectable.

The states. A review is received, then commented (the agent has responded to every item, changing nothing), then in discussion, and closes when every item is applied or declined. Items carry the same states individually, so a review can be half-landed and honest about it. The decisions. Since r003, every review also carries a decisions register, rendered at the top of its page: the calls the conversation is waiting on, each linked to its item, with its options while open and its answer once made. The Decisions column below counts what is open.

The register

Review	Reviewer	Received	Reviewed at	Items	Decisions	State
r004 · The altitude ladder: one book at five altitudes	Dinis Cruz	22 August 2026	v0.3.14	12	5 open	commented
r003 · Decouple the book, evidence first, reviews as graphs	Dinis Cruz	22 August 2026	v0.3.12	6	2 open	commented
r002 · A book for humans and agents	Dinis Cruz	22 August 2026	v0.3.8	9	2 open	in discussion
r001 · First reading of the book	Dinis Cruz	22 August 2026	v0.3.7	9	1 open	in discussion

Anyone can review the book: the easiest routes are the comms board or an issue on the repository, in any form. Screenshots with comments are welcome; so are voice memos. The workflow does the normalising.

For an agent

Each review lives at /reviews/rNNN.json with its rendered projection at /reviews/rNNN.html. Items carry states (noted, proposed, in discussion, agreed, applied, declined) and, once applied, reference the release that landed them; since r003 the JSON also carries a top-level decisions array (each decision names its item, question, options and state, then its answer once made), so read the decision states before summarising what a review is waiting on. The delta of any release pair is machine-readable under /book/changes/data/. Verbatim source memos are preserved in /briefs/. When summarising a review, carry the item states: a review is not a to-do list, it is a negotiation with a record.