[Preset] Configure a reusable anime music video workflow #78

Outcome

Provide a reusable, versioned anime music video (AMV) preset in Flow. The operator declares source video/audio, selects processing steps and destination outputs, and reviews an inspectable plan before execution. Reuse the preset across projects such as Akashic, Dingus and Exist with project-specific overrides.

Ownership and dependencies

• Extend the released Aniflow adapter/profile in [FLO-3.4] Integrate an immutable Aniflow release #51 and [Adapter] Orchestrate the released Aniflow music-video profile #75; depend on [Release] Publish the qualified Aniflow music-video profile for downstream consumers aniflow#40 for the qualified music-video capabilities.
• Aniflow owns media processing, timing, validation and its stage evidence; Flow owns cross-tool planning, authority, approvals and recovery.
• Coordinate with [Music video] Package the selective repair, upscale, and verified delivery workflow aniflow#35–[FLO-3.2c] Verify locked packages and executable subjects #38 (composition, selective repair, recovery and tools), [AI] Define optional runtime profiles, local model preparation and existing provider routing #80 (native audio inspection), docs: audit flow and reconcile the complete roadmap #83 (destination exports), and Reconcile flow's current implementation and continuation documentation #82 (provenance/timestamps).
• Optional creator watermarking is [Release preparation] Qualify optional creator watermarks for stereo audio and video aniflow#81; experimental cleanup [FLO-3.2c] Verify locked packages and executable subjects #39 is separately selected and never a prerequisite.
• Reuse existing Flow configuration, persistent execution and checkpoint contracts. No second workflow engine or sibling source dependency.

Acceptance

• Declare immutable input references for the edited video and approved audio master, source selection, project overrides, output location, supported destination profiles and exact provider versions.
• Allow explicit selection/skipping of inspect, selected-range repair, upscale, assemble, validate, export and supported provenance/timestamp steps. Bind model/settings, frame ranges, intended geometry and audio policy in the resolved plan.
• Preview effective steps, inputs/outputs, dependencies, expected effects, resource/tool requirements, unsupported combinations and review points before execution.
• Keep originals and clean archival masters; create distinct identities for transformed, watermarked and platform copies. Preserve exact timing, stereo channels, offsets and audio tails through Aniflow evidence.
• Default to local preparation with no implicit downloads, normalization, watermarking, signing, timestamp networking or upload. Each external effect requires explicit selection and existing Flow authority.
• Provide durable human review points for processed candidates and final posting packages. Structural validation never substitutes for creative approval.
• Resume compatible completed stages after interruption; explain invalidation when source/configuration/provider/approval identities change, and never reuse stale downstream results.
• Compute final-byte digests and timestamps after every selected byte-changing operation; preserve proof state and original/final evidence references.
• Public documentation includes a minimal preset and project override examples plus generated plan/status/evidence output through supported contracts.
• Author redistribution-safe synthetic end-to-end and refusal/recovery coverage. Record execution evidence separately; retain current Aniflow [FLO-13.4a] Revalidate dependency graphs before durable resume and execution #64 deferral.
• Actual platform publication stays a separate explicitly authorized action and retains the resulting URL/receipt only when observed.

Scope boundary

This captures a future reusable preset, not permission to process private songs/videos, approve creative output or publish. It does not block the first Flow release or duplicate #75's adapter implementation.