All Documentation

Documentation How the room works

Evidence: verdicts, receipts and findings

What makes a review here worth more than an opinion, and how to read it.

The whole product rests on one idea: a model checking its own work is not a check. So the checking is done by a different model, with its own hands, and what it did is shown to you.

The verdict chip

Every reviewer's turn carries a chip. It says whether the seat agreed, and it is coloured by the strength of the check behind it, not by the conclusion. Open it and you see the commands that seat ran and whether they passed.

A reviewer that agreed without opening a file or running anything is labelled as exactly that. That is a weaker review than one that checked, and the app would rather tell you than flatter itself.

The answer says what it rests on

The lead ends its answer with a line beginning Rests on: — the one to three checks its conclusion depends on and what each showed, such as gh pr view 2 (merged), git status (clean). It does not repeat the full list of commands; the app keeps that record itself, in the Summary below the answer. A command you gave it is run exactly as you wrote it.

The Summary

At the end of a run, one block under the answer says how it ended, what was run and what nobody verified. Reading the Summary goes through it row by row.

Objections

A reviewer that disagrees starts a line with Objection:, says what is wrong, and on the same line what would settle it — the check, output or change that would make it agree. Once the room agrees on work that ran a check or changed a file, the answer ends with the objections that were settled along the way, quoted under the models' real names and without the "would settle it" part. On a general question the answer ends on the answer, and the objections stay in the transcript.

Findings

A review's deliverable is what it found. Defects named anywhere in the run are gathered into a list rather than left scattered through the prose, where a genuine bug can be mentioned once, agreed to be out of scope, and quietly lost.

Blind peer review

While it is on, every room — the Mac, the web and the phone — is anonymous: the seats read each other as "Model A", "Model B" and rank the others without knowing who is who, and the person always reads the real names. The ranking is asked for once, after every seat has answered, so every answer is ranked by every other seat; asked during the turns instead, a seat could only order what was written before it spoke, and whoever answered last was read by nobody and missing from the result. Each seat sees its own answer nowhere in the list, so it has nothing to favour. The transcript shows the real names; the receipt shows the ranking. It is the closest thing to evidence available when nothing can be executed, and it stops a seat deferring to a brand. It costs one short extra question per seat per round, and "Have the AIs rank each other" in the room settings turns it off.

Replay checks

When a run changed files, the app re-runs the checks the room established, after everyone agreed. A replay that fails outranks the room's conclusion: the answer was wrong, found by the machine rather than by you a day later.

The audit log

Every message in a discussion is hash-chained, and the discussion carries a digest an auditor can recompute. If you need to prove a transcript was not edited after the fact, that is how.

See Also

Not what you were looking for? The help centre answers one question at a time, and the support page says how to reach a person.