builderauto-generated · unproven

How do I generate only explicitly selected, planner-approved reference frames and cinematic video shots from an immutable project bundle. Preserve assigned Higgsfield/Runway providers and models, enforce an exact per-run spend grant, emit complete provenance and QA, and never plan scenes or compose the final video

the agent that answers this

Cinematic Shot Generator — Higgsfield + Runway. Generate only explicitly selected, planner-approved reference frames and cinematic video shots from an immutable project bundle. Preserve assigned Higgsfield/Runway providers and models, enforce an exact per-run spend grant, emit complete provenance and QA, and never plan scenes or compose the final video.

4 runsLast run 2mo ago1 on a scheduleUpdated Aug 16v3

Cost: Free; on your own plan
Runs: On demand; or scheduled
Built from: 11 steps; plain language
Runs in: Claude or Codex; as you

what you get

A bounded set of explicitly authorized, locally downloaded cinematic assets with updated manifest candidates, provider/model generation IDs, exact cost receipts, technical and creative QA, hashes, and portable artifact references—or typed per-shot failures without exceeding the signed spend and attempt ceiling.

example result

illustrative

A finished run delivers: A bounded set of explicitly authorized, locally downloaded cinematic assets with updated manifest candidates, provider/model generation IDs, exact cost receipts, technical and creative QA, hashes, and portable artifact references—or typed per-shot failures without exceeding the signed spend and attempt ceiling.

Example output, to show the shape of the deliverable. It has not run on your data. Build the agent to get this on yours.

the steps

11 steps

Step 1
Load the required approved project bundle by its bound artifact identity, validate its digest, and discover the production plan, generated-video request manifest, shot manifest, asset manifest, and provenance using relative paths. Treat narration, timestamps, claims, evidence restrictions, shot IDs, provider/model assignments, and approved treatments as immutable. Never rely on a hard-coded machine path.
Your model fills this step
Step 2decision
Parse the exact required shot_selection and admit only those shot IDs that exist in the generated-video request manifest and are eligible for generated video. Reject duplicates, unknown IDs, non-generated lanes, empty selection, or any implicit request for all remaining shots. Preserve the manifest-assigned provider/model and record the exact admitted set.
Decision step
Step 3decision
Parse the required spend_authorization into exact global and per-shot ceilings: approved providers/models, maximum credits and/or USD, and attempts per shot. Optional provider constraints may narrow but never broaden this authority. If approval is absent, ambiguous, or incompatible with the admitted set, hold before any paid call.
Decision step
Step 4tool
Preflight only the execution routes required by the admitted shots. Verify the authenticated Higgsfield CLI with a non-generating command for Higgsfield assignments; if auth is absent, run the supported login flow and hold for the user. Verify the Runway adapter and Implexa Vault authorization only for Runway assignments. Verify ffmpeg and ffprobe. Never request or expose secrets and never substitute providers/models.
Your model fills this step
- No integration? Use signed-in Higgsfield Computer Use only when an approved Higgsfield control is unavailable in the CLI and the manifest explicitly permits that surface.
- No integration? Return a typed provider_auth or unsupported_control blocker; never switch provider/model silently.
Step 5decision
Resolve reference-frame strategy separately from video generation. Record reference_frame_source/provider/model and video_provider/model independently. Permit generated frames only for non-factual creative imagery; never fabricate evidence, records, official documents, maps, branded interfaces, addresses, seals, personal data, or an allegedly real property/person.
Decision step
Step 6decision
Approval gate before the first paid invocation: prove that generation_authority is explicitly approved for this exact admitted shot set and current bundle digest. If not, return awaiting approval and do not call any provider. Approval never covers shots outside this run.
Decision step
Step 7tool
Generate each admitted shot through its manifest-assigned Higgsfield or Runway provider/model, sequentially enforcing the remaining global and per-shot ceilings before every invocation. Preserve exact prompts, negatives, references, dimensions, frame rate, duration/extension strategy, camera/lens/depth controls, and continuity. Poll to terminal status, download locally, and never treat submitted or processing as complete.
Your model fills this step
Step 8tool
Append a non-destructive attempt and provenance record for every success, failure, retry, and blocker. Record shot ID, provider/model, exact prompts and references, frame/video identities, generation IDs, timestamps, local relative path, measured media properties, attempt, spend, approval evidence, status, and any deviation. Never overwrite the planner's authoritative manifests.
Your model fills this step
Step 9tool
Validate every downloaded asset with ffprobe/FFmpeg for existence, full decodability, duration, dimensions, frame rate, codec, corruption-free playback, handles, and SHA-256. Extract representative QA frames and a review proxy for each video.
Your model fills this step
Step 10
Review each complete video end to end and inspect QA frames against the approved treatment: prompt adherence, camera/lens/depth behavior, continuity, flicker, morphing, malformed people or architecture, accidental text/logos/watermarks, evidence violations, and usable edit boundaries. Issue pass, retry, reject, or blocked per asset. Retry only within the same provider/model and remaining explicit authority.
Your model fills this step
Step 11decision
Produce a portable generation handoff without overwriting source manifests: generated assets, updated asset-manifest candidate, generation provenance, spend receipt, technical/creative QA, exact failures/blockers, and relative artifact paths. Confirm the output set contains only the admitted shot IDs, then hold for review rather than generating additional shots.
Decision step

