Socialseal Asset Planning

SocialSeal Asset Planning

Overview

Asset planning converts a blueprint's shot panels into a concrete capture and clip-library plan. The goal is that every planned video shot panel has a rights-cleared clip ready for the editor. This is the bridge between socialseal-blueprint-builder and an editor handoff. Record panel coverage in the handoff document; SocialSeal's clip-to-shot mapping and generated-video tools have retired.

See references/production-pipeline.md. Work from the blueprint shot panels (vnext-blueprints-shots-read), not a generic shot list.

Read references/creative-production-gates.md for production-bound work. The asset gate must present meaningful choices and evidence, not silently assign approximate images because they are visually convenient.

When to Use

• Turning blueprint shot panels into a capture/clip plan.
• Auditing clip-library coverage against blueprint panels.
• Batching capture and preparing clips for upload.

Inputs

• the blueprintId and its shot panels (panelId, shot label, kind)
• current clip library (vnext-clips-read) and any user-provided panel coverage table
• platform specs and aspect ratio
• available footage, creator/talent/location constraints, deadline

Workflow

1. List the shot panels. From vnext-blueprints-shots-read, enumerate every panelId and what it needs (hook, hero, supporting, detail).
2. Audit coverage. Compare panels against the clip library and documented panel coverage. Mark each panel: covered, needs capture, needs sourcing, or needs generation. Inspect the actual media (or a contact sheet), not only filenames/descriptions. Record rights and subject/location confidence as verified, likely, or unknown.
3. Plan capture for gaps. For panels needing footage, write required shots first, then useful, then optional B-roll.
4. Batch capture. Group shots by location, setup, product, screen recording, creator, or time of day.
5. Add validators. Capture practical details that make utility content useful: signs, screens, maps, prices, steps, timing, packing, setup, texture, before/after.
6. Prepare clips for upload. Define file names and confirm usage rights for each clip. vnext-clips-create with action: "create" returns a signed upload target; upload bytes, then finalize with action: "finalize", clipId, fileName, storagePath, mimeType, sizeBytes, and rightsAttested: true.
7. Run the asset decision gate. For material gaps, present 2-3 viable choices: verified owned material, rights-cleared stock, new capture/reshoot, generated reference, or a concept change. Get approval before using substitutes.
8. Hand off. Package the approved plan, exported brief, source clips, trim suggestions, and delivery specs for the user's editor. Route gaps to socialseal-generation-prompts only for approved generated references. SocialSeal does not assemble the video or export FCPXML.

Output

• panel coverage table: panelId -> status (covered / capture / source / generate) -> clip or plan
• capture batch plan
• missing-asset list
• reviewed asset options with rights and location/factual confidence
• file naming convention and rights notes
• editor/handoff notes for shots that still need real footage

Do / Don't

Do:

• plan against blueprint panelIds, not an abstract list
• mark shots required / useful / optional
• confirm rights before planning a clip for upload
• show the user the material asset choices for a major creative deliverable
• plan reusable B-roll across multiple panels/concepts

Don't:

• plan footage that does not map to a blueprint shot
• assume a panel is covered without inspecting the source clip and coverage table
• label or depict an unknown location/person/product as verified
• over-polish UGC assets
• forget thumbnails, first frames, safe areas, captions, source audio

Troubleshooting

• A panel has no candidate footage: route it to socialseal-generation-prompts (write a prompt for an external generation tool) or flag for a reshoot.
• Too expensive: reduce locations and combine capture batches.
• No hero shot exists for the hook panel: the concept is not production-ready; revisit the blueprint.

Verification Checklist

• Every blueprint shot panel has a coverage status.
• Capture is batched where possible.
• Missing assets are listed with a fill path (capture/source/generate).
• Rights are confirmed for clips planned for upload.
• Editor handoff includes the brief, approved coverage table, accessible source clips, and unresolved blockers.