How to work through it

01

Define the orientation job before choosing a product

Treat “ai volcano” as a broad orientation 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. For a controlled test, preserve the continuity note, and ask the rights reviewer to record disclosure clarity before the reversible handoff.

  • Input: a risk-reviewed effect brief, non-hazardous source material, trained supervision when relevant, and a clearly fictional presentation For a controlled test, preserve the claim inventory, and ask the accessibility reviewer to record camera logic before the reversible handoff.
  • Success: a visual explanation or simulated effect that does not require injury, fire exposure, assault, or imitation of a dangerous act For a controlled test, preserve the authorization record, and ask the production lead to record input provenance before the reversible handoff.
  • Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority For a controlled test, preserve the failure note, and ask the identity reviewer to record visible continuity before the reversible handoff.
02

Use the category discovery method

Start by defining the term or named product in neutral language, then separate the reader's likely production job from brand recognition, spelling variants, and search popularity. Build a shortlist of questions before opening any workspace or vendor page. For this query, clarify the intended meaning and production job before choosing a process or product. Keep notes about assumptions, source dates, failed checks, and human decisions beside the working asset. The category-discovery 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 input snapshot, and ask the rights reviewer to record format readiness before the final sign-off.

03

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 moving on, preserve the claim inventory, and ask the continuity editor to record destination fit before the editorial approval.

  • Replace hazardous action with simulation Before moving on, preserve the continuity note, and ask the source custodian to record evidence freshness before the editorial approval.
  • Protect performers and bystanders Before moving on, preserve the review copy, and ask the rights reviewer to record control availability before the bounded test.
  • Review context and disclosure Before moving on, preserve the test fixture, and ask the model evaluator to record evidence freshness before the bounded test.
04

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

The handoff should state what the reader now understands, which interpretation remains uncertain, and which official source would be needed before a product-specific conclusion is publishable. 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. In the decision log, preserve the decision history, and ask the claims reviewer to record destination fit before the scope confirmation.