# The review desk: critics who read the pages and brief the writers > The review desk: critics who read the pages and brief the writers: one of the editor's briefs of 2026-11-04__in-session, published in full as given. *Source: · site v0.1.713 · generated from the same content as the page, so the two cannot drift.* --- The editor, Dinis Cruz, in the conductor's session (conductor@book.the-ultimate-insider), about 04:44 UTC on 4 November 2026, after the 04:02 wake closed. Kept as given. Never edited; where it turns out to be wrong, the finding goes in `BRIEF-CORRECTIONS.md`. > Cool. So I think now is, can you create also a series, maybe two or four, of reviewer, like review or reviewer agents that is going to review all these pages from the website and compare them with our guidance, and then basically brief the next round of writer changes, right? So the idea is that, you know, you have this independent view that reads the text or reads the new text, and then converts that into, like we'd be doing here, into the specific area, and then map it out. And to do this, one of the things you're going to need is, I think, a principles or review document that contains all the principles or the core ideas that we have, including examples of writing. It's kind of like the version of those documents, right? And then that can be shared with everybody so that they can see it. And also, I think this review team should have access to all those files that I uploaded, the files created by the other team, so that it kind of knows what we're going for. And then it should implement it and have a little logo of it. That would be quite cool. So we can just make it as professional as we can. And in terms of the workflow, now, like I said, now you can have this workflow where every hour we basically do a pass of the text is read, or the content is read, the reviews are made, and then reviews are read, and then reviews are executed, and then you rinse and repeat until you reach a nice state of balance, right? Again, with common sense. What you want to do, you also want to start to sign off specific chapters and specific sessions, and then focus on that. Sections, not sessions. ## How the conductor reads it (not his words) - **Decision RV1**: a review desk of independent critics. Each reads its part of the book as the site shows it, compares it with the team's guidance, and briefs its writer's next round, mapped to the place in the text. He said "two or four": the conductor's reading is four, one per writer's part (WR2), named critic1 to critic4 so they are not confused with the read-only review steps of every wake (`.claude/agents/reviewer.md`). - **The principles document** he asked for: `team/conductor/guides/the-principles.md`, on the site as `principles.html`, every principle and core idea with examples of writing, shared with everybody. It builds on the checklist in `team/conductor/guides/2026-11-04__the-editors-guidance-for-the-full-book.md`. - **"the files created by the other team"**: the newsroom journalist's files in `team/conductor/from-newsroom/`, which every critic reads. The conductor's reading: "the other team" is the newsroom, not the blind (Cold-Read) team; nothing from here goes to the blind repository. - **The logo**: the review desk's mark, `src/static/assets/review-desk-logo.svg`, an original drawing. - **The loop**: every hour each critic reads the newest text and leaves a note; its writer reads the note at its next wake and applies it; repeat until a pass finds nothing material, with common sense. The conductor's reading of the minutes: each critic wakes about midway after its writer (critic1 :00, critic2 :20, critic3 :37, critic4 :07 London), so it reads the writer's fresh push and its note is ready for the writer's next wake. - **Signing off sections** ("Sections, not sessions"): put to him as **SO1, open**. The conductor's reading: a critic proposes a section for sign-off when two passes running find nothing material; the editor signs it; the writers then focus on what is not yet signed. Until he signs SO1, sections are only proposed, and nothing is frozen. - The conductor starts the four sessions at his word ("can you create ... and then it should implement it"), as for WR2; each member's own session creates its own hourly task. --- *[Site index for agents](../llms.txt) · [HTML version](https://the-ultimate-insider.book.sgit.ai/brief/23-the-review-desk.html)*