Infrastructure · Data Structures

Exception

Runtime anomaly signal

Definition

Mechanism

A signal indicating that the standard execution flow has encountered a critical anomaly or invalid State. Must be handled explicitly by a CircuitBreaker or FailClosed policy to prevent system corruption.

Invariants

  1. Classifies the anomaly by `error_code`.
  2. Must be handled by CircuitBreaker or FailClosed, never merely observed.

Risks

Failure modes

  1. Swallowed

    the signal is caught and discarded, so the invalid State continues unhandled.

  2. Over-broad code

    one `error_code` covers unrelated anomalies, so no handler can dispatch on it.

Relationships

Builds on

References

FailClosed

Default-deny policy for uncertain states

State

System condition at time T

Used by

References

Reference

Data schema

{
  "type": "object",
  "required": [
    "error_code",
    "message"
  ],
  "properties": {
    "error_code": {
      "type": "string",
      "description": "Standardized failure ID"
    },
    "message": {
      "type": "string",
      "description": "Human-readable description"
    },
    "stack_trace": {
      "type": "array",
      "description": "Execution context at failure"
    },
    "severity": {
      "type": "string",
      "enum": [
        "Fatal",
        "Error",
        "Warning"
      ]
    }
  }
}

Identity

Ref
Exception#ae94
Sema ID
sema:Exception#mh:SHA-256:ae9485039008abed9587e74c05a8c31c37d9a8f70347a11c0630fe87673fb7bb
Ring
0
Tier
1
Updated
2026-11-11
Supersedes
  • sema:Exception#mh:SHA-256:bcdc11a8b6e4c1af2def02029ab03bf24c1480bd827ee3d570e374096cfccdc6
  • sema:Exception#mh:SHA-256:39fb7ba646e5c1dc91699ae4b3dc0887f4ec476fe6bf29970b83aaaca025f686
  • sema:Exception#mh:SHA-256:054ce28455dfd0a13bce0b5a23e048429a58a1b7e6c9082252bc3f815fe6be21
  • sema:Exception#mh:SHA-256:61e41a9f4e26dad1ab09516b35640c6204e99e7d1df29ce0899bcbb24a126e1d
  • sema:Exception#mh:SHA-256:7c68ca1c9f4cae08d081d6fd31a667fa16a67d2de79eae1a96b196ad69bb9869