Define the verification job before choosing a product

Treat “does smoke have a shadow” as a yes-or-no verification request, not as evidence that a feature exists. The action implied by the query is to resolve a factual or conceptual question; the working object is editorial topic. Write the intended audience or user, authorized input, desired change, review owner, and finished handoff. Also state what the task excludes. This brief keeps search wording from turning into an unsupported promise about SEELE, a named vendor, a model, or an automatic result. For the working record, preserve the authorization record, and ask the source custodian to record format readiness before the acceptance review.

• Input: a subject and story beat, authorized references, camera or composition intent, lighting and color context, and a delivery frame For the working record, preserve the failure note, and ask the policy reviewer to record evidence freshness before the acceptance review.
• Success: a visual decision whose angle, movement, framing, color, or effect strengthens the intended beat without confusing style with factual reality For the working record, preserve the continuity note, and ask the accessibility reviewer to record source fidelity before the fallback decision.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority For the working record, preserve the claim inventory, and ask the production lead to record human approval before the acceptance review.

Use the how-to method method

Translate the request into an input, a reversible action, a checkpoint, and a finished handoff. Practice on a duplicate or non-sensitive sample, preserve the original, and stop when authorization, account access, safety, or factual uncertainty appears. For this query, identify the claim, the authoritative source, the date, and the conditions that could change the answer. Keep notes about assumptions, source dates, failed checks, and human decisions beside the working asset. The how-to-guides classification determines this learning sequence, while the authoritative taxonomy remains the only owner of the route. This page supplies editorial copy and cannot silently change the category, subhub, or URL. For the working record, preserve the source ledger, and ask the rights reviewer to record failure conditions before the workflow transfer.

Apply the camera, color, and visual language boundary

A named look or effect is an editorial direction, not proof of a product control or guaranteed output. Reference rights, safety, and truthful context still require review. Work from a subject and story beat, authorized references, camera or composition intent, lighting and color context, and a delivery frame. Review toward a visual decision whose angle, movement, framing, color, or effect strengthens the intended beat without confusing style with factual reality. A polished draft is not enough: the reviewer must be able to see which source supports each factual statement, who authorized each asset or identity, and which product behavior is still an unanswered test question. Topic selection alone never establishes safety, availability, quality, or permission. At the next gate, preserve the delivery checklist, and ask the production lead to record destination fit before the scope confirmation.

• Tie the visual choice to a story beat At the next gate, preserve the reference set, and ask the accessibility reviewer to record evidence freshness before the scope confirmation.
• Use authorized references At the next gate, preserve the source ledger, and ask the production lead to record visible continuity before the fallback decision.
• Review continuity, safety, and delivery context At the next gate, preserve the brief version, and ask the accessibility reviewer to record revision intent before the fallback decision.

Record evidence, review the handoff, and name the next check

The result should be reproducible from the written decisions while leaving product-specific buttons, limits, and account behavior to current official documentation rather than invented steps. Run separate passes for craft, factual accuracy, identity and source rights, safety, accessibility, and destination requirements. Record the source and verification date for any changing platform, model, price, policy, privacy, export, or compatibility statement. If primary evidence is missing, publish the item only as a question or editorial planning step. The finished handoff must name the approver and preserve a path back to the authorized original. For a reversible workflow, preserve the review copy, and ask the identity reviewer to record claim scope before the release review.