Verdicts and thresholds
Every finding leaves the hearing with a vote between 0 and 3. What happens next is entirely determined by two numbers you control.
The vote
| Vote | Default outcome | Meaning |
|---|---|---|
| 3 / 3 | Posted, blocks the merge | No juror could refute it given the surrounding code. |
| 2 / 3 | Posted as a warning | A majority held; one juror had a specific objection worth reading with @dicast why. |
| 1 / 3 | Struck | One juror defended it. Usually a real pattern applied to the wrong place. |
| 0 / 3 | Struck | Refuted outright — commonly a condition already guarded elsewhere. |
Choosing a threshold
| threshold | Effect | Suits |
|---|---|---|
| 1 | Posts anything one juror will defend | Security-sensitive paths where a miss costs more than a false alarm. |
| 2 | Majority. The default. | Almost everything. |
| 3 | Unanimity. Very quiet. | Repositories where the team has already stopped reading review bots. |
Threshold 3 is worth considering as a starting point if your team has been burned by a noisy reviewer. Trust is easier to build upward than to recover.
Two-juror panels
If a vendor is unavailable, panels seat with two jurors rather than failing the review. The threshold is not lowered — a threshold of 2 becomes unanimity for the duration, so you see fewer comments rather than less-scrutinised ones. Affected reviews are marked in the struck record and can be re-heard with @dicast recheck at no cost. Incidents of this kind are published on the status page.
The gate is separate
block_at is independent of threshold. A common arrangement posts on a majority but blocks only on unanimity, which is the default. See the merge gate.