ultrathink-protocol

Root cause analysis for persistent service failures requires a structured investigation process using explicit THOUGHT/ACTION/OBSERVATION cycles. This approach forces hypothesis testing with direct evidence from logs and process state, blocking implementation until the cause is verified.

Debugging multi-layer failures across runtime, middleware, and network boundaries requires a diagnosis ladder that traces the data path from symptom to divergence. This method escalates to source code reading and research only after standard diagnostic tools are exhausted.

To stop trial-and-error debugging during incident response, apply a verified-evidence gate before implementation. This blocks fixes until the root cause is confirmed by direct evidence from the running system, such as configuration reads, ports, and process inspection.

A structured debugging protocol is needed when a production incident remains unresolved after multiple unsuccessful fix attempts. If system symptoms persist despite restarts or configuration changes and the root cause is unknown, evidence-based troubleshooting replaces guessing.

Yes, this root cause analysis method applies to configuration verification in complex environments by requiring direct evidence reads from the running system. It ensures configuration state is explicitly verified against runtime behavior before any implementation changes occur.