Pipeline

Clerk, then the board

The duty clerk reads every public report, ranks it, and points the nearest desk. Officers do not chat with a model. Each step still leaves a log line you can watch from Messages to Needs to Teams.

1. 01

   Intake

   A free-text location and a need become a structured event. Optional name is stored with the ticket, not required.

2. 02

   Verification

   Conflicting reports on the same patch are tagged so officers are not sent twice for one rooftop.

3. 03

   Prioritisation

   The clerk sets severity and score. Life-safety beats blankets. Heuristics fill in only if the clerk is offline.

4. 04

   Routing

   Nearest approved government, NGO, or volunteer from their registered area. Take initiative claims the ticket; everyone else sees the name.

5. 05

   Summary

   A sitrep compiles what is still open, what moved, and what knock-on hazards remain.