How do I produce a verified Remotion master from typed inputs and a frozen scene_execution_contract. Final production requires eight approved, verified Higgsfield Kling 3.0 assets bound into their authorized Master timeline ranges; no-cost fallbacks are only for preview, explicit decline, or typed provider/auth/generation failure

the agent that answers this

Visual Evidence & Remotion Compositor. Produce a verified Remotion master from typed inputs and a frozen scene_execution_contract. Final production requires eight approved, verified Higgsfield Kling 3.0 assets bound into their authorized Master timeline ranges; no-cost fallbacks are only for preview, explicit decline, or typed provider/auth/generation failure.

• Step 1tool

  Preflight the local production stack before ingest by consuming the exact Desktop launch-attestation and executor-capability-route evidence for available disk, the managed Node/npm runtime, strict npm-registry TLS and its selected CA mode, FFmpeg, ffprobe, and Desktop-attested Higgsfield installation, authentication, and Kling 3.0 model availability. A READY entry is authoritative readiness for this exact launch, not proof that the capability was used. Do not run worker-owned version, status, HTTPS, npm-registry, setup, or installation probes merely to reconfirm it, and do not select, override, or persist a worker-authored CA mode or executor environment; Desktop already froze the non-secret CA mode, executor-environment digest, and exact executable identities. React, TypeScript, and Remotion are project dependencies to install and verify through step 9, not machine-readiness probes. Raw Higgsfield CLI, configuration, credentials/authentication, provider network access, and spend are intentionally denied to the model; this denial is expected isolation, not failed Desktop readiness. Consume only the broker-owned route and Desktop readiness evidence for those Higgsfield requirements. Never probe the raw provider surface or self-record broker-owned capability proof, including through record_capability_usage. Begin actual no-cost work on the declared non-broker routes. Record record_capability_usage outcome=used for a non-broker requirement only after its role is actually performed. If an authorized non-broker invocation or Desktop tool returns a typed capability-loss reason during actual work, record unavailable only for that exact requirement and stop; a generic project, dependency, or tool error is not proof that a capability disappeared. Report exact blockers. Do not perform worker-owned installation, authenticate, weaken TLS, mutate npm configuration, or incur cost silently. This is execution policy only: add no input fields or activation-time file requirements.

  Your model fills this step
• Step 2

  Resolve project_bundle and presenter_video only through their Desktop-bound identities and digests. Validate any editable revision capsule inventory and continuation lineage without reopening hidden workspaces; discover ordinary bundle contents only through relative internal paths. Verify presenter custody against its declared binding, never trust prompt paths or copy/cache the large source. Compile and persist the authoritative run-specific quality brief from frozen Manager decisions, exact-attempt approved learnings, and planner contracts; an accepted manager-quality-bar is optional read-only enrichment, never a required input or source authority. Preserve Manager handling/proof. For an ordinary full-duration working MP4 with no authorized editorial cut, invoke exactly once the Desktop materialize-presenter adapter and use only its returned receipt-bound output; reserve render --plan for separately approved editorial work. When optional revision_source_video is supplied, resolve it only through its Desktop-bound immutable identity and digest; verify stable no-writer state plus ffprobe, full decode, duration, resolution, fps, and audio. Treat it as authoritative visual starting-point evidence only; presenter_video remains the source and audio authority. If invalid, stop with a typed needs-input result before any provider or render work. Revision mode is elected only when both revision_source_video and revision_capsule are bound. Resolve the capsule only through its Desktop-bound identity and digest; validate stable no-writer state, archive integrity, inventory, complete Remotion source/timeline, composition ID, dependency lock, scene/asset/provenance manifests, presenter adapter binding, prior QA, and recorded Master digest. Require that recorded digest and media identity to equal the bound revision_source_video. Compile the exact current-run feedback into an authorized_revision_set, then freeze the Master hash, capsule hash, composition ID, and authorized set. When neither revision_source_video nor revision_capsule is supplied, continue as a fresh build using project_bundle and presenter_video; no revision-only requirement may block this mode. When either revision input is supplied, require both exact Desktop-bound, lineage-matched revision inputs; if the pair is incomplete, mismatched, invalid, or not editable, stop with editable_revision_source_required before provider, dependency, preview, or render work. Never reconstruct an editable project from the MP4, planner bundle, presenter, screenshots, or reference frames.

  Your model fills this step
• Step 3decision

  Compile the run-specific quality brief before production from frozen Manager stage decisions, owner-approved learnings, and planner creative-direction, visual-evidence, scene, timing, and fallback contracts; persist identities and digests. Never invent a required third input or search another run. Enforce narration-matched supporting visuals, entrances after their spoken anchors (target 150 ms, never before), varied evidence/layouts, no burned-in captions or production metadata, continuous source audio, and sustained purposeful motion after entrances. Preserve all Manager handling/proof requirements. Required Manager/Judge acceptance criterion provider_temporal_correspondence: every one of the eight Kling/provider clips must demonstrate non-trivial source motion and monotonic rendered/source temporal correspondence over its complete intended 5.04-second source interval, before preview approval and again against the final Master. Treat this as required evidence in the frozen quality brief, not a worker assertion; preserve all existing Manager handling, Judge, and final Review settlement. Fresh builds are eligible for current-version, explicitly reaccepted training decisions from predecessor session 4078c483-98ee-4937-84e4-2b44f0db4db4 and source d9ce52ac-b72d-4460-83b4-e7b7e6b8ca6c only through supported successor acceptance with durable source/evidence custody. Never select predecessor-only records or fabricate readiness. The training authoring stages are exactly planning, scene_contract, asset_selection, build, preview, qa, revision; admission and render are not training acceptance stages. Run-specific revision coverage activates only under the exact verified revision input mode; the other six creative-stage policies also apply to fresh builds.

  Decision step
