Define the explanation job before choosing a product

Treat “what are the four elements of a fire” 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 identity reviewer to record failure conditions before the source comparison.

• Input: a risk-reviewed effect brief, non-hazardous source material, trained supervision when relevant, and a clearly fictional presentation For the working record, preserve the source ledger, and ask the policy reviewer to record control availability before the source comparison.
• Success: a visual explanation or simulated effect that does not require injury, fire exposure, assault, or imitation of a dangerous act For the working record, preserve the control log, and ask the policy reviewer to record revision intent before the controlled revision.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority For the working record, preserve the input snapshot, and ask the creative lead to record input provenance 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. For the working record, preserve the failure note, and ask the channel editor to record control availability before the controlled revision.

Apply the safe effect planning boundary

Do not perform or encourage dangerous acts for footage. Use safe plates, compositing, stock assets, qualified professionals, and authoritative safety guidance; stop if real-world harm is possible. Work from a risk-reviewed effect brief, non-hazardous source material, trained supervision when relevant, and a clearly fictional presentation. Review toward a visual explanation or simulated effect that does not require injury, fire exposure, assault, or imitation of a dangerous act. 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. Before approval, preserve the source ledger, and ask the workflow owner to record temporal order before the final sign-off.

• Replace hazardous action with simulation Before approval, preserve the brief version, and ask the delivery owner to record destination fit before the final sign-off.
• Protect performers and bystanders For a controlled test, preserve the delivery checklist, and ask the workflow owner to record format readiness before the reversible handoff.
• Review context and disclosure For a controlled test, preserve the reference set, and ask the delivery owner 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. For the working record, preserve the source ledger, and ask the source custodian to record input provenance before the workflow transfer.