The advisors and their sessions
Two panels govern this project, and their jurisdictions do not touch. The literary masters judge reading — which dimension deserves attention. The nine advisors judge building — whether the artifact works, whether the link resolves, whether a first reader can use it. The chair proposes; the author ratifies.
They are never merged. Corrected 28 July 2026. They have now sat
together twice — on 27 July and again on 28 July — and the joint sessions found things neither
body had found alone. The standing rule when they meet is attack across the aisle: every
opening must name and break a member of the other body, and a colleague does not count.
The jurisdictions still do not touch, which is why the format works; what was wrong was the word
never.
- The nine advisors — the build panel: two technologists, three literary advisors, two historians, two chair's picks. Its routing table and type discipline are there too.
- The masters session — the adversarial session on which dimension to build next. It produced ten of them, and the finding that reorganised them all.
- Panel session 01 — do we go to Code now? Unanimously yes, with four binding vetoes. One of those the author later overruled, and the record of that stands in the log.
- Panel session 02 — the design of the site. Three rounds, seven advisors, four directions on the ballot, two killed by argued veto. The outcome is applied in the design record.
- Joint session 09 — the two bodies together, on what this project has built read through the book, through Homer, and through the newest Odyssey. Seventeen agents — thirteen openings, three cross-examinations, and an adversarial verifier printed unedited at the end, including where it is wrong about this project. It found a passage the project had been arguing from and never showing.
The other session records — 03 through 08 — are working documents and stay in the repository rather than on this site. The line is not seniority: this one was written to be read by somebody who was not in the room, and those were written to settle a build. Where a working session produced a ruling that binds, the ruling is on the surface it binds, and the reasoning is in the log.