diagnose

To diagnose a failing test or outage without premature edits, apply a strict four-gate protocol: state the error, gather logs and environment details, list ranked hypotheses, and get explicit user approval before changing code.

A root-cause analysis protocol for broken pipelines enforces evidence-based debugging by requiring error statements, log collection, and three ranked hypotheses before any code changes are proposed or executed.

Structure software bug hypotheses by stating the error, collecting environment details and recent changes, then listing three ranked hypotheses to isolate the root cause before proceeding with fixes.

Yes, you can use this gated diagnostic protocol for failing tests, broken pipelines, and production outages. It requires gathering logs and recent changes to support evidence-based root-cause analysis across various failure types.

The best way to prevent premature fixes when debugging failures is to enforce a gated protocol that requires explicit user approval after ranking three hypotheses and gathering supporting logs, ensuring reproducibility before edits.