Define the orientation job before choosing a product

Treat “claude cowork setup guide” 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. At the next gate, preserve the test fixture, and ask the workflow owner to record failure conditions before the bounded test.

• Input: the exact product, provider, version, region, account surface, production job, and verification date At the next gate, preserve the review copy, and ask the factual editor to record evidence freshness before the bounded test.
• Success: a dated evidence ledger covering identity, access, documented inputs, observable controls, outputs, limitations, and unresolved gaps At the next gate, preserve the handoff draft, and ask the continuity editor to record reversal cost before the bounded test.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority At the next gate, preserve the decision history, and ask the delivery owner to record human approval before the bounded test.

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, 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 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. At the next gate, preserve the rights memo, and ask the brand reviewer to record input provenance before the editorial approval.

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. Before revision, preserve the input snapshot, and ask the policy reviewer to record failure conditions before the evidence refresh.

• Confirm exact provider and version Before revision, preserve the control log, and ask the identity reviewer to record human approval before the evidence refresh.
• Date every changing fact Before revision, preserve the rights memo, and ask the claims reviewer to record reversal cost before the evidence refresh.
• Keep observations separate from documentation Before revision, preserve the evidence table, and ask the channel editor to record claim scope before the rights check.

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. During review, preserve the failure note, and ask the channel editor to record camera logic before the editorial approval.