Verdicts

This section is not part of the specification. A verdict is the record of the evidence one decision gate closed on: the commit and the run it was read at, the tests that carry each of the gate’s clauses, the rulings that interpreted the gate, what the evidence does not show, and whether an outsider can reproduce it today. It adds no requirement. The gate’s text, on the page that states the gate, is what a verdict answers to.

What a verdict states

Section	Meaning
The gate	The gate’s text, quoted from the page that states it
Where the evidence was read	The commit, the CI run and the step the evidence comes from, or for an editorial gate the commit the text was read at
The clauses, and the tests that carry each	Every clause of the gate, paired with the tests that exercise it and a negative control that keeps the clause from passing vacuously. An editorial gate pairs each clause with the passage that satisfies it instead
The rulings that interpreted the gate	Where the gate’s text needed reading, how it was read, and why
What the evidence does not show	The claims the closure deliberately does not make
Reproducibility	Whether an outsider can re-run the evidence today, and if not, what is owed

A verdict exists only for a closed gate, and a closed gate exists only with its verdict. The site build enforces both directions: a gate table that marks a gate closed without a verdict page fails, and so does a verdict page on a gate no table marks closed. Every entry below therefore reads closed; a gate that reopens loses its verdict page in the same change.

Entries

Gate	Stated in	Outcome	Verdict
GI1 interoperability	SOVM-IROH §10	closed	GI1 — interoperability
GI2 object identity	SOVM-IROH §10	closed	GI2 — object identity
GI3 revocation	SOVM-IROH §10	closed	GI3 — revocation
GB1 alignment and range access	Blob extension §28	closed	GB1 — alignment and range access
GR1 normative adoption	SOVM-SYNC-RT §6	closed	GR1 — normative adoption

GI1 to GI3 are gates of the iroh transport binding, closed on evidence read from nodes running as separate processes on one host. GB1 is a gate of the blob extension, closed on a prototype run against the reference transfer layer. None of those four can be re-run by an outsider yet: the code the tests exercise is not released, so each of those pages is a record an outsider can read and not yet one they can check.

GR1 is different. It is a gate of the realtime conformance module, and it is editorial rather than empirical: it closed on SSP/1 text, not on a test run. Anyone can check its verdict today by reading the passages it cites.

Closing a binding, extension or module gate does not promote that document out of Draft, and closes none of the gates on the status page.