• Step 4

  Inspect the complete planner bundle, transcript, scene records, quality brief, and optional accepted quality reference as read-only evidence. Treat compositor-scenes.json and supplied Remotion TSX only as editable semantic/timing scaffolds. Synthesize and persist a run-specific scene_execution_contract for every planned scene from valid narrative, transcript, visual-evidence, generated-shot, timing/fallback, Manager, and learning contracts; preserve source timestamps, scene boundaries, continuous presenter audio, evidence constraints, uncertainty, asset identities, and authorized fallbacks. Block only invalid required timing/evidence/source identity or insufficient semantic information. When optional revision_source_video is supplied and valid, bind requested feedback to that exact digest-bound revision artifact while preserving the existing planner, presenter, Manager, and evidence authorities. In revision mode, extract the verified revision_capsule as the sole editable project lineage and open its exact composition entry. The project_bundle remains planning and evidence authority only and must not replace the capsule timeline, layout system, styles, animation code, fonts, or asset bindings. Bind every requested change to the authorized_revision_set; all other properties and ranges are immutable by default.

  Best practices for Remotion - Video creation in React

  --- name: remotion-best-practices description: Best practices for Remotion - Video creation in React metadata: tags: remotion, video, react, animation, composition --- ## When to use Use this skills whenever you are dealing with Remotion…

  Full skill: Remotion Best Practices
• Step 5decision

  Classify every planned visual and complete the persisted scene_execution_contract for every scene: narration anchor, exact frame range, evidence/asset identity, treatment, animation family and unique motion signature, transition, text and presenter treatment, and fallback. Choose semantically among presenter-only, editorial, kinetic type, cards, counters, charts, diagrams, maps, evidence, cinematic B-roll, picture-in-picture, and mixed composites; preserve factual evidence, planner fallbacks, unresolved-scene reporting, and at least three previewed treatment families. Forbid decorative variety, invented facts, repeated titles, template repetition, and adjacent identical motion signatures. For each generated/provider clip, freeze its own local Remotion Sequence, authorized Master entrance, local source start (frame 0 unless an explicit authorized source offset exists), intended source interval of exactly 5.04 seconds, source and Master fps/timebases, and frame/PTS mapping. Require the entire intended interval to fit the authorized range and source duration; fail closed on incompatible timing instead of trimming, retiming, extending the authorized range, clamping, or looping without explicit authority.

  Decision step
• Step 6

  Ingest each supplied clip and small asset declared by the current bundle, verify identity/digest, and use portable relative-path copies only in the editable project. Before any production asset generation, parse the planner bundle into a generation bundle and validate it contains exactly eight, and only eight, well-formed Higgsfield Kling 3.0 video requests with stable scene/request IDs, bounded prompts, model, resolution, authorized scene/frame range, and deterministic asset destination. Persist every request as planned_not_submitted. Reject malformed, missing, duplicate, substituted, unbounded, or non-Kling requests. Do not invoke Higgsfield in this stage. If optional preserved_provider_batch is present, before approval or generation and through Desktop-bound custody only, require one manifest, exactly eight receipt JSON files, and exactly eight MP4s. Fail closed unless stable regular-file identity; SHA-256; decode; duration; model; resolution; provider terminal status; original request/run/launch identity; and a one-to-one match to the current project bundle's exact eight frozen scene/request IDs, prompts, models, resolutions, destinations, and authorized frame ranges all validate. Reject missing, duplicate, substituted, extra, mutable, or mismatched entries. If validation succeeds, persist reuse_verified_provider_batch with its manifest digest and source lineage; historical receipts are evidence only and grant no settlement, replay, or spending authority. If validation fails, stop before any provider call and do not silently fall back to new paid generation. When optional revision_source_video is supplied and valid, record its bound digest and revision intent in current-run project evidence; it confers no provider authority and does not alter preserved_provider_batch validation.

  Your model fills this step
• Step 7tool

  Acquire approved authoritative evidence and real contextual sources for scenes that require them. Open the actual primary source, capture or download the highest-quality usable local asset, and record URL, publisher, title, capture date, license/usage basis, supported claim, relative path, and digest.

  Your model fills this step
• Step 8tool

  Use the current engine's authenticated browser or Computer Use only when an approved source requires interactive navigation or download. Confirm the relevant signed-in identity, redact private data where required, save locally, and never hotlink.

  Your model fills this step
