A Zero-Hardware, 4-Layer Agentic Disaster Triage Cockpit for Philippine LGUs.
EdgeResQ is a monorepo for a disaster response platform designed to support citizen intake, edge-assisted verification, and LGU triage operations.
It combines two prototype surfaces:
- Mobile client for citizen reporting, offline capture, and sensor-assisted checks
- Web dashboard for LGU triage, verification, mapping, and incident management
The goal is to keep shared schemas, backend logic, and documentation in one place so both prototypes can evolve together.
Developed by Team Shareen Bola for SparkFest 2026.
EdgeResQ fuses multiple layers of data — phone accelerometer and IoT sensor input, authoritative government and satellite feeds (e.g. PHIVOLCS, NASA FIRMS, Meta Data for Good), AI-structured multilingual incident reports (Tagalog/Bisaya via Gemini), and an SMS fallback for off-grid areas — into a single live triage cockpit for LGUs. Each incoming report is scored with an Algorithmic Trust Score (Ts) that automatically flips markers from "Pending" to "Verified" on a real-time map, helping responders prioritize where to act first during a disaster.
EdgeResQ is organized around a software-first disaster response flow:
- Citizen intake via the mobile app
- Validation and verification through backend services
- Incident triage in the web dashboard
- Documentation and coordination across the full repository
Team Name: Bola
Members:
- Arnaez, Anjelo Benedict
- Balocating, Aaliyah Marie
- Bomediano, John David
- Maligaya, Gian Brent
- Gemini API — structures multilingual (Tagalog/Bisaya) incident reports and powers AI-assisted triage
- Firebase — real-time data sync and backend infrastructure
EdgeResQ/
├── .github/
├── backend/
├── docs/
├── infra/
├── packages/
├── web/
├── .gitignore
├── bun.lock
├── CONTRIBUTING.md
├── package.json
└── README.md
This project is planned and developed during Sparkfest 2026: GDG PUP Hackathon
Android client for the citizen intake flow, offline queueing, and fallback messaging.
LGU dashboard for incident mapping, verification, triage, and operational review.
Shared API and ingestion layer for validation, routing, and event processing.
Shared schemas, types, and utilities used across mobile, web, and backend.
Architecture notes, demo flow, and project documentation.
Deployment helpers, Firebase setup, and environment configuration.
Please read CONTRIBUTING.md before opening pull requests or making changes.
For local development instructions, required software, environment variables, and backend startup notes, see docs/dev-setup.md.
Contributors should use .github/pull_request_template.md when opening pull requests so each PR includes a summary, checklist, and notes.