Why record the narration before editing?

The picture follows its real word timings, especially the rolling verbs. Replacing the read afterward changes beat boundaries and word alignment. Lock and transcribe the final recording instead of forcing a new read into existing scene lengths.

Why remove narration over the walkthrough?

That is the interval viewers need to read the step cards and terminal commands. A competing voice would split attention. The reference raises the music through the pause so it feels intentional.

Is a downloadable partner logo enough for this workflow?

No. The package requires agreement to this specific announcement film, recording who approved it and when, as well as the presenter’s consent. Treat those as production inputs rather than inferring approval from an available logo file.

Can the film say an integration is available before it is live?

Its wording should match the actual state. A coming-soon announcement and a currently available workflow make different claims; do not let the shared lockup or working-looking terminal imply availability that has not been established.

Does the package include footage or a ready-made project?

It contains production and craft references. You supply approved footage, marks and narration, and the agent authors the HyperFrames project and final MP4. It does not provide a presenter or establish partnership approval for you.

Partnership Announcement Film

Previews from the publisher

Announce an agreed partnership through a presenter, two-brand lockup and a short operational walkthrough. Partnership Announcement cuts to the recorded narration’s word timings, leaving a deliberate speech-free interval for viewers to read the commands. A rolling verb list, presenter return and white close connect the joint statement to what users can actually do.

What you get

A production method for a twenty-four-to-forty-second, 1920×1080, 30 fps H.264/AAC MP4 in seven beats: treated presenter, two-mark lockup, count, step-card/terminal walkthrough, rolling verbs, presenter close and fade to white.
An editable-project plan timed to a locked word-level transcript, including per-beat compositions, narration, metadata and the original presenter footage.
Treated-window and read-alignment craft: border and mask reveals for the presenter, four verbs landing on their spoken words and a walkthrough with no narration competing with the commands.
A two-background transition discipline with one crossfade at the colorway change and hard cuts elsewhere. The guide-only archive supplies the production references; the agreed announcement and final MP4 are outputs to author.

Before you choose

Choose this for a genuinely joint announcement with a useful short workflow. Lock the shared statement and command sequence before shooting or cutting, then let the transcript drive the pace. The strongest ending is clear agreement plus something the user can actually try, not a two-logo card alone.

Good fit

Two companies that have agreed to a specific partnership announcement.
A team with approved presenter footage, a locked read and real working commands for the walkthrough.
A short workflow worth reading on screen; the reference reserves roughly seven seconds for that purpose without narration.

Not for

A one-sided compatibility claim, customer-logo wall or an unagreed “works with” announcement.
A production lacking the partner’s recorded sign-off for this specific film or the presenter’s consent required by the package workflow.
A film with no narration, because the beat lengths and closing verbs derive from a spoken read.

How to use

You say

/hyperframes-partnership-aroll-launch Announcement film for our integration. Narration and A-roll attached, both logos approved.

Confirm the actual relationship and announcement status and collect the partner’s film-specific approval, both marks and the presenter’s permitted footage. Distinguish a live integration from one that is only coming soon.
Record and lock the narration, then obtain its word-level transcript. Gather the walkthrough count, matching step labels, real commands and four closing verbs; the reference demonstrates three commands, but the count must match your actual sequence.
Prepare HyperFrames CLI, Node.js 22 or newer and FFmpeg and locate the referenced audio/window/motion guidance. Derive beat boundaries and verb onsets from the recorded words before authoring picture timing.
Build the treated presenter window, lockup and counted walkthrough, preserving two background roles and one crossfade at their change. Leave the command-reading interval free of narration, lifting the music deliberately rather than making the pause sound accidental.
Check each verb against its spoken word and verify the displayed commands and results. Review presenter masks and transitions, run documented project/output checks and inspect final dimensions, frame rate, duration and audio. Keep approval records, narration provenance and command evidence with the handoff.

Requirements and costs

You bring: The narration, recorded and locked, with a word-level transcript · The presenter's footage, with their written consent · Both marks, and the partner's written permission for this film · A count, that many step labels, and the real commands · Four verbs, one per beat of the closing line
Dependencies: HyperFrames CLI — required · Node.js 22 or newer — required · FFmpeg — required
Outside costs: Not collected yet
Tools used: HyperFrames
Publisher testing: v1.0.0 — Claude Code / Claude Desktop / Cowork / Codex / ChatGPT