• Step 9tool

  After all planning and evidence acquisition are durably complete, and before paid manifest approval or any provider execution, install and verify editable Remotion-project dependencies exactly once in the current extracted project using its immutable bundled package-lock.json. Validate lockfile/root/dependency coverage. Consume exactly the launch-bound Desktop CA-mode and executor-environment authority without inspecting, reproducing, re-probing, selecting, or overriding it. Invoke the Desktop MCP tool prepare_paid_project_dependencies exactly once with projectRootRelativePath. This tool exclusively owns the foreground locked npm ci, strict sandboxed registry configuration, installed-tree publication, and project-local browser installation. Do not run a second worker-owned install, readiness probe, or network setup. Do not force NODE_USE_SYSTEM_CA=1, switch CA modes, or retry installation under another environment. Preserve existing timeout requirements and keep the foreground invocation attached/polled through its terminal exit; a timeout is a failure, never permission to start a second install. Never disable strict SSL, set NODE_TLS_REJECT_UNAUTHORIZED=0, install certificates, or mutate user/global npm configuration. Immediately before this actual local-tool use, Desktop revalidates the exact frozen executor-capability policy. If the tool returns a typed capability-loss refusal, stop and record unavailable only when the refusal identifies the exact affected non-broker requirement; any other preparation error is dependency_install_failed, not proof that a machine capability disappeared. After success, record record_capability_usage outcome=used only for each non-broker requirement whose role the successful preparation actually performed; never self-record a broker-owned Higgsfield requirement. Record the chosen non-secret CA mode from launch evidence and the Desktop preparation command/receipt and terminal exit/timeout as QA evidence; do not invent or repeat preflight probe commands or exits. Never regenerate/repair the lockfile, run npm install/force, overlap installs, or mistake output yield for completion. On nonzero, certificate failure, or incomplete node_modules, stop as typed dependency_install_failed. Only after exit 0 and installed-tree verification run TypeScript and composition discovery sequentially and record commands, exits, and QA evidence; maintain monotonic durable stage heartbeats. Complete all no-cost local dependency, TypeScript, composition-discovery, and project validation in this stage, before spend. Persist digest-bound project, immutable-lock, installed-tree, TypeScript, composition-discovery, and project-validation results and obtain an accepted durable step-9 passing checkpoint before step 10 is eligible. Never install or repair dependencies after a provider call; missing or failed dependency/project proof blocks paid approval and execution. Preserve exactly one npm ci and all existing strict CA, terminal-exit, timeout, no-retry, and no-lockfile-repair safeguards. Before this stage may pass, complete the entire editable composition and all creative source work specified by steps 13 and 14, including the exact entry point, composition ID, timeline, scene/layout/animation code, styles, fonts, source-local playback clocks, loader destinations, deterministic fallback branches, manifests, render scripts, QA scripts and frozen numeric QA thresholds. Obtain the build-stage Manager context before this creative work and preserve its frozen handling/proof; the later build policy seam verifies that same stage authority rather than creating a new creative pass. Complete planning and evidence downloads before freeze. All eight future provider destinations and source-local-to-Master frame mappings must already be implemented; absent not-yet-approved provider outputs are planned slots, never claimed as generated or verified. Final 8/8 artifact/insertion/temporal proof remains mandatory after actual provider outputs arrive. Use the preserved Remotion skill bindings and all scene/timing/revision constraints in steps 13 and 14 while authoring now. After prepare_paid_project_dependencies returns success and all creative preparation is complete, call verify_paid_project_checkpoint with exactly projectRootRelativePath, entryPointRelativePath, compositionId. Require its accepted desktop-paid-project-checkpoint-receipt.v1 containing checkpointId and checkpointDigest and returned projectRootRelativePath. Freeze the exact Desktop-owned snapshot and persist those identities; a prose claim or dependency-only pass is insufficient. The accepted checkpoint and paid approval begin an immutable execution phase. Keep creative source, dependencies, browser installation, and evidence acquisition frozen throughout that phase. Continue only through Desktop-owned provider outputs at frozen destinations, deterministic receipt/evidence generation, rendering, QA, and existing approval/delivery settlement. Any needed source change fails closed and requires a separately authorized preparation/checkpoint cycle; do not mutate the approved snapshot or retry a provider job.

  Your model fills this step
• Step 10decision

  Only after step 9 passed durably, validate exactly eight current-run Kling requests and obtain a read-only cost estimate for each only through the broker; if exact request details cannot be loaded, fail closed. Except on the verified preserved_provider_batch no-spend branch, declare exactly one application/json manifest with contractVersion "paid-action-request-manifest.v3", provider "higgsfield", operation "kling3_0.video_generation", currency "USD" or "credits", and the complete current run's Desktop-bound input set as inputs [{semanticKey,displayName,artifactId,sha256}]. displayName is basename-only and input identity comes only from immutable current-run bindings, never a prompt or local path; require project_bundle and presenter_video. requests contains exactly eight unique safe IDs. Every request object has exactly these fields and no others: requestId, sceneId, prompt, sourceRange, model, resolution, durationSeconds, estimatedCost, intendedUse, outputRelativePath. Retain sourceRange:{startFrame,endFrame} as bounded integer half-open frame ranges, bounded six-decimal cost, and exact total. Require model "kling3_0", resolution "1920x1080", durationSeconds 5; the fixed Kling 3.0 execution contract is mode pro, aspect ratio 16:9, sound off. Mode, aspect ratio, and sound are fixed execution settings, not extra request-object fields. The authorized scene range must contain the provider’s complete approximately 5.04-second result, preserving the existing full-interval temporal-correspondence contract. Resolve each outputRelativePath only from the project bundle asset-manifest planned_asset whose requestId matches, requiring one unique matching asset and exact equality with its unique materializeTo value. Require a safe relative public/media filename ending in.mp4; reject traversal, symlinks in the destination or any parent, duplicate destinations, absolute paths, invented destinations, and any mismatch. Display all eight exact outputRelativePath destinations with their corresponding requests in owner approval. Keep every request planned_not_submitted until authority exists. Pre-approval provider preparation may use only the broker and deferred/non-spending identifiers; it must not submit a provider job, invoke raw Higgsfield CLI/config/auth/network access, incur spend, or manufacture provider execution identifiers. Desktop readiness supplies installation/auth/model-availability evidence; the model must never self-record broker-owned capability proof or treat readiness, estimates, deferred identifiers, or prepared inputs as used capability proof. Persist the strict typed partialOutcome with contractVersion "brokered-paid-action-approval.v1", holdKind "approval_before_action", requestManifestArtifactId, requestManifestDigest, projectCheckpointId, and projectCheckpointDigest, then stop. projectCheckpointId must echo the exact accepted checkpointId returned by verify_paid_project_checkpoint and projectCheckpointDigest must echo its exact checkpointDigest. Never invent either identity or substitute a digest-only dependency report. Do not infer authority from an earlier run, purchase, license, login, or broader permission. If reuse_verified_provider_batch is present, verify its manifest digest and source lineage against the current run, preserve the verified no-spend branch, and continue without paid-action authority. Bind the step-9 durable passing dependency/project proof into paid-approval eligibility; prepared inputs or an unaccepted checkpoint do not qualify. Preserve every existing v3 identity, input, estimate, exact-eight, manifest artifact/digest, and no-spend rule.

  Decision step
