Operating sequence

Review Wan 3.0 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

    <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 a circulating model phrase into a source-verified multi-reference-asset and continuous-creation planning package. Circulation does not establish the current model identity, access, supported inputs, generation limits, output quality, rights, pricing, or commercial performance. 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>model-and-access verification record:</strong> save the source, date, owner, and decision it supports.</li><li><strong>reference-asset and shot brief:</strong> save the source, date, owner, and decision it supports.</li><li><strong>variant comparison sheet:</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 production package that remains executable if the circulating label or access path cannot be confirmed. 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 model label and account context are recorded; record pass, fail, not tested, or not applicable.</li><li>each reference asset has provenance and permitted use; record pass, fail, not tested, or not applicable.</li><li>observed outputs are compared from original files; record pass, fail, not tested, or not applicable.</li><li>unknown access, quality, rights, and price remain explicitly unknown; record pass, fail, not tested, or not applicable.</li></ul><p>Investigate likely failure modes before approval:</p><ul><li>a product mention is treated as proof of repeatable behavior; stop and revise rather than converting the gap into a capability claim.</li><li>reference-asset count or duration is inferred from repost language; stop and revise rather than converting the gap into a capability claim.</li><li>visual polish hides missing rights or verification; 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>