Facts have sources.
Requests must be marked verified before they affect an operational plan.
LIFELINE
OPEN HUMANITARIAN COORDINATION
Coordinate what matters.
A human-approved incident room that turns verified reports, available resources, open routes, and shelter capacity into an inspectable response proposal.
Illustrative flood scenario — not a live emergency service.
Enter LIFELINE.
Three ways in — pick one below.
01 / SYNTHETIC DEMO
Incident room
Sealed synthetic scenario. Approve/reject actions run locally in your browser — no dispatch.
Open the demo room → 02 / YOUR EXPORTMy exported room
Inspect a plan produced by the deterministic kernel from your own local export.
Open my exported room → 03 / LOCAL SERVERLocal operations
Console for the loopback LIFELINE server: create incidents, append reports, compute sealed plans.
Open local operations →The map is not the decision.
LIFELINE makes operational facts and constraints visible. The planner proposes only feasible combinations; a coordinator must verify and approve every action.
●Family · urgent
✚Boat 02
✚Ambulance 01
⌂Shelter A · 12 beds
×Route closed
Solid line: viable route · red dash: unavailable route
Humanity before automation.
The first release deliberately keeps authority narrow. It records facts and constraints, creates a reproducible proposal, and tells a human where it cannot proceed.
Feasible is explicit.
Capacity, route status, availability, and medical compatibility are hard constraints, not model guesses.
People stay accountable.
Every proposed action awaits an authorized human approval and produces an audit record.