• Step 11

  Only after explicit owner approval of the exact frozen batch is durably recorded, invoke only the scoped Implexa MCP tool execute_approved_paid_action exactly once for each exact frozen requestId. Never call the Higgsfield CLI, API, or browser directly, and never pass or change prompt, model, resolution, duration, or cost. The Desktop parent exclusively owns the provider call, HTTPS download, symlink-safe atomic write to the exact frozen outputRelativePath, SHA-256, size, ffprobe resolution and duration verification, durable receipt, and replay recovery. The worker must never call Higgsfield, curl, another provider route, or download any output URL itself. Consume only execute_approved_paid_action's immutable local outputArtifact identity and bind it directly to the matching project-bundle planned asset, its exact materializeTo/outputRelativePath, and the composition loader path. Verify matching immutable identities and declared binding evidence; an output URL or worker-invented path is never an outputArtifact. A recovery or replay must consume the Desktop-owned settled receipt and verified local artifact without resubmitting a completed provider job. If authority is declined, or a typed provider/auth/generation failure occurs, use only the declared no-cost fallback and mark the result clearly partial/preview; native diagrams or other no-cost fallbacks are never final-production substitutes. Do not claim final production from a native-only or incomplete generated-asset result. If reuse_verified_provider_batch is present, preserve the existing verified preserved_provider_batch no-spend branch: never call a provider, rebind all validated assets into current-run provenance, and prove their 8/8 authorized Master-timeline insertions. If preserved-batch validation failed, this step is forbidden. Except for the existing verified preserved-provider no-spend branch, require eight of eight distinct approved requests, claims, settled receipts, verified immutable outputArtifact identities, and declared final asset bindings before successful artifact, Judge, Manager, or final completion. The exact approved request set must equal the claim, settled-receipt, verified-artifact, and declared final-asset-binding sets with one-to-one request/scene/destination/loader identity correspondence. Zero, subset, extra, mismatched, wrong-path, wrong-size, wrong-duration, stale-fence, or unresolved claims fail closed without resubmitting a completed provider job. Desktop verification must prove each artifact's SHA-256, byte size, 1920x1080 resolution, and complete approximately 5.04-second duration against its fixed five-second Kling request and authorized scene range. Preserve no-spend reuse only after existing exact-eight preserved-provider validation and current-run rebinding; never fabricate current-run claims, approval, or new settlement for historical receipts. Execute only against the exact approved Desktop checkpoint snapshot. Consume provider outputs into its already-frozen loader destinations without changing source, manifests that define composition behavior, styles, timing, code, dependencies, or QA thresholds. Never perform a network/dependency/browser install after approval. Desktop/backend settlement exclusively supplies immutable used capability proof for higgsfield_cli, higgsfield_auth, and higgsfield_model_access, bound to the exact current request, run, launch attempt, fencing epoch, provider CLI identity and provider identity digest, explicit owner approval, and the approved higgsfield/kling3_0.video_generation route with execution_mode desktop_broker_after_approval. The model must never self-record, synthesize, or substitute broker-owned capability proof, including through record_capability_usage. For each executed approved action, require its matching settled broker proof in addition to the existing receipt and artifact evidence; missing, mismatched, stale, or unbound broker proof after execution fails closed before successful artifact, Judge, Manager, or final completion, without resubmitting a completed provider job. Preserve the verified historical no-spend branch without fabricating current-run used proof.

  Generate images and videos via Higgsfield AI through 30+ models including Nano Banana 2, Soul V2, Veo 3.1, Kling 3.0, Seedance 2.0, Flux 2, GPT Image 2, plus...

  --- version: 0.3.0 name: higgsfield-generate description: | Generate images and videos via Higgsfield AI through 30+ models including Nano Banana 2, Soul V2, Veo 3.1, Kling 3.0, Seedance 2.0, Flux 2, GPT Image 2, plus Marketing Studio for…

  Full skill: Higgsfield Generate
• Step 12

  Create a provenance receipt for every supplied, sourced, captured, licensed, and generated asset, bound to scene IDs and supported claims. For each of the eight generated assets record request ID, exact Kling 3.0 model/resolution, provider job terminal result, relative path, SHA-256, media validation/duration, authorized scene/frame range, privacy treatment, and actual fallback if applicable. Confirm nothing is hotlinked and fail closed on missing, duplicated, substituted, or unverified required binding. For reuse_verified_provider_batch, record its manifest digest and source lineage in current-run provenance; historical receipts remain evidence only and never grant settlement, replay, or spending authority. Bind each newly generated asset only to its matching Desktop-owned immutable local outputArtifact identity, settled receipt, exact frozen outputRelativePath/materializeTo, and composition loader path; retain artifact ID, SHA-256, verified byte size/resolution/duration and current fence provenance. Except for the existing verified preserved-provider no-spend branch, require eight of eight distinct approved requests, claims, settled receipts, verified immutable outputArtifact identities, and declared final asset bindings before successful artifact, Judge, Manager, or final completion. The exact approved request set must equal the claim, settled-receipt, verified-artifact, and declared final-asset-binding sets with one-to-one request/scene/destination/loader identity correspondence. Zero, subset, extra, mismatched, wrong-path, wrong-size, wrong-duration, stale-fence, or unresolved claims fail closed without resubmitting a completed provider job. Desktop verification must prove each artifact's SHA-256, byte size, 1920x1080 resolution, and complete approximately 5.04-second duration against its fixed five-second Kling request and authorized scene range. Preserve no-spend reuse only after existing exact-eight preserved-provider validation and current-run rebinding; never fabricate current-run claims, approval, or new settlement for historical receipts.

  Your model fills this step
