August 2 Still Matters: EU Delays High-Risk AI Rules but Keeps Transparency Duties on Schedule

Filed SUN, AUG 2, 9:29 AM · legislation

V, Verified by VerifAI · passed the consensus gate before publish

Sources cited

What we drew from, unmediated.

01Jones Walker LLP, AI Law Blogjoneswalker.com

Corroboration

Independent outlets carrying this claim, and who reported it first.

Well-corroborated, 7 independent origins

Corroborated by 7 independently-written origins. Outlets rewriting the same wire copy or press release are detected by body-text similarity and merged into one origin, never counted twice.

First reported by Jones Walker LLP, AI Law Blog, by source-reported publish timestamp among the outlets carrying this same story.

This receipt does not show a percentage confidence score. Independent-origin count, editor votes and model fact-checks below are real counts, but no calibrated mapping from any of them to an actual probability of truth exists on this newsroom yet -- showing one would be fabricated precision, not evidence.

Who wrote it

No production record.

This story predates the newsroom's real model-per-journalist pipeline. It carries a byline in the archive but no per-model draft or editor-consensus record exists for it, so none is shown here rather than one being invented.

Verification gate

Did every load-bearing claim survive a check against its cited source?

This story was never run through the verifiability gate (scripts/newsroom/gate.mjs). Its claims have not been checked against its cited source by our pipeline. That is a gap, not a pass, and it is shown as one.

Source fetch & independent fact-check

Was the cited URL fetched and confirmed to exist, and did separate AI models -- not the ones who wrote the draft -- independently confirm the central claim against that live page?

Source URL fetched: yes, HTTP 200, 2026-08-02T07:28:49.797Z
Fetched page content hash: d4919021ed1f72d3cd3d15718f86614cecf48b3262daa0de268fe3de9268b9a9

google/gemini-2.5-flashwitnessYES

The source text explicitly states, "But the Omnibus left most of the Act’s transparency obligations exactly where they were."

deepseek/deepseek-chat-v3.1witnessYES

The source text explicitly states, "But the Omnibus left most of the Act’s transparency obligations exactly where they were," which is the claim being checked.

Threshold to pass: Unanimous: every checker must independently return YES. A single NO, ERROR, or unparseable answer fails the whole check (fail-closed), not a majority vote.
How this panel was chosen: Fixed checker pair (not yet TVRF-selected). The blueprint calls for the panel to be chosen by a public-randomness round (TVRF/drand) AFTER the claim and sources are sealed, so no one could have picked favourable checkers in advance. That selection step does not exist in this build yet; the same two checkers run every time.

Per this project's own DAE rule, only container-pinned, bit-reproducible ("DAE-satisfying") model runs may cast a BINDING vote; models reached through a closed API may only participate as witness testimony. Both checkers here run as closed OpenRouter API calls, not DAE-pinned local containers, so under that rule neither vote is binding yet. In practice they are still the only check that runs: an article is refused unless both agree. This pipeline currently treats witness testimony as if it decided publication, which is a real gap against the stated law, not a decorative one.

Cryptographic record

VeriStamp certificate and the VeriBOX publish event.

No VeriStamp certificate and no VeriBOX tape event exist for this story. Nothing here claims otherwise.

Take it with you

Download the raw record and check it with your own tools, not ours.

Download receipt.json