Category, severity, and capture source

An ErrorAssessment contains category and severity. Capture source belongs to the original ErrorOccurrence. These dimensions answer different questions and must not be inferred from one another.

ErrorCategory: what area failed?

The closed vocabulary contains domain, application, infrastructure, integration, framework, configuration, lifecycle, and unknown. Applications extend classification behavior through ordered ErrorClassifier implementations, not string categories.

ErrorSeverity: what is the application impact?

• recoverable: one operation failed and state remains consistent;
• degraded: the application continues with reduced capability;
• critical: a significant scope needs controlled recovery;
• fatal: the current process or isolate cannot continue safely.

Derived properties such as requiresApplicationTermination come from the enum extension, so a separate flag cannot contradict severity.

ErrorCaptureSource: where was it observed?

The values are zone, framework, platform, isolate, and reported. A framework error is not automatically critical, and a Zone error is not automatically fatal.

Classifiers run in registration order. The first supporting classifier owns the occurrence. DefaultErrorClassifier remains the final fallback and produces unknown with critical severity.