Define the orientation job before choosing a product

Treat “tilt down” as a broad orientation request, not as evidence that a feature exists. The action implied by the query is to clarify the term and choose the next production decision; 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. During review, preserve the test fixture, and ask the claims reviewer to record claim scope before the workflow transfer.

• Input: a subject and story beat, authorized references, camera or composition intent, lighting and color context, and a delivery frame During review, preserve the review copy, and ask the identity reviewer to record source fidelity before the workflow transfer.
• Success: a visual decision whose angle, movement, framing, color, or effect strengthens the intended beat without confusing style with factual reality During review, preserve the handoff draft, and ask the release approver to record input provenance before the workflow transfer.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority During review, preserve the decision history, and ask the channel editor to record visible continuity before the workflow transfer.

Use the category discovery method

Start by defining the term or named product in neutral language, then separate the reader's likely production job from brand recognition, spelling variants, and search popularity. Build a shortlist of questions before opening any workspace or vendor page. For this query, clarify the intended meaning and production job before choosing a process or product. Keep notes about assumptions, source dates, failed checks, and human decisions beside the working asset. The category-discovery 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. During review, preserve the rights memo, and ask the policy reviewer to record destination fit 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. For a controlled test, preserve the input snapshot, and ask the workflow owner to record destination fit before the controlled revision.

• Tie the visual choice to a story beat For a controlled test, preserve the control log, and ask the delivery owner to record evidence freshness before the controlled revision.
• Use authorized references For a controlled test, preserve the rights memo, and ask the continuity editor to record failure conditions before the controlled revision.
• Review continuity, safety, and delivery context For a controlled test, preserve the evidence table, and ask the source custodian to record human approval before the controlled revision.

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

The handoff should state what the reader now understands, which interpretation remains uncertain, and which official source would be needed before a product-specific conclusion is publishable. 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. In the decision log, preserve the failure note, and ask the source custodian to record visible continuity before the dated decision.