Operating sequence

Review Wan 3.0 on Flova as a prompt blueprint task with query-specific artifacts, checks, evidence boundaries, and a safe fallback plan.

  1. 01

    Prompt blueprint question for Wan 3.0 on Flova

    <p>The reader task is to encode the creative brief as modular prompt instructions and negative constraints. For this phrase, the concrete focus is to turn the phrase into an evidence-safe, independently testable research and production-planning package. Circulation is not product capability evidence; verify current identity, access, specifications, rights, and output behavior with primary sources and direct tests. Start by writing the requested deliverable, intended audience, delivery format, source date, and decision owner. Keep circulation signals out of the capability column: discussion can explain why a phrase deserves investigation, but only primary documentation and direct inspection can support product or output facts.</p><p>Keep one instruction responsible for one visible or audible decision; version changes and record which module each revision addresses. The required result is a prompt packet with scene, action, camera, timing, audio, continuity, disclosure, and exclusion modules. This differs materially from the other Hub routes because it owns a distinct artifact and decision: the prompt blueprint record. A guide owns sequence, a prompt page owns instruction design, a model page owns identity and provenance, and this route must not collapse into those neighboring jobs.</p>

  2. 02

    Build the a prompt packet with scene, action, camera, timing, audio, continuity, disclosure, and exclusion modules

    <p>Use these query-specific artifacts rather than generic inspiration. Preserve originals whenever possible and document transforms between capture, generation, editing, and delivery. Unknown access, price, model identity, or specifications should remain unknown until a current first-party source or direct account test resolves them.</p><ul><li><strong>source and account-context record:</strong> save the source, date, owner, and decision it supports.</li><li><strong>original input/output comparison set:</strong> save the source, date, owner, and decision it supports.</li><li><strong>measurement and decision ledger:</strong> save the source, date, owner, and decision it supports.</li><li><strong>rights and delivery checklist:</strong> save the source, date, owner, and decision it supports.</li></ul><p>Apply this method: Keep one instruction responsible for one visible or audible decision; version changes and record which module each revision addresses. Save exact input versions and separate factual checks from creative preference. The safe end state is a model-agnostic evidence-safe planning package with a conventional fallback path. That outcome stays useful even when a product name changes, an interface is unavailable, or a social example cannot be reproduced.</p>

  3. 03

    Acceptance checks and failure review

    <p>The packet passes when prompt edits map to diagnosed failures and no wording promises a capability that has not been verified. Run the following checks against original artifacts, not a repost or marketing summary.</p><ul><li>the exact label and source context are recorded; record pass, fail, not tested, or not applicable.</li><li>original artifacts are compared under fixed test conditions; record pass, fail, not tested, or not applicable.</li><li>unknown capability and access remain explicitly unknown; record pass, fail, not tested, or not applicable.</li><li>a fallback path remains executable; record pass, fail, not tested, or not applicable.</li></ul><p>Investigate likely failure modes before approval:</p><ul><li>a promotional caption is generalized into a guarantee; stop and revise rather than converting the gap into a capability claim.</li><li>one polished result replaces reproducible testing; stop and revise rather than converting the gap into a capability claim.</li><li>unverified access, quality, rights, or price is inferred; stop and revise rather than converting the gap into a capability claim.</li></ul><p>Record who checked each item, when it was checked, the source or file inspected, and the next action. Do not infer availability, quality, commercial performance, rights clearance, or repeatability from popularity. The final recommendation should name the evidence that would change it and retain a fallback production path.</p>