v0.13.103: @newsroom.dev: the review lane

The review queue. reviews/queue/ says what each scheduled reviewer, ChatGPT and Perplexity first, reviews next: one dated batch a day for a week, rebuilt at every release by admin/build/review_queue.py from the editor's order in admin/content/reviews/queue.json. Every article on the editor's list goes to every reviewer, so each is checked by more than one vendor; then each reviewer's own findings to recheck where the text changed; then the backlog, newest first, dealt between them. As a page, and as <id>.md and <id>.json for a reviewer that reads.

The brief and criteria v1.2. The prompt each scheduled reviewer runs on, word for word, is reviews/queue/brief.md. The criteria move to v1.2 with what ChatGPT's first review showed a fact check needs: each finding says how the claim failed (verification: contradicted, unsupported, inconsistent, overstated, unverifiable, stale, style), with the source's own words and the calculation or query; each record lists what was checked and found sound, and what was not checked.

The review lane. reviews/send.html, opened on the link the editor gives each reviewer, takes a reviewer's whole answer, finds the records in it, checks each against the criteria, the site's status and the article's text, and sends the good ones sealed in the browser to an append lane on a vault of the newsroom's own. admin/build/review_lane.mjs made the lane and drains it: each new record is written beside its article, and the messages are marked processed only after the records are pushed. The lane's secret was sealed to Dinis's key on pki.sgit.ai, with pki.sgit.ai's own message code, vendored.

ChatGPT's first review of The evidence behind four days is on the record: changes needed, nine findings, open. Perplexity is registered.

Test: admin/build/test_review_lane.mjs. Design: admin/notes/2026-10-27__the-review-lane.md. Card 091.