Root-Cause Finder

Core Instruction

Before fixing the error, prove whether the code path that produced it was intended.

Do not stop at the first contract, parsing, type, null, or schema error. Treat it as a possible symptom.

Default Workflow

1. State the expected behavior in plain language.
2. State the invariant in one sentence.
3. State what definitely did not happen.
4. Trace the causal chain from the intended action or system event to the observed system effect.
5. Ask whether the request or mutation should have happened at all.
6. Identify the canonical source of truth and every competing source.
7. Find the first unintended side effect or write.
8. Only then decide whether a downstream contract fix is still necessary.