systematic-debugging

Systematic debugging enforces a disciplined, phase-driven approach to identify root causes before applying fixes. You need it to replace ad-hoc fixes with auditable investigations that preserve context across sessions. It is essential for multi-component system debugging where traceability matters.

You can debug recurring incidents by hydrating context from a memory system at the start of a session. This surfaces prior evidence and debugging context, allowing you to link events across sessions for traceable insights and continuous learning instead of starting from scratch.

To start a systematic debugging session, hydrate context from the memory system to surface prior evidence, then begin Phase 1 to identify root causes. The process progresses through five phases: Root Cause, Pattern, Hypothesis, Implementation, and Persistence, while logging progress for auditable traceability.

Yes, systematic debugging is applicable to incident response and multi-component system debugging. It supports linking sessions across events and components, ensuring root causes are identified and traceability is maintained through auditable logs and memory-backed insights.

Systematic debugging enforces a five-phase disciplined process—Root Cause, Pattern, Hypothesis, Implementation, and Persistence—before applying fixes, with progress logged to memory. Ad-hoc fixes lack this structure, omit memory integration, and fail to preserve debugging context or ensure continuous learning across sessions.

You should avoid a phase-based debugging process when dealing with trivial, isolated issues where establishing root causes or logging to a memory system adds unnecessary overhead. It is designed for multi-component system debugging and incident response where traceability and memory integration matter.