The same 6-beat 端午 dragon-boat reel as the manual playbook — but authored as a condition-graph: one Bo node, wired into every shot. Draw a line, the line carries the character. This is the VibePaper-moat workflow, reproduced — and it caught a real identity-drift bug that only showed up when we rendered it.
In the manual version, Bo's sheet is fed into each beat by hand. Here it's declared once on the graph: a single character wire from the Bo node into all six beats, then each keyframe wired as the first_frame of its video. Re-run one beat and only its wires re-pull — the rest stay frozen. Add a second character? One more node, one more line.






The first wired render came out broken in an instructive way — and unit tests + a "URL returned" smoke test both passed while it happened. Only looking at the frames revealed it.
character wire composed a generic "keep the same character" prompt and the edit model ignored the reference.character/subject through the same buildSubjectTransferPrompt wrapper place_subject uses.This reel and the manual one are the same output — the difference is authoring. Manual is the better one-off; Wire Graph is the better system (series, multi-character, heavy iteration, cross-surface). Full measured breakdown: