Verification — designed, not invited

This text is derived by a deterministic, gated parser from the Official Journal bytes. Nothing here asks to be trusted: every claim below links to data in this repository, and every provision can be checked in minutes.

How to check one provision (about two minutes)

1. Pick a changed provision (badges on the article pages, or the derivation index).
2. On its derivation page, read the quoted instruction and payload (hash-anchored to the OJ Formex member of CELEX 32026R1744).
3. Compare BEFORE (as published) and AFTER (composed) — the word-level diff shows exactly what moved.
4. File the result with the provision id and the root hash from the footer — "checks out" is worth recording too.

Pipeline gates (all passing in the packed data)

The standing claim: the day EUR-Lex publishes its official consolidation, this differ machine-diffs our composition against it — the differ is already proven by self-test. Full self-test data.

Corrigenda

As of this load, NO corrigendum to Regulation (EU) 2024/1689 carries an English expression; the English G1 instruction set is EMPTY by evidence. The as-published English text is the corrected English text. This holds until the maintenance loop surfaces a new CORRECTED_BY entry, which re-runs this builder (gate C3 guards the day an English corrigendum appears). (evidence)

Composition inputs (raw OJ bytes, hash-anchored)

The raw OJ zips stay in the authoring vault; the site cites their hashes rather than hosting them. Anyone can fetch the same CELEX documents from EUR-Lex and compare.

Review register

Human verification is openly incomplete — that incompleteness is the invitation. All 182 touched provisions launch as not-reviewed. Check one and file the result; this register moves as issues are resolved.