Defect taxonomy & triage
Shared severity/priority with SLAs, and — the RAPID-specific part — root-cause categories that tell you which part of the engine to fix. Classification turns defects into process feedback.
Severity & priority
Standard severity (S1–S4, see rapid-fix SLAs) and priority, with response/resolution SLAs.
Root-cause categories
Every defect is categorised by where it came from:
| Category | Fix the… |
|---|---|
| Spec gap (PFD) | acceptance-criteria / Definition rigour |
| AI-generated code defect | prompt / skill / coding standard |
| Human review miss | review standard / scrutiny tiers |
| Test gap | test strategy / coverage |
| Environment / data | environments / test data |
Why categorise
A defect isn't just a thing to fix — it's evidence about which part of the RAPID engine is weak. If most defects are "spec gap", Definition needs tightening; if "AI-generated code defect", a prompt or skill does. The taxonomy makes the pattern visible, so fixes target causes not symptoms.
Standards referenced: Orthogonal Defect Classification (adapted).