Run this agent in Implexa, on your own Claude or Codex, free

Get the Implexa app (or connect your Claude Code / Codex), then say build the Cinematic Shot Generator — Higgsfield + Runway agent and approve the schedule. It runs as you, on your real data, on the subscription you already pay for, and gets sharper each run. Your agent's memory is yours and travels with you across Claude, Codex, and whatever comes next. About 5 minutes to your first real run.

Run this agent in Implexa →

common questions

How do I generate only explicitly selected, planner-approved reference frames and cinematic video shots from an immutable project bundle. Preserve assigned Higgsfield/Runway providers and models, enforce an exact per-run spend grant, emit complete provenance and QA, and never plan scenes or compose the final video?

The Cinematic Shot Generator — Higgsfield + Runway agent. A bounded set of explicitly authorized, locally downloaded cinematic assets with updated manifest candidates, provider/model generation IDs, exact cost receipts, technical and creative QA, hashes, and portable artifact references—or typed per-shot failures without exceeding the signed spend and attempt ceiling.

Is the Cinematic Shot Generator — Higgsfield + Runway agent free?

Yes. It runs on the Claude or Codex subscription you already pay for, so there is no extra AI bill and no per-run charge. You can build and run unlimited agents on the free plan.

How often does the Cinematic Shot Generator — Higgsfield + Runway agent run?

You choose: run it on demand, or put it on a schedule (hourly, daily, weekly). Once scheduled it runs unattended, as you, on your own machine.

What does the Cinematic Shot Generator — Higgsfield + Runway agent need to run?

Just Implexa installed in your Claude or Codex. There are no fragile integrations to wire up, and Implexa never touches your accounts, passwords, or the contents of your work.

Does the Cinematic Shot Generator — Higgsfield + Runway agent use my data? Is it private?

It runs as you, on your own machine, on your real data. The model runs inside your own Claude or Codex, so Implexa never sees your data, accounts, or credentials. Your agent's memory is yours and travels with you across Claude, Codex, and whatever comes next.

How do I build the Cinematic Shot Generator — Higgsfield + Runway agent?

Install Implexa into your Claude or Codex, then say "build the Cinematic Shot Generator — Higgsfield + Runway agent" and approve the schedule. Implexa assembles the 11 steps and it runs on its own. About 5 minutes to your first real run.

Can I change what the Cinematic Shot Generator — Higgsfield + Runway agent does?

Yes. Tell it what to change in plain language and it revises its steps; the next scheduled run uses the change, with no re-scheduling. Every change is versioned, and a run can even propose its own improvements.

changelog

v3Aug 16manual
Replace the old three-asset pilot with a reusable, budget-bounded typed cinematic-generation contract.
v2Aug 6manual
added 2 steps; rebound step 2 (gap -> decision), step 3 (clawhub/runapi-runway -> gap), step 5 (clawhub/runway -> gap), and more
v1Aug 6generated
auto-generated from "Generate production-ready cinematic B-roll video assets in Runway (via the Runwa"

Agents are alive: every change is a version, and a run can propose improvements that get reviewed and applied.