Error Classification
Classify abnormal states before designing their handling. Different words imply different interventions.
Working Vocabulary
Error: a human or system mistake in reasoning, input, configuration, or operation.
Defect: a flaw in an artifact such as code, requirements, tests, or documentation.
Bug: an informal report or label for a defect, fault, or failure; clarify which precise category is meant before choosing a response.
Fault: an incorrect internal state or latent condition that can cause failure.
Failure: externally observable deviation from expected service.
Incident: an operational event requiring response.
Exception: a language/runtime control mechanism or signal, not a domain classification by itself; classify the condition it represents.
Workflow
Describe what was observed and by whom.
Separate external failure from internal fault and underlying defect.
Identify whether the condition is recoverable, retryable, user-correctable, or fatal.
Choose handling: validation error, typed domain error, exception, retry, circuit breaker, alert, or defect fix.
Detailed Reference
For non-trivial implementation, review, or refactoring work, read references/details.md before giving final guidance. It contains the detailed rules, examples, smells, and migration notes that do not belong in the short invocation body.
Output
Return the classification chain, handling strategy, tests to add, and terms the team should use consistently.
1---2name: error-classification3description: Use when clarifying software abnormal-state terminology such as error, defect, fault, failure, bug, incident, and exception. Helps choose handling, testing, and mitigation strategies from precise classification. Trigger for error terminology, fault versus failure, defect versus bug, abnormal-state design, failure analysis, or test classification.4---56# Error Classification78Classify abnormal states before designing their handling. Different words imply different interventions.910## Working Vocabulary1112- Error: a human or system mistake in reasoning, input, configuration, or operation.1314- Defect: a flaw in an artifact such as code, requirements, tests, or documentation.1516- Bug: an informal report or label for a defect, fault, or failure; clarify which precise category is meant before choosing a response.1718- Fault: an incorrect internal state or latent condition that can cause failure.1920- Failure: externally observable deviation from expected service.2122- Incident: an operational event requiring response.2324- Exception: a language/runtime control mechanism or signal, not a domain classification by itself; classify the condition it represents.2526## Workflow27281. Describe what was observed and by whom.29302. Separate external failure from internal fault and underlying defect.31323. Identify whether the condition is recoverable, retryable, user-correctable, or fatal.33344. Choose handling: validation error, typed domain error, exception, retry, circuit breaker, alert, or defect fix.3536## Detailed Reference3738For non-trivial implementation, review, or refactoring work, read `references/details.md` before giving final guidance. It contains the detailed rules, examples, smells, and migration notes that do not belong in the short invocation body.3940## Output4142Return the classification chain, handling strategy, tests to add, and terms the team should use consistently.
amadeus-dlc