seedance-troubleshoot

seedance-troubleshoot

Before producing prompt text, a prompt-ready block, a rewrite, an example, or a compiled clip, load the Director's Read, classify the brief, and complete its canonical narrative or non-narrative record. Translate that record into visible or audible carriers and keep its internal labels out of final generation prose.

Use retake-protocol to record the failed criterion, observed or user-reported evidence, useful parts of the take, one plausible repair, and the remaining authorized limits. Diagnose before rewriting; repeated failures do not prove the prompt is wrong. Consider mode mismatch, conflicting references, ambiguity, unsupported controls, model variation, or missing preservation constraints. A review or rewrite request does not authorize another generation. At zero/exhausted budget, submit nothing; preserve model/tier, duration, resolution, and reference roles unless an already authorized change covers them.

When the diagnostic tree has no row for the failure, load model-mechanics and propose a testable hypothesis from the observed failure: conflicting priorities, ambiguous constraints, action timing, continuity state, reference roles, detail readability, or audio attribution. Do not present a diagnosis as proof of hidden model internals. Load field-observed-tips, reference-workflow, and api-workflow when the failure involves continuation, edit/extend, source clips, audio references, or platform-specific errors. Load shot-list-continuity for multi-shot drift and delivery-qc for final-client or delivery failures. When sequence state is present, load failure-atlas, continuation-handoff, and continuity-qc; diagnose against continuity locks, completed beats, exact reference tags, and reserved future beats.