Define the orientation job before choosing a product

Treat “viral content architect” 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 approval, preserve the authorization record, and ask the model evaluator to record disclosure clarity before the workflow transfer.

• Input: authorized media, the intended account and destination, current platform rules, disclosure needs, and a named publisher Before approval, preserve the failure note, and ask the release approver to record camera logic before the workflow transfer.
• Success: a channel-ready handoff whose captions, links, claims, identities, commerce context, and synthetic-media disclosure have been reviewed Before approval, preserve the continuity note, and ask the policy reviewer to record evidence freshness before the workflow transfer.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority Before approval, preserve the claim inventory, and ask the creative lead to record control availability before the workflow transfer.

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 source ledger, and ask the identity reviewer to record temporal order before the rights check.

Apply the social and publishing policy boundary

Do not promise reach, approval, monetization, shop-link availability, or automatic publishing. Platform interface and policy facts must be checked at the time of handoff. Work from authorized media, the intended account and destination, current platform rules, disclosure needs, and a named publisher. Review toward a channel-ready handoff whose captions, links, claims, identities, commerce context, and synthetic-media disclosure have been reviewed. 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 revision, preserve the delivery checklist, and ask the workflow owner to record reversal cost before the editorial approval.

• Verify current channel policy Before revision, preserve the reference set, and ask the delivery owner to record claim scope before the production checkpoint.
• Review claims and disclosure Before revision, preserve the source ledger, and ask the workflow owner to record destination fit before the bounded test.
• Keep publishing with an authorized account owner Before revision, preserve the brief version, and ask the delivery owner to record evidence freshness before the bounded test.

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. Before moving on, preserve the review copy, and ask the rights reviewer to record temporal order before the rights check.