mirror of https://github.com/hanzoai/video.git synced 2026-11-03 04:21:39 +00:00

Files

T

calesthio 50891a75b7 hyperframes: add HTML/CSS/GSAP as a parallel composition runtime

Separates creative grammar (renderer_family) from technical engine
(render_runtime) so HyperFrames can stand alongside Remotion as a
first-class runtime instead of masquerading as a Remotion sub-case.
Locks runtime choice at proposal stage and enforces it end-to-end: the
schemas require it, video_compose routes by it, the reviewer fails
closed on silent swaps, and a parametrized contract test walks every
pipeline manifest to ensure each planning-stage skill explains the
conversation to the user. Adds hyperframes_compose (scaffold/lint/
validate/render/doctor/add_block), a playbook -> CSS style bridge, and
vendored HyperFrames Layer 3 skills from commit d291358, pinned via
PROVENANCE.md for future re-sync. Final_review now records
render_runtime_used and runtime_swap_detected so compose lies are
catchable after the fact.

2026-04-18 18:37:00 -07:00

2.7 KiB

Raw Permalink Blame History

Idea Director - Avatar Spokesperson Pipeline

When To Use

Use this pipeline when the deliverable is a presenter-led avatar video: a spokesperson spot, product intro, onboarding message, internal comms update, or short scripted explainer where the speaker remains the visual anchor.

Your first job is to classify the avatar path honestly before anyone writes polished copy for an impossible production setup.

Runtime Selection (MANDATORY — present the constraint, don't silently pick)

Lock render_runtime = "remotion". HyperFrames is NOT a valid runtime on this pipeline in Phase 1 — avatar-spokesperson depends on the Remotion TalkingHead composition and remotion_caption_burn, and neither has HyperFrames parity yet.

Per AGENT_GUIDE.md → "Present Both Composition Runtimes (HARD RULE)": do NOT silently default. Tell the user: "HyperFrames is available on your machine, but avatar-spokesperson depends on the Remotion TalkingHead composition and caption burn, so remotion is the only viable runtime here — OK to proceed?" Record a render_runtime_selection decision with hyperframes rejected_because: "TalkingHead + caption parity deferred on avatar-spokesperson".

Reference Inputs

docs/avatar-spokesperson-best-practices.md
skills/creative/storytelling.md
skills/creative/short-form.md

Process

1. Classify The Avatar Path

Record which production mode the project actually has:

platform_avatar
photo_talking_head
presenter_plate_lip_sync

Also record whether the avatar already exists or still has to be created outside the current run.

2. Define The Message Shape

Capture:

audience,
core offer or CTA,
runtime target,
platform targets,
whether the video is sales, onboarding, support, or announcement led.

Spokesperson videos work best when they have one clear job.

3. Capture Source Reality

The brief should explicitly state:

whether clean narration is supplied,
whether TTS is acceptable,
whether brand backgrounds or overlays exist,
whether subtitles are required,
whether multilingual variants are expected.

4. Build The Brief

Recommended metadata keys:

avatar_path
avatar_exists
narration_source
target_audience
cta_type
background_strategy
deliverable_mix
missing_capabilities

5. Quality Gate

the avatar path is explicit,
the message is narrow enough for a spokesperson format,
missing narration or avatar dependencies are visible early,
deliverables fit the actual source setup.

Common Pitfalls

Treating a generic generated-video request as a deterministic avatar workflow.
Writing the CTA before confirming the avatar and narration path.
Planning multiple aspect ratios before the hero layout is proven.

2.7 KiB Raw Permalink Blame History