Anvil Enginepart of Awairelocal · rushes stay on the workstation
Anvil Engine markAnvil Engine by Awaire

Editorial intelligence behind Awaire.

Anvil Engine is being built to help Awaire review prepared rushes locally against the brief, references and storyboards, and produce useful moments, structure and an evidence-backed first assembly suggestion. The editor reviews before use. Anvil's analysis is in controlled validation.

Brief-led.·Evidence-backed.·Editor-reviewed.

Anvil Engine is part of Awaire. Customers buy and use Awaire; Anvil explains the editorial-intelligence machinery behind the workbench.

analyse · part of awaire
Part of AwaireLocal-first by designFirst assembly suggestion (in development)
§ 01 · What Anvil Engine is being built to do

Useful moments. Structure. Evidence.

Anvil Engine is the editorial-intelligence engine behind Awaire. It is being built to help Awaire review prepared rushes locally and give the editor a traceable starting point, not a finished cut. Anvil's analysis is in controlled validation.

Capability
01

Reads prepared media locally

Built to help Awaire review prepared rushes on the workstation. Nothing is uploaded.

Capability
02

Groups useful moments

Built to cluster the moments most worth reviewing first.

Capability
03

Surfaces standouts

Built to highlight moments with source links and review context.

Capability
04

Drafts a first assembly plan

Built to help Awaire suggest a first path through the cut with reasons beside choices.

Capability
05

Traceable back to source

Every proposal points back to source clip, file path and timecode.

Capability
06

Brief and project context

The brief, references and storyboards shape what Anvil prioritises.

§ 02 · Workflow

A proposal, not an automatic edit.

Awaire does not finish the edit or change timelines. It proposes a reviewable path and waits for the editor. NLE handoff is in controlled validation — Awaire prepares package files and sidecar evidence, and the editor reviews and imports into Premiere or Resolve. This workflow is in controlled validation.

STEP · 01
Read context

Anvil uses the brief, requirements, storyboards, references, and intended structure to understand the job.

STEP · 02
Analyse

Designed to read prepared media locally, group useful moments, and keep evidence tied back to source clip and timecode.

STEP · 03
Suggest

Designed to build a reviewable first assembly suggestion with shot order and representative frames.

STEP · 04
Review

The editor reviews useful moments, evidence, and the assembly plan. Accept, change, or reject explicitly.

§ 03 · Local-first

Rushes intelligence designed to stay in the room.

Awaire is being built to review locally, produce traceable suggestions, and leave the decision with the editor.

Principle · 01
Local processing

Awaire review and proposals are designed to run on the workstation. The workflow does not require cloud upload.

Principle · 02
Source media unchanged

Awaire works from prepared media. Originals stay unchanged.

Principle · 03
No footage generation

Anvil reads what the camera recorded. It does not invent shots or produce material that was never captured.

Principle · 04
Traceable back to source

Every standout, every match, and every first assembly suggestion points back to source clip, file path, and timecode. Reviewable end to end.

Principle · 05
Editor decides

The editor reviews, accepts, changes, or rejects. Nothing is committed automatically.

Principle · 06
Suitable for sensitive material

Designed for NDA-heavy commercial work and documentary material where participant safety, privacy, and footage control matter. We validate these properties with each onboarded project during controlled access.

Awaire brings local intelligence to the rushes without sending the rushes to the cloud. Awaire is in controlled validation; some principles describe design intent and continue to be hardened.

§ 04 · Boundaries

What Anvil Engine is not.

Anvil Engine is part of the Awaire workbench. The boundaries below are deliberate — they keep editors in control.

Does not upload media
Prepared frames, briefs, and project context stay on the workstation. No cloud upload, no third-party retention.
Does not generate footage
Anvil reads what was actually shot. It does not invent shots or produce material that was never captured.
Does not edit the timeline
Anvil does not change timelines on its own. It is designed to produce traceable proposals for the editor to review, accept, change, or reject.
Does not finish the edit
A first assembly suggestion is review material for the editor, not a completed cut.
Not a separate licence
Anvil Engine is included with Awaire. No separate Anvil purchase, dashboard, or per-module decision to make.
Not a black box
Every proposal is designed to carry source clip, file path, and timecode, so the editor can trace any moment back to its origin.
Inside Awaire · controlled validation

Controlled validation. Onboarded in small batches.

Awaire is in controlled validation. We onboard projects in small batches so setup, data handling, and workflow feedback are handled properly. Anvil Engine is included behind the workbench — customers buy Awaire.

Controlled validationPart of AwaireSource unchanged
anvil.engine · summary
append-only
role:rushes intelligence · review · assemble
surface:Analyse / Review / Assemble stages of Awaire
compute:local · on the workstation
egress:no media uploaded
input:prepared review frames (from Forge Engine)
control:proposal · editor review
nle handoff:package files + sidecar evidence · editor imports
Anvil Engine never edits an NLE timeline on its own. Editor review is required for every proposal. Draft-only before export.