sgaabdu4 Repeated Failure Learning
Trigger
- Same root cause or failed approach occurs twice.
- User reports recurrence.
- Unrelated failures != recurrence.
- Failed candidate + original violation remains → prior cause/solution = unproven → return
diagnosing-bugs; same theory/variant mutation, retry, push, or publish = forbidden. - Comparable candidate fails twice → no third candidate;
question-measks whether the violation persists and whether a materially different direction is wanted. - Recurrence through an existing prose/static rule = false-gate evidence; do not count rule presence as prevention.
Ownership
- Diagnosis =
diagnosing-bugs. - Regression strength =
test-quality. - Gate contract + commands/hooks/CI =
deterministic-checks. - Any route → record recurrence evidence in the affected repository → hand packet to
he-learn; lifecycle continues. - Block delivery only when recurrence proves continued work risks security/privacy/accessibility/data integrity/data loss/irreversible action.
- This skill owns recurrence + root-cause evidence only; prevention selection =
he-learn.
Evidence
| Field | Required proof |
|---|---|
| Signature | Stable error/symptom + affected boundary |
| Attempts | Change + result for each comparable attempt |
| Recurrence | Same root cause or failed approach ≥2 times |
| Cause | Root owner + why prior action failed |
| Success | Correcting change + passing proof |
| Exposure | Callers/data/routes/tests/docs/config affected |
Complete
- Recurrence proven by comparable evidence.
- Root cause + successful correction identified.
- Evidence packet = signature + attempts + cause + correction + exposure.
he-learnpacket handed off in every route without routine source pause.
Report = PASS | CONCERNS | FAIL → recurrence proof → root cause → correction → exposure → handoff/gap.