Define the troubleshooting job before choosing a product

Treat “why does fridge have a d” as a diagnostic request, not as evidence that a feature exists. The action implied by the query is to resolve a factual or conceptual question; 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 rights memo, and ask the continuity editor to record temporal order before the acceptance review.

• Input: a clear definition of the term, the reader's production context, authorized examples, and an explicit question to resolve During review, preserve the evidence table, and ask the source custodian to record destination fit before the acceptance review.
• Success: a bounded explanation or plan that identifies the next decision without inventing product access, controls, evidence, or outcomes During review, preserve the delivery checklist, and ask the delivery owner to record claim scope before the fallback decision.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority During review, preserve the reference set, and ask the continuity editor to record identity consent before the fallback decision.

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, preserve the original state, isolate one cause at a time, and use official recovery or support paths. 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. During review, preserve the test fixture, and ask the production lead to record reversal cost before the workflow transfer.

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. While evidence is current, preserve the control log, and ask the factual editor to record input provenance before the production checkpoint.

• Clarify the intended meaning While evidence is current, preserve the input snapshot, and ask the brand reviewer to record identity consent before the production checkpoint.
• Choose an authorized example While evidence is current, preserve the evidence table, and ask the delivery owner to record temporal order before the production checkpoint.
• Name the evidence needed for the next decision While evidence is current, preserve the rights memo, and ask the workflow owner to record revision intent before the production checkpoint.

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. For this decision, preserve the authorization record, and ask the creative lead to record source fidelity before the fallback decision.