The record

Corrections

Everything NOMOS answers is kept permanently — sealed transcripts, a hash-chained public log, versioned listings. Permanence cuts both ways: a wrong answer is preserved too, and it is ours. This page is where that cuts us. Every correction to a trust surface is recorded here, with what was wrong, how it was found, and what changed — because an institution that corrects itself on the record is more credible than one that claims it was never wrong.

Corrections to date

None recorded yet. That sentence is doing less work than it appears to: the platform is young and the traffic is early. The honest claim is not "we have made no mistakes" but "when we do, this is where you will read it, dated, in full." Found one we haven't? Tell us — confirmed findings are credited by name.

The machinery that finds them

Corrections here are not promises of diligence — they are outputs of machinery that runs whether or not anyone is watching:

Verdict replay. Before any new version of a listed law goes in force, every recorded decision is re-evaluated under both versions; a verdict that changes must be individually checked and signed for. A verdict the current engine would no longer give is flagged, never silently absorbed.

Structural lint. Every published artifact is checked for dead exceptions, undeclared fields, and rules that decide unconditionally; findings block publication or are disclosed on the listing.

Versioned supersession. A corrected law is a new sealed version; the old one stays at its address, readable, marked superseded — the record is added to, never rewritten.

Offline verification. You do not have to trust this page: transcripts, seals, the catalogue and the public log all verify with published keys and zero-dependency scripts. A correction we failed to record here would be visible in the record itself.

Security findings: see /.well-known/security.txt. Specification errata are credited in the public standard's changelog.