Root Cause
Find the demonstrated cause of the observed failure and the control that would have refused it. This skill diagnoses; repair-in-place or the owner fixes.
Rules
- Every link cites an observation. A link that you reasoned to is where the chain becomes a story.
- Stop at a cause this repository owns. A vendor decision or "the model was wrong" gives you nothing to build a Control against.
- Never stop on a person. "Someone forgot" means the chain stopped early. Ask what let the mistake reach a commit.
1. Reproduce the defect
Run the failing command and paste its output. Record the input, the observed failure and the expected behaviour. For a recurring failure, read the record's tracker notes and git log -S SYMBOL for earlier attempts. When two causes predict the same result, use falsify-first to find an observation that tells them apart.
2. Ask why
Ask why until the answer is a cause this repository controls. Each link cites a file:line, a command and its output, a ledger row or a recorded verdict. When the next why leaves this repository, go back one link and name the Control there.
At each link where a second answer was available, name it and say why you took the other one.
3. Test the chain
- Per cause: if you removed this cause, would the failure still happen? If yes, it is a condition you noticed, not a cause. Continue the chain.
- For the chain: if you removed every cause in it, could the failure still happen? If yes, a link is missing, and that link needs the Control.
A second person can run these two tests against your chain without a new derivation.
4. Output
| Field | Content |
|---|---|
| Chain | Each why with its cited observation, in order, ending at the cause this repository owns |
| Control | The check, gate, schema field, refusal or document that would have stopped this defect; its Tier says how strongly |
| Tier | How strongly the Control acts, in the engine's terms: control (a gate fails), warning (it reports and continues) or documentation (a person must read it). Record a documentation tier as a downgrade, with the reason that no stronger control was available |
| Covers | The observed defect and related call paths established by evidence |
| Branch not taken | One line |
Hand the fix to repair-in-place, or to the owner, with the Control row. Record other improvements as separate recommendations.
For a worked chain from signal to control, read example.