• Step 13

  Verify read-only that the frozen step-9 composition implements every following build requirement; all creative work described here must have been fully authored in step 9 before verify_paid_project_checkpoint and paid approval. Do not build, edit, or repair source now. Require the complete deterministic Remotion scene system from the persisted scene_execution_contract, not a generic scaffold. Use useCurrentFrame with fps-derived timing and no CSS/Tailwind animations; implement required semantic treatments with safe text layout. Preserve all contract timing, narration anchors, evidence identities, uncertainty, fallbacks, and continuous presenter audio; begin reveals after anchors, sustain purposeful motion, keep captions/internal labels off, and fail rather than collapse to repeated templates. When optional revision_source_video is supplied and valid, edit the bundle's existing Remotion composition from that authoritative visual starting point rather than merely transcoding it; preserve existing composition, presenter audio, evidence, and verified Kling assets except where the exact bound feedback changes them. In revision mode, modify the capsule composition directly and only within the authorized_revision_set. Preserve all unaffected components, layouts, styles, animation families, timing, evidence, and asset bindings byte-for-byte where possible and semantically/perceptually otherwise. A generic scaffold, template substitution, or recreation from presenter plus cards is a typed failure, never a revision. Mount each Kling/provider video inside its own local Remotion Sequence at the authorized Master entrance. Media playback must use that Sequence's local time, start at source frame 0 (or the explicitly authorized local source offset), and play the complete intended 5.04-second source interval exactly once. Never pass inherited global Master time into source playback. Premounting must not advance the clip's visible playback clock. Never substitute endpoint clamping, a held final frame, looping, a screenshot, presenter movement, or synthetic scale/transform motion for moving provider B-roll.

  Best practices for Remotion - Video creation in React

  ↳ same skill as step 4 (Remotion Best Practices)

  Full skill: Remotion Best Practices
• Step 14

  Verify read-only the fully composed step-9 checkpoint timeline against actual Desktop-owned provider outputs and emit deterministic insertion/provenance QA evidence. All composition work described here must already have been completed before checkpoint and paid approval; no creative edits or loader-path changes are allowed now. Require current-run presenter footage, continuous source audio, supplied/generated clips, sourced evidence, and native graphics into the full deterministic Remotion Master timeline with exact frame math, premounted sequences, and duration-safe transitions. For final-production eligibility, insert every one of the eight verified Higgsfield outputs only in its hash-bound authorized scene/frame range and persist frame-level insertion evidence proving all eight appear in the frozen Master timeline. Preserve locked timing/current-run lineage and never import content or paths from manager-quality-bar. If any required generated asset is missing, duplicated, substituted, unverified, or absent from its authorized range, fail closed or produce only the supported partial/preview/approval outcome. For reuse_verified_provider_batch, require and persist proof of all 8/8 re-bound assets inserted only in their authorized scene/frame ranges. When optional revision_source_video is supplied and valid, preserve its verified visual lineage while composing exact requested changes in the editable Remotion Master; presenter_video remains continuous source-audio authority and verified Kling assets remain unchanged unless exact bound feedback changes them. For all eight clips, enforce the local Sequence/source-time contract from steps 5 and 13, preserving exact authorized entrances and complete once-only 5.04-second playback. Persist explicit source-local-to-Master frame/PTS mappings. Element presence and insertion-range bookkeeping alone do not establish moving B-roll; final-production eligibility additionally requires the independent temporal-correspondence proof in steps 15 and 18, including for reused provider assets.

  Best practices for Remotion - Video creation in React

  ↳ same skill as step 4 (Remotion Best Practices)

  Full skill: Remotion Best Practices
• Step 15tool

  Before any full-master render, render exactly five representative preview clips, a stitched preview reel no longer than 60 seconds, and a five-panel contact sheet from the exact frozen Master composition. Select opening hook, densest quantitative scene, map/evidence scene, one authorized Higgsfield scene or highest-risk permitted fallback, and late/closing scene; span at least three used treatment families. Persist composition digest, frame ranges, scene IDs, treatments/motion signatures, source/preview digests, and declaration that full render cannot regenerate styles/layouts/timing/assets. Reject narration mismatch, overflow, early reveals, static holds, presenter obstruction, captions/labels, missing B-roll, repetition, insufficient family coverage, flicker, partial glyphs/text, duplicate quadrants, unstable geometry, sparse motion, unjustified static holds, style deviation, or missing/incorrect Higgsfield insertions. Final-production preview approval requires 8/8 verified generated-asset bindings and authorized-range insertion evidence; otherwise only a clearly labeled partial/preview may proceed. When optional revision_source_video is supplied and valid, the existing five-preview approval set must demonstrate the exact bound revision changes against the preserved composition/asset lineage, without regenerating unrelated treatments. For revision mode, render baseline and revised samples at identical frozen frame ranges from the bound Master/capsule lineage. Persist machine-readable baseline-versus-revised visual/audio comparisons, prove every intended change appears, and reject any unexpected changed range, composition-identity change, generic-template substitution, or forbidden internal text before owner approval is eligible. In addition to preserving exactly five representative previews, the <=60-second representative reel, and five-panel contact sheet, render separate temporal QA evidence windows from the same frozen Master for all eight provider clips. Each window must show the authorized entrance and cover the complete intended 5.04-second playback through its last intended source frame; shorter previews cannot prove playback. These QA windows are additional evidence, not extra representative preview selections or a full-master render. Before requesting preview approval, independently decode/sample each immutable provider source and its actual rendered window at matched local timestamps across the entire interval, including first frame, multiple distributed interior samples, and final intended frame, with dense enough sampling to detect holds, skips, reversals, resets, loops, or missing duration. Compare a provider-dominant region while excluding presenter and text overlays; record masks/crops and any deterministic geometric normalization so presenter motion or synthetic scale/transform cannot count as source motion. Require measured non-trivial motion within the source itself and monotonic rendered-to-source temporal correspondence consistent with the frozen local source offset and fps/PTS mapping, with no unexplained jumps, repeated/clamped endpoint, or replay. Use both matched-time similarity and temporally discriminative source-frame matching; fail closed on static/ambiguous/occluded evidence or insufficient provider-visible area. Freeze explicit numeric motion, similarity, temporal-error, and coverage thresholds before evaluating results; record method/version and do not relax thresholds to pass a failed clip. Persist qa/provider-temporal-correspondence-preview.json as a declared qa_report artifact with run/composition/source/render digests, eight scene/request/clip identities, authorized Master entrances, local offsets and intervals, fps/timebases, full-duration coverage, sampled source-local and rendered/Master timestamps and frame indices, source/render frame SHA-256 hashes, mask/crop/normalization definitions, all metrics and thresholds, inferred temporal matches, and per-clip pass/fail reasons plus aggregate 8/8 status. Declare the underlying rendered evidence windows and reproducible verification scripts as QA/source artifacts. Fail closed before any preview approval request if any clip lacks motion, correspondence, or full-duration evidence; retain existing typed provider-failure/decline fallback branches without presenting absent provider motion as proved. Code inspection, contact sheets alone, self-authored labels/notes such as 'moving video', and an OffthreadVideo element's existence are never sufficient proof.

  Best practices for Remotion - Video creation in React

  ↳ same skill as step 4 (Remotion Best Practices)

  Full skill: Remotion Best Practices
