Start with what you notice
A symptom, frustration, missed result, or uncertain goal is enough. DR does not require the user to diagnose the system first.
The architecture is the evidence. The receipts are the proof.
DR is designed to show what was observed, what was tested, what changed, and what outcome followed.
Separate fact from assumption
DR preserves reported experience while distinguishing observations, beliefs, evidence, inference, conflicts, and missing information.
Inspect connected causes
Because DR spans workflows and industries, it can check whether the visible issue is being produced by another part of the system.
Validate before action
Likely causes become testable next steps. Protected actions remain governed, permission-aware, and receipted.