Define the orientation job before choosing a product

Treat “top view.ai” 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. During review, preserve the handoff draft, and ask the accessibility reviewer to record reversal cost before the editorial approval.

• Input: the exact product, provider, version, region, account surface, production job, and verification date During review, preserve the decision history, and ask the production lead to record format readiness before the editorial approval.
• Success: a dated evidence ledger covering identity, access, documented inputs, observable controls, outputs, limitations, and unresolved gaps During review, preserve the test fixture, and ask the source custodian to record failure conditions before the editorial approval.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority During review, preserve the review copy, and ask the continuity editor to record control availability before the editorial approval.

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. During review, preserve the delivery checklist, and ask the workflow owner to record format readiness before the production checkpoint.

Apply the named platform or model facts boundary

Do not infer SEELE support, model access, quality, legitimacy, censorship, ownership, API behavior, or compatibility from the query. Verify first-party documentation and direct observations on the use date. Work from the exact product, provider, version, region, account surface, production job, and verification date. Review toward a dated evidence ledger covering identity, access, documented inputs, observable controls, outputs, limitations, and unresolved gaps. 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 reversible workflow, preserve the decision history, and ask the workflow owner to record evidence freshness before the delivery pass.

• Confirm exact provider and version For a reversible workflow, preserve the handoff draft, and ask the delivery owner to record format readiness before the delivery pass.
• Date every changing fact For a reversible workflow, preserve the failure note, and ask the factual editor to record revision intent before the evidence refresh.
• Keep observations separate from documentation For a reversible workflow, preserve the authorization record, and ask the policy reviewer to record camera logic before the evidence refresh.

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. For the named reviewer, preserve the claim inventory, and ask the workflow owner to record input provenance before the rights check.