• Step 16decision

  Stop at a human quality approval gate after five-shot preview artifacts are verified. Present timestamps, frozen composition digest, selected scene IDs/frame ranges, animation families, provider assets, 8/8 generated-binding/insertion evidence when claiming final production, and preview QA findings. Record a digest-bound preview_approval_receipt only on explicit owner approval; it locks exact composition, styles, layouts, timing, assets, and source identities. Full rendering is forbidden without this current-run receipt. If rejected after paid approval, preserve the run and immutable approved checkpoint and stop with the named failures. Keep that approved continuation immutable: stop instead of editing creative source or regenerating provider assets. Any authorized source correction requires a separate preapproval preparation and checkpoint cycle. A partial/preview fallback cannot be represented as final-production approval. Do not enter or request this preview approval gate until the independently sampled temporal QA artifact and complete evidence windows from step 15 pass for every one of the eight required provider clips. Present the declared temporal report and its 8/8 motion, full-duration, and monotonic-correspondence results; bind its digest and source/render/composition identities into the preview_approval_receipt. A failed, missing, short, ambiguous, or stale temporal report blocks approval and must stop for bounded repair in a separately authorized preparation/checkpoint cycle; it cannot be waived by labels, code inspection, still contact sheets, OffthreadVideo presence, presenter motion, or transforms. Preserve the existing explicit decline/typed-failure partial-preview branch without granting final-production approval or falsely asserting provider proof.

  Decision step
• Step 17tool

  Render the complete Master only after current-run preview approval, at bound resolution/fps/aspect/frame count/source duration, with executor attached and heartbeating until every renderer and artifact settlement is terminal. For final-production settlement, require 8/8 verified Kling asset bindings and evidence each is visibly present in its authorized scene/frame range; otherwise fail closed or return the supported immutable partial/approval result. Use one continuous adapter-derived audio track and exact frame-derived durations; never unsafe AAC stream-copy assembly. Refuse output unless ffprobe proves exact fps/frame count and monotonic one-frame PTS cadence; full-decode audio/video, extract chapter/join proofs and a whole-timeline contact sheet, and never declare samples, partial/background files, or missing paths as master. When optional revision_source_video is supplied and valid, full render remains an edit of the bundle's Remotion Master, never a transcode of the revision artifact; preserve verified composition/audio/evidence/Kling lineage except exact bound feedback changes. Preserve the approved per-clip local Sequence clocks, authorized source offsets/entrances, and complete once-only 5.04-second intervals in the final Master. Bind rendering to the preview temporal report and frozen inputs; after render, require independently sampled final-Master correspondence evidence under step 18 rather than inheriting a preview pass as proof of final playback.

  Your model fills this step
