stuck

Break a fix-deploy-still-broken loop by applying a phased root-cause diagnosis protocol that enforces problem definition, truth auditing, and evidence chaining before any edits. This structured fault diagnosis approach prevents repeated deployment regressions and ensures auditable incident resolution.

The no-edits-until-Phase-5 rule is a debugging constraint that blocks code modifications until early diagnostic phases are complete. It forces engineers to document data, files, and decisions, establishing a verifiable evidence chain that ensures safe fixes and prevents regression.

Perform root-cause analysis for failed deployment rollbacks by defining the problem in Phase 1, auditing ground truth, and building an evidence chain. This phase-based diagnosis workflow generates a detailed Loop Report and enforces no edits until the investigation is complete.

Yes, phase-based diagnosis works for general software debugging cycles by applying a structured Loop, Ground Truth, and Evidence chain workflow. It guides engineers through disciplined problem definition and truth auditing to resolve incidents and prevent future regressions across various debugging contexts.

Debugging fixes keep failing after deployment when changes are applied without root-cause diagnosis. Using phase-based diagnosis to audit truth and chain evidence before editing ensures you identify the actual fault, breaking the cycle of deploying incomplete or incorrect fixes.