Humanitarian Aid Field Verification and Telemetry Specification
Draft a technical product specification for low-connectivity mobile data capture and donor impact reporting in disaster relief.
Apply this template when defining product features for field aid workers operating in austere network environments. It ensures accurate humanitarian metric tracking while maintaining strict beneficiary privacy and donor transparency standards.
Role: Technical Product Lead for international humanitarian relief software and offline-first telemetry.
Context
- Operational environment: {{humanitarian_mission_scope}}
- Network realities: {{field_connectivity_profile}}
- Mandated metrics: {{donor_reporting_kpis}}
- Privacy governance: {{beneficiary_data_protection_standard}}
- Client hardware: {{hardware_target_devices}}
- Data reconciliation rule: {{sync_conflict_resolution_protocol}}
Task
Generate a functional system specification for a mobile telemetry and inventory verification module that allows field operatives to log aid delivery in disconnected environments while ensuring tamper-proof audit trails for donors.
Method
- Evaluate {{hardware_target_devices}} to define local SQLite storage footprints and battery-conservative sync loops.
- Detail the offline data capture flow tailored to {{humanitarian_mission_scope}} conditions.
- Formulate cryptographic hashing and local encryption mechanisms matching {{beneficiary_data_protection_standard}}.
- Design the synchronization pipeline accommodating {{field_connectivity_profile}}.
- Operationalize {{sync_conflict_resolution_protocol}} into explicit client-server merge states.
- Structure aggregation pipelines that auto-calculate {{donor_reporting_kpis}} upon central ingestion.
- Define emergency data-wipe procedures triggered by tampering or geo-fencing perimeter breaches.
Constraints
- MUST guarantee zero data loss during sudden network disconnections.
- MUST NOT store unencrypted personally identifiable beneficiary information on {{hardware_target_devices}}.
- Sync payloads must be compressed to execute over low-bandwidth satellite links under 50 kbps.
- User interface must support one-handed, high-contrast outdoor usage.
Output format
- Section 1: Operational Scope & Technical Parameters (max 200 words)
- Section 2: Offline Architecture & Data Schemas (Database entities, field validation rules)
- Section 3: Sync & Conflict Resolution Engine (Step-by-step state machine based on {{sync_conflict_resolution_protocol}})
- Section 4: Privacy & Field Security Protocols (Protocols aligned with {{beneficiary_data_protection_standard}})
- Section 5: KPI Aggregation & Telemetry Reporting Pipeline (Mapping to {{donor_reporting_kpis}})
Self-review
- Ensure the sync conflict logic covers simultaneous updates across multiple field devices.
- Verify all security rules adhere to {{beneficiary_data_protection_standard}}.
- Confirm the payload specifications operate within {{field_connectivity_profile}}.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.