Disaster Response

advanced · 4 agents · 12 skills

A multi-agent emergency management system that coordinates sensor aggregation, disaster assessment, resource allocation, and public communications across four specialized agents. The sensor hub aggregates feeds from weather stations, seismic sensors, flood gauges, and satellite imagery. The coordinator assesses disaster severity and activates response protocols. The resource allocator manages inventory of emergency supplies, vehicles, and personnel. The communications hub broadcasts public alerts and coordinates with agencies.

Install

clawhub install pilot-disaster-response-setup

Skills used

Agents

<your-prefix>-sensor-hub - Sensor Hub
Aggregates weather, seismic, and flood sensor feeds
Skills: pilot-stream-data, pilot-metrics, pilot-gossip
<your-prefix>-coordinator - Response Coordinator
Assesses severity, activates response protocols
Skills: pilot-task-router, pilot-consensus, pilot-audit-log
<your-prefix>-resource-allocator - Resource Allocator
Manages supplies, vehicles, personnel deployment
Skills: pilot-dataset, pilot-event-filter, pilot-escrow
<your-prefix>-comms - Communications Hub
Broadcasts alerts, coordinates with agencies
Skills: pilot-announce, pilot-slack-bridge, pilot-webhook-bridge

Data flows

<your-prefix>-sensor-hub → <your-prefix>-coordinator:1002 - disaster alerts with severity and geographic data
<your-prefix>-coordinator → <your-prefix>-resource-allocator:1002 - resource requests with priority and location
<your-prefix>-coordinator → <your-prefix>-comms:1002 - public alerts with severity and instructions
<your-prefix>-resource-allocator → <your-prefix>-comms:1002 - deployment status and resource availability

Quick start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)
# On sensor aggregation server
clawhub install pilot-stream-data pilot-metrics pilot-gossip
pilotctl set-hostname <your-prefix>-sensor-hub

# On coordination server
clawhub install pilot-task-router pilot-consensus pilot-audit-log
pilotctl set-hostname <your-prefix>-coordinator

# On resource management server
clawhub install pilot-dataset pilot-event-filter pilot-escrow
pilotctl set-hostname <your-prefix>-resource-allocator

# On communications server
clawhub install pilot-announce pilot-slack-bridge pilot-webhook-bridge
pilotctl set-hostname <your-prefix>-comms
# sensor-hub <-> coordinator (disaster alerts)
# On sensor-hub:
pilotctl handshake <your-prefix>-coordinator "setup: disaster-response"
# On coordinator:
pilotctl handshake <your-prefix>-sensor-hub "setup: disaster-response"

# coordinator <-> resource-allocator (resource requests)
# On coordinator:
pilotctl handshake <your-prefix>-resource-allocator "setup: disaster-response"
# On resource-allocator:
pilotctl handshake <your-prefix>-coordinator "setup: disaster-response"

# coordinator <-> comms (public alerts)
# On coordinator:
pilotctl handshake <your-prefix>-comms "setup: disaster-response"
# On comms:
pilotctl handshake <your-prefix>-coordinator "setup: disaster-response"

# resource-allocator <-> comms (deployment status)
# On resource-allocator:
pilotctl handshake <your-prefix>-comms "setup: disaster-response"
# On comms:
pilotctl handshake <your-prefix>-resource-allocator "setup: disaster-response"
pilotctl trust