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 register
| Review | Reviewer | Received | Reviewed at | Items | State |
|---|---|---|---|---|---|
| r001 · First reading of the book | Dinis Cruz | 22 August 2026 | v0.3.7 | 9 | commented |
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; 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.