GUIDED DIAGNOSIS BETA
Follow the evidence.
Start with the symptom and move through one justified check at a time. Network troubleshooting is available now, while beginner guidance and evidence capture continue to improve.
START HERE
What are you troubleshooting?
Choose the symptom, add only the context that matters, then follow the next evidence question. Nothing here runs commands or changes the system automatically.
Diagnostic context
Only add what matters. Context helps WWH decide whether earlier evidence still applies when a path is revisited.
How to use it.Run the suggested check, look at the highlighted result, then tell WWH what you found. WWH records your troubleshooting decisions in this tab, but it does not save raw command output or automatically change your system.
GUIDED DIAGNOSIS
METHOD BOUNDARY
Diagnosis before remediation.
When evidence reaches a change, escalation or vendor boundary, WWH stops and preserves what was established. After any justified change, the correct finish is to re-test the original symptom, not merely rerun the last diagnostic command.
Field Guide owns technical meaningCommands, examples, limitations and safety stay in the canonical Field Guide. Guided Diagnosis references them by stable ID.
Chains own reasoning flowSymptom, question, evidence boundary, human-selected outcome and next diagnostic path.
Troubleshooting history stores session decisionsContext, decisions, timestamps and path history are temporary session data, not copied knowledge.