• Step 18decision

  Run independent whole-video QA as domain expert, hard skeptic, and end user. Verify every scene_execution_contract row, source timestamps/boundaries, continuous presenter audio, evidence/uncertainty, asset identities/fallbacks, narration synchronization, semantic treatments, visual-family variety, labels/data, motion, hierarchy/overflow, presenter cadence, absent captions/internal labels, branding, black/silence, decode, frame count, and PTS joins against compiled quality-bar digests and Manager proof requirements. Require 8/8 verified generated-asset bindings plus evidence every asset appears in its authorized scene/frame range for final-production and successful Manager/Judge proof. Reject flicker, partial glyphs/text, duplicate quadrants, unstable geometry, sparse motion coverage, long unjustified static holds, style deviation, and missing/incorrect Higgsfield insertion. Preserve purposeful narration-relevant supporting motion after its spoken anchor without presenter obstruction. After paid approval, permit only deterministic rerender/QA of unchanged checkpoint source; any failure requiring creative or dependency changes must stop for a separately authorized preparation/checkpoint cycle; block final delivery when quality, custody, technical validity, or required-generation proof fails. When optional revision_source_video is supplied and valid, independently verify its Desktop-bound identity/digest, stable no-writer state, media validation, exact requested changes, and preservation of all unaffected composition, source-audio, evidence, and verified Kling lineage. For revision mode, independently verify revision_baseline_preserved, authorized_ranges_only, forbidden_internal_text_absent, and provider_motion_used where applicable. Compare representative and changed-range motion samples—not contact-sheet stills alone—and fail closed when the revised output cannot prove capsule lineage or preservation outside the authorized set. Require provider_temporal_correspondence as an explicit mandatory Manager and independent Judge acceptance criterion for all eight clips. Independently repeat step 15's matched-local-timestamp source/render sampling against the actual completed Master, covering every clip's entrance and full intended 5.04-second interval; exclude presenter/text overlays and synthetic transform motion, use the frozen metrics/thresholds and source-local/Master mapping, and require non-trivial source motion plus monotonic temporal correspondence and complete once-only playback. Persist qa/provider-temporal-correspondence-final.json with the same complete per-clip timestamps, metrics, thresholds, source/render frame hashes, coverage, temporal matches, masks and pass/fail schema, bound to the actual Master digest; declare it as qa_report with underlying evidence and reproducible scripts. Manager/Judge must independently inspect the declared media and report and reject missing, unverifiable, stale, ambiguous, short, static, clamped, looped, or temporally mismatched evidence. Worker claims, code inspection, contact sheets alone, labels/notes, OffthreadVideo existence, presenter movement, screenshots, held endpoints, or synthetic scale/transform are not proof of moving B-roll. Fail closed before delivery and final Review settlement on any missing or failed required clip; repairs remain bounded by the authorized revision set and existing approval/paid-action safeguards, never authorize regeneration or spending. Except for the existing verified preserved-provider no-spend branch, require eight of eight distinct approved requests, claims, settled receipts, verified immutable outputArtifact identities, and declared final asset bindings before successful artifact, Judge, Manager, or final completion. The exact approved request set must equal the claim, settled-receipt, verified-artifact, and declared final-asset-binding sets with one-to-one request/scene/destination/loader identity correspondence. Zero, subset, extra, mismatched, wrong-path, wrong-size, wrong-duration, stale-fence, or unresolved claims fail closed without resubmitting a completed provider job. Desktop verification must prove each artifact's SHA-256, byte size, 1920x1080 resolution, and complete approximately 5.04-second duration against its fixed five-second Kling request and authorized scene range. Preserve no-spend reuse only after existing exact-eight preserved-provider validation and current-run rebinding; never fabricate current-run claims, approval, or new settlement for historical receipts. The paid checkpoint immutability rule also governs every bounded-repair reference in this stage: never edit creative source, install dependencies, acquire network evidence, relax thresholds, or regenerate provider assets in the approved continuation.

  Decision step
• Step 19decision

  Deliver one portable handoff containing the verified video_master plus a newly built immutable editable-revision capsule for that exact master. The capsule includes package files, complete Remotion source/timeline, render/QA scripts, scene/asset/provenance manifests, required evidence, all eight authorized generated clips with durable receipts and render proxies, preview/QA evidence, and presenter adapter binding with source/derived-media digests; never copy the large original presenter source. Validate archive inventory, SHA-256, scene count, generated-asset count, 8/8 verified binding/insertion evidence, and archive integrity. Record master as final_output and capsule as source only after required video QA passes. If approval is declined or provider/auth/generation fails, deliver only a clearly labeled immutable partial/preview with typed disposition; never label native-only or incomplete generation as final-production success. When optional revision_source_video is supplied and valid, include its Desktop-bound digest, validation result, and an exact change ledger in the immutable delivery capsule; preserve existing delivery, settlement, Manager, and Judge proof requirements. Include the declared preview and final provider-temporal-correspondence QA reports, complete per-clip rendered evidence windows, sampled-frame evidence, and reproducible verification scripts in the immutable editable capsule/inventory. Bind reports to exact source, preview, composition, and final Master hashes and require 8/8 full-duration motion/correspondence passes for final-production settlement. Preserve all existing custody/revision-capsule and preserved-provider reuse rules, approval gates, paid-action safeguards, Manager handling, independent Judge, and final Review settlement; this added QA requirement changes no input contract or lifecycle stage count. Except for the existing verified preserved-provider no-spend branch, require eight of eight distinct approved requests, claims, settled receipts, verified immutable outputArtifact identities, and declared final asset bindings before successful artifact, Judge, Manager, or final completion. The exact approved request set must equal the claim, settled-receipt, verified-artifact, and declared final-asset-binding sets with one-to-one request/scene/destination/loader identity correspondence. Zero, subset, extra, mismatched, wrong-path, wrong-size, wrong-duration, stale-fence, or unresolved claims fail closed without resubmitting a completed provider job. Desktop verification must prove each artifact's SHA-256, byte size, 1920x1080 resolution, and complete approximately 5.04-second duration against its fixed five-second Kling request and authorized scene range. Preserve no-spend reuse only after existing exact-eight preserved-provider validation and current-run rebinding; never fabricate current-run claims, approval, or new settlement for historical receipts.

  Decision step

common questions

1. v36Sep 15manual

   Require the compiler-v3 canonical portable project-bundle contract shared with Planner v20, including exact immutable file inventory and the 5.04-second Higgsfield Kling 3.0 timing rule.

2. v35Sep 15manual

   Update Desktop-owned readiness and dependency preparation in steps 1 and 9; normalize immutable-phase prohibitions in steps 9 and 16 without changing semantics.

3. v34Sep 14manual

   Clarify broker-only Higgsfield readiness, pre-approval preparation, approved execution, and immutable capability proof in steps 1, 10, and 11; preserve all other workflow contracts.

4. v33Sep 13manual

   Enable fresh builds with conditional revision coverage; fully prepare and freeze composition before paid approval, echo checkpoint identity, and enforce immutable provider/render/QA continuation.

