Severity Level
Objective
Capture and validate the severity level element within the Severity Scoring layer.
UAIF requirement
The incident record should implement the canonical severity_level field using the defined UAIF data type, validation constraints, and conditional rules.
Business impact
Supports consistent severity communication while preserving the analytical score, presentation score and calculation rationale separately.
Validation approach
Validate severity_level for numeric bounds and precision. Then review semantic consistency against the source incident evidence and the selected conformance profile.
Expected evidence
Retain the source record or analyst input for severity_level, schema-validation output, transformation history, selected profile, schema version and reviewer rationale where judgement is involved.
Mapping and source
UAIF Schema Specification; UAIF Technical Specification; JSON pointer /properties/severity_level.
Implementation guidance
Populate severity_level from an identified source or documented analyst decision. Enforce the schema constraints at record creation and update, preserve the original value and provenance, and surface validation failures without silently coercing data.
Assessment considerations
Sample records across normal, boundary and invalid conditions. Confirm that severity_level is populated only when applicable, conditional rules are enforced, provenance is retained and downstream systems do not change its meaning or precision.
Canonical schema definition
| JSON property | severity_level |
|---|---|
| Required in core profile | No |
| Type | "integer" |
| minimum | 1 |
| maximum | 5 |
Source: UAIF Schema Specification and UAIF Core JSON Schema.