Humanitarian Field Operations Knowledge Base Specification

Role: Principal Humanitarian Knowledge Management Specialist directing emergency response documentation.

Context

• Organization: {{ngo_name}}
• Operating theater: {{crisis_context}}
• Field personnel roles: {{field_user_profiles}}
• Network conditions: {{connectivity_constraints}}
• Data classification level: {{data_protection_classification}}
• Program sectors: {{operational_domains}}

Task

Produce a field-ready operational knowledge base specification that defines offline caching architectures, rapid-access standard operating procedure schemas, and secure data handling protocols for humanitarian aid teams.

Method

1. Map core SOPs across {{operational_domains}} into modular, lightweight knowledge units tailored for high-stress deployments.
2. Establish metadata profiles optimized for fast retrieval under {{connectivity_constraints}} with local SQLite and IndexedDB caching rules.
3. Classify operational content against {{data_protection_classification}} to isolate personally identifiable beneficiary data from field guides.
4. Design specialized content templates for rapid checklists, safety protocols, and emergency medical guidelines for {{field_user_profiles}}.
5. Define bi-directional synchronization and conflict resolution logic between forward operating bases and central repositories.
6. Formulate low-bandwidth media compression and progressive downloading standards.
7. Create emergency deprecation protocols to purge expired or compromised field directives immediately upon network reconnection.
8. Construct a field feedback capture framework allowing frontline workers to submit situational annotations.

Constraints

• MUST mandate zero-trust data segregation for all sensitive beneficiary and location records.
• MUST specify byte-budget constraints per knowledge article to ensure rapid loading on low-spec field hardware.
• MUST NOT require continuous internet access for critical life-safety procedures.
• Governance models must assign explicit local verification authorities in {{crisis_context}}.

Output format

Deliver a technical specification organized as follows:

1. System Context & Operational Architecture (under 200 words)
2. Content Taxonomy & Sectoral Schema (table covering {{operational_domains}})
3. Offline Synchronization & Caching Policy Specification
4. Field Article Templates (Checklist Schema, Critical Action Protocol, Context Dossier)
5. Data Privacy & Rapid Deprecation Controls

Self-review

1. Ensure offline-first constraints and caching mechanisms are technically explicit.
2. Verify humanitarian protection principles align with {{data_protection_classification}}.
3. Check that field user roles in {{field_user_profiles}} have tailored view schemas.