Photo Lighting Editor Generator

Define the tool job and source contract

For Photo 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 shot contract; have the editor review visual hierarchy; 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 photo assumptions.

• Name required input rights and formats — record decision memo, technical reviewer, claim support, and release review; keep editor evidence separate from photo assumptions.
• List controls that must be directly observable — record rights record, channel owner, temporal stability, and production checkpoint; keep editor evidence separate from photo assumptions.
• Define a reversible review handoff — record versioned handoff, product specialist, visual hierarchy, and production checkpoint; keep editor evidence separate from photo 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 continuity sheet; have the post supervisor review motion coherence; 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 photo 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 evidence ledger; have the channel owner review revision control; 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 photo 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 test worksheet; have the legal reviewer review input fidelity; 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 photo 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 annotated source board; have the art director review message clarity; 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 photo assumptions.

Build a specific test brief for photo lighting editor

Start with an authorized still image and its untouched original. 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 test worksheet; have the art director review identity consent; record the failed case as well as the accepted one; and do not advance it beyond a reversible handoff until the named limitation is resolved. Keep editor evidence separate from photo assumptions.

• Primary query: photo lighting editor; test record: test worksheet, channel owner, action readability, and shot approval; keep editor evidence separate from photo assumptions.
• Editorial owner: keyword-expansion:0576; decision record: prompt brief, product specialist, visual hierarchy, and evidence-backed brief; keep editor evidence separate from photo assumptions.
• Source scope: a user-provided competitor-gap export dated 2026-08-05 supports topic prioritization only; source review: annotated source board, product specialist, continuity, and rights-cleared draft; keep editor evidence separate from photo assumptions.

Separate topic fit from product proof

A dated, user-provided competitor-gap export supports only the decision to cover “photo 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 delivery checklist; have the prompt designer review message clarity; record the failed case as well as the accepted one; and do not advance it beyond a dated decision until the named limitation is resolved. Keep editor evidence separate from photo assumptions.