Define the explanation job before choosing a product

Treat “what is a big flip” 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. For the working record, preserve the brief version, and ask the channel editor to record revision intent before the evidence refresh.

• Input: a clear definition of the term, the reader's production context, authorized examples, and an explicit question to resolve For the working record, preserve the source ledger, and ask the claims reviewer to record visible continuity before the evidence refresh.
• Success: a bounded explanation or plan that identifies the next decision without inventing product access, controls, evidence, or outcomes For the working record, preserve the control log, and ask the claims reviewer to record human approval before the evidence refresh.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority For the working record, preserve the input snapshot, and ask the identity reviewer to record format readiness before the evidence refresh.

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. For the working record, preserve the failure note, and ask the brand reviewer to record visible continuity before the rights check.

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. For a controlled test, preserve the source ledger, and ask the identity reviewer to record source fidelity before the release review.

• Clarify the intended meaning For a controlled test, preserve the brief version, and ask the claims reviewer to record claim scope before the release review.
• Choose an authorized example For a controlled test, preserve the delivery checklist, and ask the identity reviewer to record camera logic before the source comparison.
• Name the evidence needed for the next decision For a controlled test, preserve the reference set, and ask the claims reviewer to record temporal order before the source comparison.

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. At the next gate, preserve the source ledger, and ask the release approver to record failure conditions before the reversible handoff.