Lighting Generator

Define the tool job and source contract

For Lighting Generator, specify the material entering the workflow, the transformation expected within general video generation, and the deliverable leaving it. Keep generation, editing, publishing, and measurement as separate responsibilities. For this section 1, save a continuity sheet; have the visual lead review motion coherence; record the failed case as well as the accepted one; and do not advance it beyond a approved master until the named limitation is resolved. Keep generator evidence separate from lighting assumptions.

• Name required input rights and formats — record prompt brief, prompt designer, action readability, and approved master; keep generator evidence separate from lighting assumptions.
• List controls that must be directly observable — record evidence ledger, creative producer, visual hierarchy, and workflow decision; keep generator evidence separate from lighting assumptions.
• Define a reversible review handoff — record continuity sheet, producer, source rights, and workflow decision; keep generator evidence separate from lighting assumptions.

Compare against a stable acceptance frame

Use the same inputs, review dimensions, and stopping rules for every candidate. Record tradeoffs separately from availability so a promising test is not mistaken for verified product support. For this section 2, save a shot contract; have the producer review visual hierarchy; record the failed case as well as the accepted one; and do not advance it beyond a approved master until the named limitation is resolved. Keep generator evidence separate from lighting assumptions.

Run a bounded tool test

Use one representative asset and a fixed brief. Observe what the interface actually accepts, which controls affect the result, how revisions behave, and what must still be completed elsewhere. Record failures as carefully as successes. For this section 3, save a prompt brief; have the brand reviewer review temporal stability; record the failed case as well as the accepted one; and do not advance it beyond a approved master until the named limitation is resolved. Keep generator evidence separate from lighting assumptions.

Select on workflow fit, not implied automation

Compare review effort, controllability, source fidelity, rights handling, and export readiness. A useful planning page does not upload media, invoke a model, or manufacture a result merely because the query contains the word tool. For this section 4, save a revision log; have the creative producer review identity consent; record the failed case as well as the accepted one; and do not advance it beyond a approved master until the named limitation is resolved. Keep generator evidence separate from lighting assumptions.

Keep the evidence ledger attached to the decision

Partial evidence was supplied, but it does not establish product support or a complete capability, customer, or performance claim. Record the source, verification date, claim scope, unresolved gap, and the decision that the evidence can support. Search demand must never be reused as capability proof. For this section 5, save a frame review; have the producer review delivery fit; record the failed case as well as the accepted one; and do not advance it beyond a approved master until the named limitation is resolved. Keep generator evidence separate from lighting assumptions.

Build a specific test brief for lighting generator

Start with a rights-cleared representative source and a written acceptance brief. Define one observable change, protected details, a stopping rule, and the named reviewer. The intended output is a reviewable visual-production brief and evidence-aware handoff. Test one variable per version, preserve the source and settings, and compare results at the actual delivery size instead of choosing from an unrecorded impression. For this topic test, save a decision memo; have the editor review continuity; record the failed case as well as the accepted one; and do not advance it beyond a source-preserving edit until the named limitation is resolved. Keep generator evidence separate from lighting assumptions.

• Primary query: lighting generator; test record: decision memo, rights reviewer, camera intent, and bounded experiment; keep generator evidence separate from lighting assumptions.
• Editorial owner: keyword-expansion:0825; decision record: annotated source board, technical reviewer, revision control, and editorial approval; keep generator evidence separate from lighting assumptions.
• Source scope: a user-provided competitor-gap export dated 2026-08-05 supports topic prioritization only; source review: delivery checklist, rights reviewer, continuity, and versioned review; keep generator evidence separate from lighting assumptions.

Separate topic fit from product proof

A dated, user-provided competitor-gap export supports only the decision to cover “lighting generator.” It does not prove audience demand, SEELE capability, third-party behavior, commercial value, or a likely outcome. Verify product-specific statements against current first-party documentation and a recorded representative test. For this source review, save a versioned handoff; have the product specialist review editability; record the failed case as well as the accepted one; and do not advance it beyond a rights-cleared draft until the named limitation is resolved. Keep generator evidence separate from lighting assumptions.