5. v32Sep 13manual

   Add Manager quality coverage only at revision, planning, scene-contract, and asset-selection seams; preserve v31’s 19-stage contract and existing build, preview, and QA policies.

6. v31Sep 13manual

   Move dependency proof before spend, bind Desktop-owned paid outputs to exact compositor destinations, and close Manager coverage in build, preview, and QA.

7. v30Sep 12manual

   Replace paid actions with the v3 manifest and MCP execution path; enforce Manager coverage in build, preview, and QA.

8. v29Sep 12manual

   Corrected obsolete ElevenLabs setup metadata while preserving the exact 19-stage compositor, Manager/Judge authority, typed inputs, and current permission policy.

9. v28Sep 12manual

   Removed obsolete ElevenLabs voiceover setup requirement; preserved the existing 19-stage compositor workflow, typed inputs, Judge, and delivery outcome.

10. v27Sep 11manual

    Require local once-only provider playback and full-duration temporal QA for all eight clips before approval and final Manager/Judge acceptance; preserve v26 contracts and 19 stages.

11. v26Sep 11manual

    Require a paired editable revision capsule and prove exact Master lineage, authorized-only changes, and unaffected-range preservation.

12. v25Sep 11manual

    Add optional Desktop-bound revision-source video input and preservation path while retaining all v24 contracts.

13. v24Sep 10manual

    Change only steps 1 and 12: strict provider-free CA probing, persisted verified child environment, and exactly one npm ci reusing that environment; preserve all v23 production and recovery contracts.

14. v23Sep 10manual

    Add an optional Desktop-verified preserved provider batch with a strict fail-closed no-respend branch while retaining the existing 19-step ordinary production flow.

15. v22Sep 10manual

    Require eight approval-gated Kling assets for final production and 8/8 binding proof.

16. v21Sep 9manual

    v21: Use Desktop materialize-presenter once for full-duration ingest; reserve render --plan for approved editorial work. Preserve all 19 steps, bindings, inputs, and v20 safeguards.

17. v20Sep 9manual

    Synthesize semantic scene contracts from valid planner scaffolds; retain v19 safeguards.

18. v19Sep 9manual

    Make quality references optional; compile a digest-bound quality bar from Manager decisions, exact-attempt approved learnings, and planner contracts. Preserve all 19 v18 steps and safeguards.

19. v18Sep 9manual

    Harden dependency installation with immutable-lock validation, one foreground system-CA npm ci, terminal polling, fail-closed verification, sequential checks, and monotonic stage heartbeats.

20. v17Sep 9manual

    Serialize npm CI with explicit system CA trust and fail-closed dependency verification.

21. v16Aug 28manual

    Hardened revision-source inheritance, exact-composition previews, attached long renders, timestamp-safe segmented assembly, semantic/PTS QA, and immutable editable delivery capsules.

22. v15Aug 26manual

    Add a digest-bound five-shot representative preview and explicit owner approval gate before any full-master render.

23. v14Aug 26generated

    restored range-safe presenter authority after proposed revision

24. v13Aug 26feedback

    Force-bind Remotion best practices and Higgsfield generation after automatic binding stripped the explicit integrations.

25. v12Aug 26manual

    Manager L1 manual proof: compile approved learnings and accepted quality evidence, bind Remotion and Higgsfield skills, gate previews, and verify scene-level quality.

26. v11Aug 26generated

    preserved range-safe presenter access across typed-input revision

27. v10Aug 26manual

    Require the original presenter video as a verified typed input for metadata-only planner bundles.

28. v9Aug 24generated

    added range-safe presenter-video access for project-bundle composition

29. v8Aug 20manual

    reconciled active outcome capability input authority

30. v7Aug 17manual

    Add the canonical V1 outcome capability and cryptographically verified video_master delivery.

31. v6Aug 16manual

    Add typed bundle ingestion, missing-generated-asset handling, and verified portable compositor outputs.

32. v5Aug 11manual

    Allow the required project bundle to be selected as a local folder or ZIP.

33. v4Aug 7manual

    Added optional Higgsfield CLI editorial still generation (gpt_image_2): runtime auth detect, no baked-in text, illustrative-only never evidence, full metadata in manifest+receipts. No video.

34. v3Aug 6manual

    Single required project_bundle (folder/ZIP) with conventional-filename discovery; the five files become optional overrides; preflight moved before any ffprobe probing; accepted extensions configured.

35. v2Aug 6manual

    Removed broll_generation + all Runway/Seedance/HeyGen requirements/fallbacks; agent never generates video, consumes Runway MP4s only as manifest inputs; kept browser/computer-use + local Remotion.

36. v1Aug 6generated

    auto-generated from "Turn an approved cinematic production plan, transcript timing, presenter footage"

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

related agents

• creator

  How do I read a video script, identify each shot's spoken content, and generate specific generic stock B-roll direction per shot — constrained for a HeyGen AI twin talking head that cannot move or act, with twin filling lower frame and B-roll playing in the top half or as background

  B-Roll Director for AI Twin Videos

• dailybuilder

  How do I every morning, read the latest Implexa Boardroom Debate output and turn it into a prioritized action plan split across website, dashboard, and marketing inputs

  Boardroom Debate → Daily Action Plan

• on demandvideo-production

  How do I generate a finished concept-animation MP4 for a raw video using the user's provided reference video and brand style. Use full-screen or half-screen explanatory animations when they clarify concepts, reserve simple text-only treatments for basic emphasis, and avoid persistent presenter/name overlays; mention only "Sanna" when the presenter explicitly introduces herself or the script requires it

  Brand-Style Concept Animation Video Producer

• weeklybuilder

  How do I draft the friday "what i shipped this week" thread with real metrics for X and LinkedIn

  build-in-public weekly thread