Define the explanation job before choosing a product

Treat “what's a live action movie” as a definition and explanation 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. Before approval, preserve the failure note, and ask the brand reviewer to record failure conditions before the source comparison.

• Input: a clear definition of the term, the reader's production context, authorized examples, and an explicit question to resolve Before approval, preserve the authorization record, and ask the creative lead to record human approval before the source comparison.
• Success: a bounded explanation or plan that identifies the next decision without inventing product access, controls, evidence, or outcomes Before approval, preserve the claim inventory, and ask the policy reviewer to record reversal cost before the source comparison.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority Before approval, preserve the continuity note, and ask the identity reviewer to record claim scope before the controlled revision.

Use the concept explanation method

Move from a plain-language definition to one visual or production example, one counterexample, and a small observation exercise. Explain the durable concept first; treat named software, model behavior, and trend language as separate evidence questions. For this query, define the term, contrast adjacent meanings, and test understanding with an example. Keep notes about assumptions, source dates, failed checks, and human decisions beside the working asset. The concepts-explainers 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. Before approval, preserve the brief version, and ask the channel editor to record human approval before the release review.

Apply the topic orientation boundary

Treat ambiguous or weakly related search language as a question to clarify. Do not turn it into a SEELE capability, endorsement, factual claim, or interactive workflow without evidence. Work from a clear definition of the term, the reader's production context, authorized examples, and an explicit question to resolve. Review toward a bounded explanation or plan that identifies the next decision without inventing product access, controls, evidence, or outcomes. 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 handoff, preserve the continuity note, and ask the policy reviewer to record source fidelity before the bounded test.

• Clarify the intended meaning At handoff, preserve the claim inventory, and ask the creative lead to record reversal cost before the dated decision.
• Choose an authorized example At handoff, preserve the test fixture, and ask the release approver to record source fidelity before the dated decision.
• Name the evidence needed for the next decision At handoff, preserve the review copy, and ask the channel editor to record reversal cost before the reversible handoff.

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

A useful explanation lets a reader distinguish the concept from a nearby idea and apply it to a new example without depending on a vendor interface or an unsupported capability statement. 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. Before revision, preserve the continuity note, and ask the brand reviewer to record format readiness before the bounded test.