Resilience and community
Summary¶
The resilience-community domain covers libdrone's role as civilian preparedness infrastructure. It addresses the information gap that drives poor decisions in crisis scenarios, documents fifteen operational use cases from everyday training through active emergency response, and defines what a community group needs to deploy libdrone as a genuine preparedness asset. The core argument: a drone flown 50 times before any crisis with spare parts on the shelf is preparedness; a drone in a box is not.
Concept¶
Reference¶
Articles in this domain¶
| Article | Content |
|---|---|
| civilian-preparedness | Information gap, individual/neighbourhood/security impact, why libdrone |
| resilience-use-cases | 15 use cases UC-01 through UC-15, sensor thresholds, payload-mission matrix |
| community-deployment | Three roles, equipment list, skills maintenance schedule, standing up from scratch |
Procedure¶
Rationale¶
Why resilience is a corpus domain alongside technical domains¶
Institutional procurement decisions for libdrone are made by civil preparedness groups and municipal emergency management — not by drone engineers. The resilience-community domain provides the non-technical case directly from the corpus, accessible to the evaluator persona without requiring them to navigate technical domains first.
Connections¶
requires: [] related: - civilian-preparedness - resilience-use-cases - community-deployment leads_to: - civilian-preparedness