Define the procedure job before choosing a product

Treat “how to set yourself on fire as an effect” as a step-by-step learning 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. In the decision log, preserve the brief version, and ask the release approver to record visible continuity before the workflow transfer.

• Input: a risk-reviewed effect brief, non-hazardous source material, trained supervision when relevant, and a clearly fictional presentation In the decision log, preserve the source ledger, and ask the channel 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 In the decision log, preserve the control log, and ask the channel editor to record format readiness before the workflow transfer.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority In the decision log, preserve the input snapshot, and ask the claims reviewer to record evidence freshness before the workflow transfer.

Use the how-to method method

Translate the request into an input, a reversible action, a checkpoint, and a finished handoff. Practice on a duplicate or non-sensitive sample, preserve the original, and stop when authorization, account access, safety, or factual uncertainty appears. For this query, sequence the work into reversible decisions and observable review points. Keep notes about assumptions, source dates, failed checks, and human decisions beside the working asset. The how-to-guides 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. In the decision log, preserve the failure note, and ask the factual editor to record identity consent before the acceptance review.

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. While evidence is current, preserve the source ledger, and ask the factual editor to record input provenance before the reversible handoff.

• Replace hazardous action with simulation While evidence is current, preserve the brief version, and ask the workflow owner to record revision intent before the reversible handoff.
• Protect performers and bystanders While evidence is current, preserve the delivery checklist, and ask the factual editor to record control availability before the dated decision.
• Review context and disclosure While evidence is current, preserve the reference set, and ask the workflow owner to record evidence freshness before the dated decision.

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

The result should be reproducible from the written decisions while leaving product-specific buttons, limits, and account behavior to current official documentation rather than invented steps. 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 identity reviewer to record temporal order before the final sign-off.