video-autopilot

# Hao Video Autopilot Turn a content brief and creator-owned source material into reviewable video artifacts and publishing packages. The workflow supports long-form video, YouTube Shorts, Instagram Reels, illustrated music videos, and reusable image or motion assets. It does not ship a maintainer profile: voice, face policy, captions, palette, outro, channel links, performance baselines, and aesthetic choices come from the active creator configuration or an explicit brief. ## Modes - **Plan** — clarify the audience promise, evidence, format, platform, constraints, and packaging hypotheses; produce a script and edit plan. - **Build** — inspect authoritative source material, bind every decision to evidence, apply an audited edit plan atomically, render, and run delivery QA. - **Log Outcome** — record human review and comparable platform outcomes in the creator's protected local state; never treat missing values as zero. - **Optimize Patterns** — propose reversible changes from repeated comparable evidence. A single preference or result cannot become a universal default. ## Operating contract 1. Discover the project root from its manifest and keep generated work inside the existing project structure. Do not invent sibling project directories. 2. Classify the requested format and load only the references needed for that route. Treat project media, accounts, drafts, outcomes, and creator profiles as local data unless the creator explicitly authorizes a separate action. 3. Inspect source material before planning. Claims about products, places, prices, results, licenses, or identities require verifiable evidence. Bind every review score and correction to its exact video and version; never transfer a rating or complaint to another cut. For shot choice, use the nine evidence-gated styles in [Shot selection language](references/shot-selection-language.md). A style guides which observed shots deserve review; it never proves performance, source rights, or story fit and never edits a timeline by itself. 4. Before writing narration, load the active creator's own voice profile and at least two creator-written scripts in the same format and register. Write an audience promise, evidence map, and claim boundaries first. Generic `script_gate` checks audience language and retention, not voice authenticity. Compare the draft beat by beat with those samples; if footage or proof is missing, mark it `ASSET_REQUIRED` and plan capture. 5. Compile decisions into `hao.video-autopilot.edit-plan/v4`, audit the plan, apply it atomically through the workflow contract, and retain immutable receipts. Older plan versions may be imported for migration but not applied as the current workflow. 6. Programmatic motion uses the registered `hao.motion-composition/v1` or `hao.motion-composition/v2` contract; Editkin Motion also supports editable 2.5D floating video frames, portrait perspective orbit, and two rear portrait panels through the registered MCP presets. Use the read-only scene compiler and include its commands in the audited v4 plan as described in [Workflow execution](references/editkin-workflow-execution.md). Effects, tracking, masks, generated assets, and transitions require a semantic purpose and the evidence needed by their adapters. Missing evidence falls back to a clean cut or clean hold. For original chapter explainers and three-source spatial galleries, use the [native reel scene route](references/native-reel-scenes.md). Develop all UI geometry, animations and editable templates in our own systems; third-party UI components and demo templates are not permitted. Require the installed capability and keep this acceptance separate from illustrated music MV. For an illustrated music video, use the separate [illustrated music MV route](references/music-video-motion.md): original layered character and scene art, verified musical phrases, frame-aligned kinetic typography, editable silhouettes and foreground accents. Call `prepare_illustrated_music_video_draft` to create a read-only scene draft, then bind its commands and text events into the audited v4 plan. The live-action `prepare_music_video_draft` route is used only when the creator explicitly requests live-action montage. 7. Render only through the v4 workflow after prerequisites pass. Run technical QA, content-integrity checks, and the bound creator review policy. Human review remains the default; explicit creator authorization permits agent reference comparison tied to the exact project, output hash, full decode and timestamped motion observations. Agent review is never human approval. Retired Shorts direct builds and historical long-form pipelines cannot produce or register a new current film. Publication remains a separate gate. 8. Package platform variants from one verified content truth. Platform copy, aspect ratio, safe areas, and metadata may differ without changing factual claims. 9. After creating or changing a long-form thumbnail, pair it with the proposed title and actual opening. Inspect a 168x94 preview, record evidence for all ten dimensions, and run `thumbnail_algorithm_score.py` before calling it the selected or upload-ready cover. Below 85, a weak critical dimension, or a blocking/review signal means revise and rescore. This is an explainable pre-publish judgment, not an automated CTR prediction; validate the winner with real post-publish watch-time and retention evidence. The workflow lifecycle is represented by `hao.video-autopilot.workflow-contract/v1` receipts. Interrupted work resumes from verified state; an unknown apply state must be reconciled before retrying. ## Remote review When visual artifacts need review, create a manifest-bound review bundle for the authoritative media. Local review is preferred when available. Remote review may use a temporary secret HTTPS endpoint after verifying the page and media range response from the public URL. Keep the workstation online while review is active, share the URL only with the intended reviewer, and stop the endpoint when review is complete. A review URL is access, not approval. ## Release and update The public project is [https://github.com/Hao0321/video-autopilot-kit](https://github.com/Hao0321/video-autopilot-kit). Release archives must be manifest-driven, reproducible, checksummed, and limited to redistributable files. Exclude creator media, accounts, local profiles, outcomes, credentials, private paths, and assets without redistribution rights. Updates verify the release channel and manifest, preserve protected local paths, back up managed files before replacement, and roll back on failure. Incompatible upgrades require confirmation; unknown files are never deleted implicitly. ## Authorization boundaries - Planning, local rendering, validation, and creation of review artifacts are implementation steps within an authorized build. - Publishing, messaging, spending credits, installing external components, or exposing a remote endpoint requires the authority appropriate to that action. - Generated or illustrative media cannot be presented as documentary proof. - Human review remains explicit and cannot be inferred from a passing test. ## Public references - [Editorial intelligence contract](references/editorial-intelligence-contract.md) - [Workflow execution](references/editkin-workflow-execution.md) - [Native reel scene route](references/native-reel-scenes.md) - [Illustrated music MV route](references/music-video-motion.md) - [Plugin automation](references/editkin-plugin-automation.md) - [Mobile device binding](references/editkin-mobile-device-binding.md) - [Model and context adaptation](references/model-and-context-adaptation.md) - [Script and retention calibration](references/script-retention-2026.md) - [Thumbnail algorithm score](references/thumbnail-algorithm-score.md) - [Asset workshop](references/asset-workshop.md) - [Publish hub and remix](references/publish-hub-and-remix.md) - [Storage lifecycle](references/storage-lifecycle.md) - [Token budget system](references/token-budget-system.md) - [Open-source release and upgrade](references/open-source-release-and-upgrade.md)