1Vehicle / Job Information
Start clean2Safety / Reproduction Gate
Do not force it3Condition Lock
Define the test conditionThe condition lock is the known setup where the symptom is supposed to show itself. Do not interpret the result until this is written down.
4Reproduction Attempt Log
Repeat the conditionRecord what actually happened. Do not convert memory, guesses, or “seems fine now” into proof.
Attempt 1
Attempt 2
Attempt 3
5Observation Quality
Evidence check6Reproduction Result
Choose one7Interpretation Guide
Route cleanDirect symptom path
Use when the complaint appears under the locked condition and can be observed safely. The next move is a system-specific proof test, not a parts guess.
Masking / distortion path
Use when the symptom changes after heat, load, reset state, bypass, recent service, connector movement, module state, or another system influence.
Inconclusive path
Use when the condition is unsafe, not repeatable, not directly observed, or drifting. Better capture comes before better diagnosis.