Read-only until authorized
No file changes before explicit repair authorization. If you reject the conclusion, it stays read-only and tests a new hypothesis.
← Back to workflowsREAD-ONLY → REPAIR
WORKFLOW 02 / 05
Diagnose
Reproduce a failure, find its root cause, then repair when authorized.
How it runs
Human approval required- 01Pin the symptom
State the expected versus actual behavior, then build the fastest, most deterministic reproduction signal.
- 02Minimize & locate
Observe the failure with your own eyes first, then strip it down — test one falsifiable hypothesis at a time.
- 03Repair when authorizedHuman approval required
After authorization, the first write must be a regression test. Watch it fail (red) before any production code may change (green).
- 04Harden the root cause
Add only the adjacent cases that prevent the same class of regression — never grow a fix into a redesign.
- 05Complete
Re-verify the original symptom and report the root cause, evidence, fix, and remaining uncertainty.
Key mechanisms
Red before green
The first write after authorization is the regression test, and its failure must be observed. No probe or workaround can bypass this gate.
One hypothesis at a time
Each observation is chosen to distinguish between hypotheses — never change two variables at once.