Define the procedure job before choosing a product

Treat “how to zoom out in epic” as a step-by-step learning 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 handoff draft, and ask the model evaluator to record claim scope before the source comparison.

• Input: a clear definition of the term, the reader's production context, authorized examples, and an explicit question to resolve Before approval, preserve the decision history, and ask the rights reviewer to record source fidelity before the source comparison.
• Success: a bounded explanation or plan that identifies the next decision without inventing product access, controls, evidence, or outcomes Before approval, preserve the test fixture, and ask the accessibility reviewer to record human approval before the release review.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority Before approval, preserve the review copy, and ask the production lead to record failure conditions before the release review.

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, sequence the work into reversible decisions and observable review points. 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. Before approval, preserve the delivery checklist, and ask the continuity editor to record reversal cost before the source comparison.

Apply the topic orientation boundary

Treat ambiguous or weakly related search language as a question to clarify. Do not turn it into a SEELE capability, endorsement, factual claim, or interactive workflow without evidence. Work from a clear definition of the term, the reader's production context, authorized examples, and an explicit question to resolve. Review toward a bounded explanation or plan that identifies the next decision without inventing product access, controls, evidence, or outcomes. 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 decision history, and ask the identity reviewer to record reversal cost before the fallback decision.

• Clarify the intended meaning Before revision, preserve the handoff draft, and ask the claims reviewer to record source fidelity before the scope confirmation.
• Choose an authorized example Before revision, preserve the failure note, and ask the policy reviewer to record disclosure clarity before the scope confirmation.
• Name the evidence needed for the next decision Before revision, preserve the authorization record, and ask the source custodian to record control availability before the scope confirmation.

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. While evidence is current, preserve the claim inventory, and ask the continuity editor to record claim scope before the acceptance review.