Veo 3.1参考图角色契约

Applicable scenario

Use before a Veo 3.1 Ingredients to Video request that uses reference images for a character, object, scene, or style. Python 3.9+ is required; no external package, account, model key, network call, or upload is required.

Inputs and outputs

Input is a redacted JSON object with model, prompt, aspect_ratio, and references. Each reference has a unique id, role, asset kind, size in bytes, and locked fields. Output is veo31_reference_contract.json plus a Markdown review report.

Installation and execution

1. 1. Copy the skill directory or run it in place.
2. Replace the example references with licensed, redacted metadata only.
3. Run python scripts/build_reference_contract.py <request.json> --out-dir <output-dir>.
4. Give a ready_for_generation contract to the model operator only after a person confirms the role map and rights.

Rules

The contract requires Veo 3.1, a non-empty prompt, one to three image references, supported roles (character, object, scene, or style), unique ids, positive byte counts no larger than 20,000,000, and non-empty locked fields. A reference may guide content but does not force the provider to preserve every pixel.

Recovery

Fix every blocker and rerun. Do not silently drop a reference, merge two roles, or change a locked field to make the request pass. Provider moderation, quota, permissions, and unsupported input errors stay with the provider\'s normal controls.

Permission and privacy

Keep private faces, brand assets, customer data, API keys, cookies, and source paths out of the JSON. The script only reads metadata and never contacts a provider.

Acceptance

The normal example exits zero and emits three ordered reference roles; the invalid example exits nonzero for four references, an unsupported role, and an oversized asset. A human must confirm the references are authorized before generation.