I2V pre-generation conflict layer¶
The sanity layer that checks the inputs of a multi-shot Seedance 2.0 / 2.5 generation before we pay for the video. Shipped code lives in ../../src/workbench/sequenceValidation/.
Read this¶
| File | What it is |
|---|---|
| SEQUENCE_CONFLICT_TAXONOMY.md | THE TAXONOMY — 23 codes in 6 groups. What to warn about, what to stay quiet about, what is our bug instead of the user's, and how a conflict turns into a one-click fix. §9 maps the old C1…X1 draft onto it. Cited from sequenceIssueCatalog.ts, which must stay in step with it. |
| i2v_handover_yash_human_readable.md | What the feature is and how it behaves, for a person. Written for Yashasewi Singh, who owns the frontend. |
| i2v_agent_handover_yash.md | The same feature for a coding agent picking up the work: endpoints, payloads, the fields the panel reads. |
Evidence¶
Primary sources. Everything in the taxonomy traces back to one of these.
| File | What it measures |
|---|---|
| evidence/I2V_20_SEQUENCE_DISSECTION.md | Pass 1. Field-by-field dump of the 20 most recent multi-shot sequences, frozen 2026-09-16, across five stories. |
| evidence/I2V_20_MORE_SEQUENCES.md | Pass 2. A different 20, frozen 2026-09-17, zero overlap. 10 findings — including what the request actually sends as a reference, which pass 1 never looked at. |
| evidence/I2V_SEQUENCE_CONFLICTS_IN_REAL_DATA.md | Earlier, wider pass: rates across 193 selections. Useful for frequency; its severity calls are superseded. |
| evidence/I2V_ANALYSIS_A_VARIANTS.md | How character and environment variants flow into a generation. |
Not in the repo¶
The planning material is kept locally, in i2v_conflicts/ (gitignored), and is not needed to read or
change the feature: the brief, Miki's raw notes, the architecture proposal and Codex's review of it, plus
five superseded drafts of the taxonomy under archive/. All of the taxonomy drafts are replaced by
SEQUENCE_CONFLICT_TAXONOMY.md.
Related, different feature¶
The four conflict codes on the "Review inputs before generating a sketch" screen are a different feature, but they are the shipped precedent for the shape a user-facing conflict takes: a code, a one-line message, a severity, and a fix the user can actually perform. See ../../src/workbench/preGenValidation/issueCatalog.ts — 26 codes, all single-shot.
toShotBreakdown() in
../../src/workbench/sequenceFlow/sequenceFlow.utils.ts
is the definitive list of what actually reaches Seedance per shot.