Define the explanation job before choosing a product

Treat “what elements are in 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. At the next gate, preserve the test fixture, and ask the source custodian to record input provenance before the workflow transfer.

• Input: a risk-reviewed effect brief, non-hazardous source material, trained supervision when relevant, and a clearly fictional presentation At the next gate, preserve the review copy, and ask the continuity editor to record identity consent before the workflow transfer.
• Success: a visual explanation or simulated effect that does not require injury, fire exposure, assault, or imitation of a dangerous act At the next gate, preserve the handoff draft, and ask the accessibility reviewer to record temporal order before the workflow transfer.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority At the next gate, preserve the decision history, and ask the production lead to record revision intent before the workflow transfer.

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. At the next gate, preserve the rights memo, and ask the delivery owner to record failure conditions before the workflow transfer.

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. For this decision, preserve the input snapshot, and ask the creative lead to record destination fit before the source comparison.

• Replace hazardous action with simulation For this decision, preserve the control log, and ask the policy reviewer to record control availability before the source comparison.
• Protect performers and bystanders For this decision, preserve the rights memo, and ask the identity reviewer to record failure conditions before the source comparison.
• Review context and disclosure For this decision, preserve the evidence table, and ask the claims reviewer to record format readiness 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. While evidence is current, preserve the failure note, and ask the claims reviewer to record identity consent before the reversible handoff.