Lighting Editor Generator

Define the tool job and source contract

For Lighting Editor, specify the material entering the workflow, the transformation expected within video and image editing, and the deliverable leaving it. Keep generation, editing, publishing, and measurement as separate responsibilities. For this section 1, save a continuity sheet; have the legal reviewer review temporal stability; 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 editor evidence separate from lighting assumptions.

• Name required input rights and formats — record acceptance matrix, rights reviewer, action readability, and editorial approval; keep editor evidence separate from lighting assumptions.
• List controls that must be directly observable — record input manifest, motion designer, editability, and editorial approval; keep editor evidence separate from lighting assumptions.
• Define a reversible review handoff — record delivery checklist, visual lead, continuity, and editorial approval; keep editor 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 brand reviewer review continuity; record the failed case as well as the accepted one; and do not advance it beyond a shot approval until the named limitation is resolved. Keep editor 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 motion designer review camera intent; record the failed case as well as the accepted one; and do not advance it beyond a shot approval until the named limitation is resolved. Keep editor 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 producer review message clarity; 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 editor 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 brand reviewer review licensing; 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 editor evidence separate from lighting assumptions.

Build a specific test brief for lighting editor

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 reversible before-and-after edit with review notes. 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 rights reviewer review camera intent; record the failed case as well as the accepted one; and do not advance it beyond a production checkpoint until the named limitation is resolved. Keep editor evidence separate from lighting assumptions.

• Primary query: lighting editor; test record: evidence ledger, post supervisor, claim support, and production checkpoint; keep editor evidence separate from lighting assumptions.
• Editorial owner: keyword-expansion:0711; decision record: evidence ledger, rights reviewer, visual hierarchy, and evidence-backed brief; keep editor evidence separate from lighting assumptions.
• Source scope: a user-provided competitor-gap export dated 2026-08-05 supports topic prioritization only; source review: rights record, editor, source rights, and versioned review; keep editor 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 editor.” 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 prompt designer 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 editor evidence separate from lighting assumptions.