Define the orientation job before choosing a product

Treat “pre visualization software” 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. Before moving on, preserve the evidence table, and ask the source custodian to record destination fit before the evidence refresh.

• Input: an audience brief, supportable message, authorized references, beat list, visual constraints, and delivery target Before moving on, preserve the rights memo, and ask the continuity editor to record temporal order before the evidence refresh.
• Success: a traceable script or board in which each beat has a purpose, source, shot intention, continuity note, and review owner Before moving on, preserve the reference set, and ask the continuity editor to record identity consent before the rights check.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority Before moving on, preserve the delivery checklist, and ask the delivery owner to record claim scope before the rights check.

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 moving on, preserve the review copy, and ask the source custodian to record human approval before the delivery pass.

Apply the script and storyboard planning boundary

Templates and generated suggestions are proposals, not factual evidence or finished footage. Do not fabricate quotes, customer experience, product behavior, or rights to reference imagery. Work from an audience brief, supportable message, authorized references, beat list, visual constraints, and delivery target. Review toward a traceable script or board in which each beat has a purpose, source, shot intention, continuity note, and review owner. 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 rights memo, and ask the rights reviewer to record identity consent before the acceptance review.

• Map every beat to purpose and evidence For a controlled test, preserve the evidence table, and ask the model evaluator to record visible continuity before the acceptance review.
• Preserve source and identity rights For a controlled test, preserve the input snapshot, and ask the production lead to record human approval before the workflow transfer.
• Review continuity before visual polish For a controlled test, preserve the control log, and ask the accessibility reviewer to record source fidelity before the acceptance review.

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. At the next gate, preserve the rights memo, and ask the policy reviewer to record human approval before the controlled revision.