Risk Score Triggers Wrong Escalation

A risk score, severity label, confidence value, or threshold result triggers the wrong escalation path.

What This Looks Like

The AI produces a risk score, severity label, confidence value, or threshold result that sends a case to the wrong escalation path. A low-risk case may be escalated unnecessarily, a high-risk case may be routed too weakly, or a case may go to the wrong reviewer, queue, workflow, or authority level.

Why It Matters

Escalation changes who reviews a case, how much scrutiny it receives, and what actions become available. If a score triggers the wrong escalation, the workflow can overreact, underreact, waste review capacity, or bypass the authority that should handle the case.

Structural Signal

A score crosses or fails to cross an escalation threshold in a way that does not match the intended authority path. The issue is not only that the score may be inaccurate; it is that the score is connected to escalation behavior that does not fit the case or governing rule.

Common Triggers

Thresholds are configured without enough calibration
Risk labels are treated as routing authority
The score is generated from incomplete or stale evidence
Escalation rules do not distinguish advisory scores from control signals
The workflow lacks a human or policy check before escalation
Similar scores route to different queues without a declared rule

When to Use This Issue

Use this Issue when a model-generated risk, severity, confidence, or threshold value causes the wrong escalation, review path, queue, or authority level.

When Not to Use This Issue

Do not use this Issue when the score is wrong but does not trigger escalation. Do not use it when the escalation path is correct but the reviewer disagrees with the score.

Primary Pattern

PAT-0300 — Escalation Growth

Declared Patterns

PAT-0300 — Escalation Growth
A structural condition where impact, authority, scope, or consequence increases across sequential states without a declared limiting mechanism.
PAT-0390 — Threshold Breach
A structural condition where an observed metric, value, state, or condition exceeds a declared quantitative or qualitative threshold.
PAT-0120 — Missing Authority
A structural condition where a region, action, state, or decision path exists without a declared governing authority.

Derived Primary Lenses

LEN-0100 — Absence Lens
Detects structurally required elements that are missing from the observed structure.
LEN-0110 — Authority Overlay Lens
Maps declared authority hierarchies onto observed structure to detect absence, override, or conflict.
LEN-0190 — Escalation Gradient Lens
Measures structural growth or intensification across sequential executions, states, or transitions.
LEN-0210 — Invariant Lens
Verifies that declared invariants are structurally enforceable and not contradicted by observed structure.
LEN-0290 — Variance / Entropy Lens
Measures structural variability across repeated or comparable evaluations and identifies divergence beyond expected bounds.

Derived Secondary Lenses

LEN-0120 — Boundary Compliance Lens
Evaluates observed structure against declared boundary posture, including allow, block, and exception rules.
LEN-0150 — Conflict Lens
Detects mutually incompatible constraints, claims, states, or declarations that cannot be simultaneously satisfied.
LEN-0250 — Propagation Lens
Traces how structural declarations, effects, or state changes propagate across boundaries or stages.
LEN-0270 — Reconciliation Lens
Evaluates whether structural changes align with declared authority updates, version changes, or reconciliation rules.

Search Intents

risk score triggers wrong escalation
AI risk score escalated wrong case
wrong escalation from model score
risk threshold caused wrong workflow
AI severity score triggered escalation
confidence score sent case to wrong review

Ontology Metadata

Code: ISS-0065
Version: ISS-0065@0.1.0
Ontology release: 0.1.0
Updated: 2026-05-10T00:00:00Z

History

No public history entries recorded.

View full ontology changelog