{"id":"TEC-009","name":"Troubleshooting begins with observable symptom","domain":"technical_writing","layer":"section","strength":"hard_constraint","human_logic":"IF troubleshooting advice begins with an assumed cause, THEN reframe from the user-observable symptom and branch by tests ELSE retain.","when":{"all":[{"path":"section.topic_type","operator":"eq","value":"troubleshooting"},{"path":"section.entry_point","operator":"eq","value":"assumed_cause"}]},"then":[{"action":"restructure","target":"section","pattern":"symptom -> discriminating_check -> cause -> fix -> verification"}],"else":[{"action":"retain","target":"current_text","reason":"No triggering condition is present."}],"unless":[],"because":"Users know what they observe, not necessarily what caused it.","diagnostics":[],"examples":{},"source_ids":["WEB-008","BK-024"],"laka":{"smallest_sufficient_intervention":true,"primary_axes":["scope","depth","magnitude","reversibility"]},"requires_facts":["section.topic_type","section.entry_point"],"tests":[{"id":"TST-016","rule_id":"TEC-009","before":"Cause: The token expired. Fix it.","after":"Symptom: Sign-in returns “token expired.” Generate a new token, retry sign-in, and confirm the account page opens.","reason":"Troubleshooting starts from observation and ends with verification.","assertion":{"if":{"path":"output","operator":"eq","value":"Symptom: Sign-in returns “token expired.” Generate a new token, retry sign-in, and confirm the account page opens."},"then":"pass","else":"review"}}],"sources":[{"id":"WEB-008","title":"DITA 1.3 Technical Content Specification","creator":"OASIS","domain":"structured_authoring","type":"OASIS Standard","note":"Topic-based concept, task, reference, troubleshooting, and reuse architecture.","url":"https://docs.oasis-open.org/dita/dita/v1.3/os/part2-tech-content/dita-v1.3-os-part2-tech-content.html"},{"id":"BK-024","title":"Developing Quality Technical Information","creator":"Michelle Carey; Moira Lanyi; Deirdre Longo; et al.","domain":"technical_writing","type":"Book","note":"Quality dimensions for usable technical information.","url":null}],"defined_in":{"file":"15-technical-writing-rules.json","title":"Technical Writing and Documentation Rules","slug":"technical-writing-rules"}}