01Falsifier — what changes this claim
A controlled violation of a required registry field, bound-evidence trigger, or review window reaches a successful named CI workflow, or the workflow no longer runs on pushes to main and weekly.
Consequence REJECTThis is the condition and consequence recorded in the registry. The vocabulary this is published in defines what each consequence commits the author to.
02Scope
The verifier at the recorded content hash, and the public workflow that runs it. The generated-page and figure checks are separate steps in the same workflow (ledger, modules, observatory, figure geometry, internal links).
03Forbidden rescues
Repairs declared unavailable in advance; using one after a failure would breach the recorded commitment.
- do not cite a normal green run as evidence that violations are rejected
- do not count a manual review or a generated-page drift check as automatic schema, trigger, or freshness enforcement
- do not treat a warning-only or report-only job as a build failure
04Non-claims — what this does not license
- a green run verifies registry consistency and quiet triggers, never the truth of any claim's content
- an UNDETERMINED run (exit 2) blocks the build because a source was never reached; it is not a finding about any binding, and must not be read or recorded as a failed check
- triggers watch file content; semantic drift outside watched files remains a manual review event, and the ledger says so
05Binding and freshness