Engine & Framework

Deterministic. Reproducible. Auditable. Every result can be re-run from the same inputs and will return the same output.

◆ Inkanyamba

Named after a storm-force from Southern African tradition — Inkanyamba appears when systems are under stress and decisions cannot wait. That is exactly the context this engine is built for.

Emergency Response

Purpose

Emergency response is the shock layer of the disaster cycle. It captures what changed, which systems are disrupted, and which delivery constraints are now binding.

What This Section Holds

Key Concepts & Definitions

Term Definition
Shock Event Immediate incident causing disruption (e.g., flood, fire, cyber‑attack).
Constraint Limitation on modality feasibility (access, security, finance, protection).
Rapid Feasibility Check Quick assessment of modality suitability under current constraints.

Process Flow

  1. Event Capture – Manual or sensor‑based entry of incident details.
  2. Impact Assessment – Map affected areas, infrastructure status, and population exposure.
  3. Constraint Identification – Populate the constraint matrix (access, security, finance, protection).
  4. Rapid Feasibility – Run the CDI scoring engine with shock‑specific inputs.
  5. Output Generation – Produce a feasibility summary and highlight critical gaps.

Evidence & Data Sources

Decision Brief Template

Shock Summary – Flash flood affecting 3 km², 1 500 people displaced.

Key Constraints – Road access reduced 60 %, power outage 80 %, market price surge 30 %.

Feasibility – Cash assistance viable (score 0.78), in‑kind limited (score 0.42).

Recommendations – Prioritise cash distribution, pre‑position shelters, coordinate with power restoration.

Governance & Review

WordPress Subpages

Page Slug Purpose
Event Input /emergency-response/event-input/ Shock data, changed conditions, and affected area notes
Rapid Feasibility Check /emergency-response/rapid-feasibility-check/ Fast route into modality feasibility assessment