Population Flow pulse
Aggregated zone-level activity, heat severity, and pressure signals from the Population Flow layer.
Signals in
Four families of inputs feed the coordination layer at all times.
Resource Nodes inventory
Live status of every cooling center, hydration station, shelter, and mobile unit in the network.
Alerts & advisories
NWS excessive heat warnings, air-quality alerts, transit disruptions, and partner-flagged incidents.
Operator field reports
Free-text dispatches from field teams, intake updates from shelters, and partner-system event streams.
How a recommendation is made
Five stages from raw signal to operator decision. Every stage is logged with its inputs and outputs.
Ingest
Every signal source is normalized to a common schema and scored for freshness and confidence the moment it arrives.
Score
A heat-response model fuses signal severity, vulnerability, and resource-gap factors into a priority score per zone.
Recommend
For each high-priority zone the layer drafts a recommendation: which resource to move, when, and why, citing the underlying signals.
Hand to operator
Recommendations queue into the operator interface with full provenance. A human approves, declines, or edits, every time, no exceptions.
Close the loop
Operator decisions and field outcomes feed back into the scoring model so the next recommendation is better than the last.
Guardrails
The constraints we apply before anything reaches a partner or a resident.
Privacy is inherited, not added
The coordination layer reads from Population Flow, which only sees aggregated signals. There are no individual location trails, device IDs, or movement records anywhere in the stack.
Show your work
Each recommendation is paired with the signals that produced it and the alternatives the model considered. Operators see the reasoning, not just the answer.
It can say "I don't know"
When the signal stack is thin or contradictory, the layer falls back to a published, lower-confidence playbook. We would rather flag uncertainty than invent a confident answer.
A person makes the call
Nothing clinical, dispatch-related, or safety-critical happens automatically. The layer drafts. A named operator decides. Both the draft and the decision are logged.
What the layer coordinates
Four operational surfaces the coordination layer keeps in sync across partners.
Resource dispatch
Mobile units, water deliveries, and outreach teams routed against the live priority picture instead of yesterday’s plan.
Shelter capacity
Real-time view of overnight intake, queue length, and supply levels so partners can flex before a site is overwhelmed.
Resident escalation
Concierge conversations that detect a clinical or safety signal trigger a warm hand-off to a named human responder.
Cross-partner briefings
A single live ops view assembled for mayors, hospital ops chiefs, and community-org directors, not a stack of agency PDFs.
Want the coordination layer live in your city?
Pilot conversations start with one 45-minute call.
Cities, healthcare systems, and community organizations welcome. We start with your existing signals and grow from there.