Integrity

Five families of test over this record’s own data. Each states the question in words, the population it was asked over, and what it found on 2026-09-18.

10 findings across 2 of 5 families. A finding here is a fact about the DATA — a date, a referent, a verification event — and this board reports it rather than stopping the build: the lane that can repair a row is not always the lane that runs the test. What does stop the test is a failed read, because a check whose extraction came back empty would turn silence into a receipt.

TEMPORAL 1 finding

The question: A dated event about a document may not fall before the year the document's own designator carries. `Regulation (EU) 2026/1744` cannot have an event in 2024.
Population: 13 calendar event(s) whose row carries a number-year in its title
Test: temporal.number-year-precedes-event
Known-satisfying row: eu-cyber-resilience-act — a 2024-numbered act with an event dated 2027-12-11 — later than its own number-year, which is the satisfying shape. This family must stay silent about it. If it does not, nothing here is published: a test wrong about a row whose answer is known is a reader whose other findings cannot be trusted.

TEMPORAL — 1 finding(s)
Entry	What	Why it is a finding
`eu-digital-omnibus-ai`	effective_date dated 2024-08-01	the designator's own year is 2026; a dated event about it cannot precede the year it is numbered for

REFERENTIAL 9 findings

The question: A row that declares its address is the document must hash the document. Where the referent audit finds the address serves a hub, a listing or another artifact, the two disagree and neither is silently preferred.
Population: 132 audited row(s)
Test: referential.declared-vs-served
Known-satisfying row: astm-e2363 — declared a document, and the referent audit returned AUDITED-OK: the row and the address agree. This family must stay silent about it. If it does not, nothing here is published: a test wrong about a row whose answer is known is a reader whose other findings cannot be trusted.

REFERENTIAL — 9 finding(s)
Entry	What	Why it is a finding
`astm-e2537`	declared a document; the audit disagrees	the referent audit found the address serves something other than the document this row names
`health-canada-ml`	declared a document; the audit disagrees	the referent audit found the address serves something other than the document this row names
`iso-iec-27017-2026`	declared a document; the audit disagrees	the referent audit found the address serves something other than the document this row names
`iso-iec-27018-2025`	declared a document; the audit disagrees	the referent audit found the address serves something other than the document this row names
`iso-iec-42001`	declared a document; the audit disagrees	the referent audit found the address serves something other than the document this row names
`nist-ai-rmf-playbook`	declared a document; the audit disagrees	the referent audit found the address serves something other than the document this row names
`nist-csf`	declared a document; the audit disagrees	the referent audit found the address serves something other than the document this row names
`us-21-cfr-part-820`	declared a document; the audit disagrees	the referent audit found the address serves something other than the document this row names
`who-trs1033-annex4-data-integrity`	declared a document; the audit disagrees	the referent audit found the address serves something other than the document this row names

TYPE no finding

The question: An attribute exists on a type only where the publisher can state it. A row whose publisher states it is not a document may not publish a document's lifecycle status.
Population: 0 row(s) with a stated non-document object type
Test: type.attribute-excluded-by-object
Known-satisfying row: astm-e2363 — object type `document` with a published status — the attribute its type can carry. This family must stay silent about it. If it does not, nothing here is published: a test wrong about a row whose answer is known is a reader whose other findings cannot be trusted.

No row in that population answers the question the wrong way. A zero here is a measured zero: the fixtures in scripts/integritygates.py require this family to produce a finding against a seeded row before its real result is trusted, so a family that reports nothing has been shown capable of reporting something.

PROVENANCE no finding

The question: A published human verification needs a recorded act behind it. A row saying a person checked it, with no event naming the actor and the date, is a claim with no receipt.
Population: 60 row(s) publishing a human verification
Test: provenance.verified-without-event
Known-satisfying row: fda-device-cybersecurity-2026 — publishes a human verification AND has the event behind it; the id ends in a year, which is what the reader once mangled. This family must stay silent about it. If it does not, nothing here is published: a test wrong about a row whose answer is known is a reader whose other findings cannot be trusted.

RECONCILIATION no finding

The question: A figure a reader meets on two surfaces derives from one function. Where the store and the page carry the same named figure, they must carry the same value.
Population: 7 comparison(s): figures published on both the store and the page, plus populations counted under more than one name across stores
Test: reconciliation.figure-on-two-surfaces
Known-satisfying row: front-door — a figure published on both the store and the page, carrying the same value on each. This family must stay silent about it. If it does not, nothing here is published: a test wrong about a row whose answer is known is a reader whose other findings cannot be trusted.

What this board does not do

It does not repair anything, and it does not rank its findings. A date that precedes its own document’s year and a verification with no recorded act are different problems, and putting them in an order would be this record ranking them — which is the one thing it will not do. Each finding names the entry it is about; the entry’s own page carries what the record holds.

Last updated: 18 September 2026