Make / Continuity workbook / task entry

Make a character passport workbook from authorized records.

Make a character passport workbook to assemble a portable editorial record with explicit rights, continuity states, version history, and approval fields; the artifact does not create imagery, scan identity, or activate a hidden passport capability.

Custom direction0 characters
TemplatesChoose one to replace the prompt above. You can switch at any time.
Review structured video direction
Video task: make a character passport workbook
Creative brief: 
Deliverable: Short concept sequence
Aspect ratio / frame: 16:9 landscape
Shot direction: Keep subject, action, setting, camera behavior, and ordered beats explicit.
Continuity: Preserve identity, wardrobe, objects, geography, lighting direction, and movement across the sequence.
Review criteria: Confirm the sequence serves the brief, respects rights and factual boundaries, and is ready for the intended delivery frame.

Prepared workflow

From brief to reviewable handoff.

Make a character passport workbook with reference provenance, invariant tables, scene-state tracking, attempt review, change control, and a production handoff page.

  1. 01

    Create the workbook cover and source register

    Begin with project, character, workbook version, owner, review date, and distribution scope. On the source sheet, assign a durable ID to every authorized image, drawing, performance, voice sample, wardrobe note, prop design, and story reference. Record creator or rights holder, permission scope, expiration, storage location, file hash when appropriate, approved uses, and missing coverage. Add a prominent column for real-person likeness and sensitive-data handling. Do not embed unneeded personal data or copy material into a wider-access workbook merely for convenience. A complete source register makes every later requirement traceable and exposes gaps before production begins.

    • Cover and change history
    • Authorized source register
    • Likeness and sensitivity flag
    • Missing reference list
  2. 02

    Build invariant, variation, and scene-state sheets

    Give stable traits one sheet with requirement, reference ID, affected shots, tolerance, failure code, and reviewer. Give authorized variations another sheet with trigger, permitted range, start and end beat, and approving owner. Use a timeline-style scene-state sheet for dirt, damage, weather, carried objects, wardrobe, knowledge, emotion, location, and screen direction. Write values that can be compared against a frame or track. Link every deliberate change to the script or approved art decision. This separation prevents a temporary state from rewriting identity and prevents a general design reference from freezing story-driven change.

  3. 03

    Add attempt review and publish a handoff snapshot

    Create one row per attempt with input packet version, visible product context, date, output ID, criterion findings, timecoded notes, decision, repair route, and reviewer. Preserve failed attempts when authorized so selections are not detached from their denominator. Add a dashboard that lists unresolved critical issues without turning scores into a product performance claim. Before handoff, freeze the workbook, export a readable snapshot, name the next owner, and specify the event that requires a new version. The completed artifact supports consistent human review; it cannot demonstrate automated preservation, current system capability, or successful video generation by itself.

Capability boundary

Dated evidence

Sources behind the current facts.

Product and model details can change. These links identify the evidence checked for the claims scoped below.

  1. X / the public discussion signalAI video character passport representative X circulation post

    Representative URL for circulation in the preserved observed public-post context only; it is not product, integration, capability, specification, access, availability, quality, repeatability, adoption, campaign, or commercial evidence.

Reader notes

Before you hand off.

What does this Make route produce?

It produces a workbook structure and handoff snapshot for an authorized team to complete, review, and version. It does not produce video or character assets.

Should approved and rejected attempts share one ledger?

Yes, when policy and permissions allow. Keeping their order and reasons makes the continuity decision auditable and prevents highlight-only reporting.

Continue the workflow

Take a prepared brief into the workspace.

Open the current SEELE Film & CG workspace only to verify the exact visible product context relevant to this assemble a versioned character-continuity workbook artifact task; do not infer capability or access from the public discussion signal.

Try it free