← Catalogue
World Models · legacy example

Incident & Emergency

This meta-model describes harm events that require response: from the first report through severity grading, alerting and response operations to resolution and after-action review. It is its own model, extending the generic occurrence (X1), because harm events carry semantics no ordinary happening has: graded severity, attributable impact, organized response and a formal closure and learning cycle.

AI YAMLAGENTS.mdSource
IDworld.x3-incident-and-emergency
Version history0.2.0-legacy
CategoryReference example
IndustryCross-industry
Domainevents-phenomena
Tagsincident, emergency
Data structure

Bundles and layers

Bundle

incident

The harm event and how bad it is

Layers

incidentCore`: kind, report and status of the incident · `severity`: graded judgements on declared scales · `impact`: harm attributed to people, assets and services

Bundle

response

Warning and organized reaction

Layers

alerting`: warning messages, levels and audiences · `operations`: response efforts and responder deployments

Bundle

closure

How the incident ends and what is learned

Layers

resolution`: the closure statement and residual risk · `review`: structured after-action findings

Findings

Catalogue-native findings must describe the information grouped by each layer. This legacy version does not declare them separately.

Questions & artifacts

Questions, artifact requirements and serial naming rules are required by Vercy vNext; they remain unassigned in this reference version.

Service layers

How this specification operates

Dimension & namespace

  • EXTEND `world.occurrenceEvent` (X1): an incident is an occurrence with severity, impact and response semantics added
  • REFERENCE `world.buildingStructure` (U1): damaged buildings and structures in impact records
  • REFERENCE `world.premisesSpatialUnit` (U2): affected premises and their occupancy context
  • REFERENCE `world.physicalInfrastructureNetwork` (U3): affected network assets, mirrored there as closure events
  • REFERENCE `world.situationCondition` (X4): a prolonged emergency is registered as a situation while it holds
  • REFERENCE `world.person` (H1): affected parties and individual responders
  • REFERENCE `world.organization` (O1): responder units and relief organizations
  • imports: oasis-cap (EXTEND: alert message structure, levels and audiences)
  • imports: iso-22320 (ALIGN: incident response terminology)

Canon, patches & standards

  • EXTEND `world.occurrenceEvent` (X1): an incident is an occurrence with severity, impact and response semantics added
  • REFERENCE `world.buildingStructure` (U1): damaged buildings and structures in impact records
  • REFERENCE `world.premisesSpatialUnit` (U2): affected premises and their occupancy context
  • REFERENCE `world.physicalInfrastructureNetwork` (U3): affected network assets, mirrored there as closure events
  • REFERENCE `world.situationCondition` (X4): a prolonged emergency is registered as a situation while it holds
  • REFERENCE `world.person` (H1): affected parties and individual responders
  • REFERENCE `world.organization` (O1): responder units and relief organizations
  • imports: oasis-cap (EXTEND: alert message structure, levels and audiences)
  • imports: iso-22320 (ALIGN: incident response terminology)

Artifact formats & serial data

Format-independent core. Concrete artifact formats and naming prefixes are not declared in this legacy version.

Policies & accepted processes

  • `publicAlertFeed`: open dissemination of active alerts to any consumer
  • `mutualAidExchange`: data sharing between cooperating response operators during and after incidents
  • `impactDisclosureContract`: verified impact data disclosed to insurers or relief organizations under owner grant

Read / add / edit / delete

CRUD procedures and interface bindings are not declared in this legacy version.

Ownership, roles & access

The owner archetype is the emergency response operator, which stewards incident, alert and operation records. Victims' and responders' personal details are disclosed only under S2 grants, statistics are released in aggregate form, and the full record trail is auditable via S4.

Existing assembly

Objects, relationships, events and projections

Objects

  • `incident`: a harm-causing or harm-threatening occurrence requiring response; key attributes: incidentKind, reportedAt, status
  • `severityAssessment`: a graded judgement of how bad the incident is; key attributes: scale, grade, assessedAt
  • `impactRecord`: harm attributed to the incident across people, assets and services; key attributes: impactKind, quantity, verified
  • `alert`: a warning message issued about the incident; key attributes: alertLevel, audience, issuedAt, expiresAt
  • `responseOperation`: an organized effort to contain and resolve the incident; key attributes: operationKind, startedAt, endedAt, commandRef
  • `responderAssignment`: a responder unit's deployment into an operation; key attributes: unitRef, assignedAt, releasedAt
  • `resolutionRecord`: the closure statement of the incident; key attributes: resolvedAt, outcome, residualRisk
  • `afterActionReview`: the structured review of the response; key attributes: reviewedAt, findings, recommendations

Relationships

  • `severityAssessment` -> grades -> `incident` (n:1): regrades accumulate as the picture clarifies
  • `alert` -> warnsOf -> `incident` (n:1): one incident can drive several alerts to different audiences
  • `responseOperation` -> respondsTo -> `incident` (n:1): large incidents can carry several parallel operations
  • `responderAssignment` -> deploysInto -> `responseOperation` (n:1): units join and leave operations over time
  • `impactRecord` -> attributesHarmTo -> `incident` (n:1): impacted objects are referenced in U1, U2, U3 and H1
  • `resolutionRecord` -> closes -> `incident` (1:1): exactly one closure statement per incident
  • `afterActionReview` -> examines -> `responseOperation` (n:1): reviews target operations, not victims

Events

  • `incidentReported`: a harm event was reported and entered the record
  • `alertIssued`: a warning was published to a defined audience
  • `severityRegraded`: the graded severity changed on new information
  • `responseDispatched`: an operation was launched or a unit deployed
  • `impactAssessed`: harm was attributed and quantified
  • `incidentContained`: the harm stopped spreading though the incident remained open
  • `incidentResolved`: the incident was closed with an outcome and residual risk
  • `reviewCompleted`: the after-action review was finished and findings recorded

Projections

  • `liveIncidentBoardProjection`: active incidents with alert levels and operation status; omits victim identities
  • `incidentStatisticsProjection`: aggregate frequency, severity and impact; omits all case-level detail
  • `afterActionSummaryProjection`: findings and recommendations; omits personal data of responders and victims