Seedance 2.5 空间镜头契约

Use this skill before generating a multi-shot sequence. It turns a redacted shot list into a deterministic state ledger so the next shot has an explicit predecessor instead of relying on memory in a long prompt.

Prerequisites

• - Python 3.9 or newer.
• A UTF-8 JSON file with an ordered shots list and a rights_review object.
• The buyer\'s own references, storyboard, and continuity decisions. This skill validates metadata and does not inspect media.

Inputs and outputs

Run python scripts/check_shot_plan.py examples/pass_plan.json --out ledger.json --report ledger.md.

Each shot declares a unique shot_id, an integer sequence, location_id, screen_direction, camera, subjects, props, end_state, and predecessor. The checker verifies that sequence numbers are contiguous, every later shot names the prior shot, each subject has a position and action, and the rights review is confirmed. It emits a JSON ledger and Markdown report.

Execution and acceptance

1. 1. Replace only the redacted IDs and factual state fields in the example.
2. Run the checker. Exit code 0 means the ledger is structurally ready for an authorized prompt or reference handoff; exit code 1 means fix the errors.
3. Before any paid generation, compare the ledger with the current model interface and confirm the buyer\'s chosen camera/reference controls manually.

This is not a visual continuity guarantee. It does not prove geography, anatomy, action, reference-file existence, or model compliance.

Privacy and recovery

Keep private images, names, addresses, tokens, and media bytes out of examples. Obtain permission for people, places, brands, and props. If a shot has no predecessor, conflicting screen direction, or an unreviewed rights state, stop rather than submitting a paid request.

Standalone use

The shot contract is independently useful for storyboarding, prompting, or handoff to another authorized operator. The companion auditor can consume its shot IDs but is not required.