Incident & Emergency
Authority-declared operational or emergency incident with revisioned severity impact containment restoration resolution and review
Bundle → Layer → Finding → Questions Incomplete
3 bundles · 7 layers · 0 findings · 0 questions
incident The harm event and how bad it is
incidentCore
kind, report and status of the incident
severity
graded judgements on declared scales
impact
harm attributed to people, assets and services
response Warning and organized reaction
alerting
warning messages, levels and audiences
operations
response efforts and responder deployments
closure How the incident ends and what is learned
resolution
the closure statement and residual risk
review
structured after-action findings
Note: Legacy card: layers named, findings and questions never written.
Classifiers Filled
- Family
- World Models
- Category
- Activities and processes
- Entry kind
- standalone-mm
- Navigation path
- NAV.ACT.INC
- Domain
- ACT.INC
- Industry
- Cross-industry
- Tags
- incidentemergencyact.inc
- Also called
- X3
What it is Derived, awaiting review
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.
Note: First sentence of the legacy card introduction.
Why it exists Filled
Authority-declared operational or emergency incident with revisioned severity impact containment restoration resolution and review
Distinguishing features Derived, awaiting 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.
What robots and AI may and may not do Missing, in the backlog
Not described yet. This gap is in the card backlog.
Moral aspects Derived, awaiting review
- 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.
- afterActionSummaryProjection: findings and recommendations; omits personal data of responders and victims
Owners Filled
Steward
The owner archetype is the emergency response operator, which stewards incident, alert and operation records.
Links to other meta-models Filled
extends
- world.occurrenceEvent - an incident is an occurrence with severity, impact and response semantics added
references
- world.buildingStructure - damaged buildings and structures in impact records
- world.premisesSpatialUnit - affected premises and their occupancy context
- world.physicalInfrastructureNetwork - affected network assets, mirrored there as closure events
- world.situationCondition - a prolonged emergency is registered as a situation while it holds
- world.person - affected parties and individual responders
- world.organization - responder units and relief organizations
requires
- vr.wm-act-017
- vr.wm-blt-002
- vr.wm-blt-003
- vr.wm-blt-005
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Direct properties not applicable Not applicable
Not applicable
Institutional or informational subject: no invented physical properties.
Recognition optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Derived, awaiting review
- 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
Legacy events listed as state transitions.
Hazards and failure modes optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Derived, awaiting review
- 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
- 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
Context of use required Filled
- 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.
Sources Missing, in the backlog
Not described yet. This gap is in the card backlog.
Open questions
- Superseded by a researched world model? Map this legacy card to its successor or retire it.
Machine files
Provenance
legacy MMAS card (world-models v0.2) · legacy
Built from: models/world-x3-incident-and-emergency/spec.yaml, models/docs/events-phenomena/X3-incident-and-emergency.md