CivicOps judge tour
Follow this route from Band dispatch to intake, AI action, ticket tracking, control room, alerts, Citizen App and connector readiness.
Begin with Band Dispatch/Home/Report
What to click: Submit the app-first report form or review its fields.
What should happen: A reference number, citizen response, routing and status link.
Why it matters: Proves web/PWA reporting works without WhatsApp.
/citizen-app
What to click: Open the phone-like app tiles.
What should happen: Report, track, alerts, weather and resident profile paths.
Why it matters: Shows the main citizen channel.
/Home/Agent
What to click: Run each action button once.
What should happen: Validation, department, priority, citizen response, alert recommendation and audit trail.
Why it matters: Shows Gemini/fallback intelligence is event-triggered and quota-safe.
/Home/Dashboard
What to click: Review stats, queues and high-priority reports.
What should happen: A civic operations view for staff review.
Why it matters: Shows routing has operational value.
/Home/Lookup
What to click: Enter a reference from a submitted ticket.
What should happen: Status, department, timeline and latest update.
Why it matters: Residents can self-serve status without calling staff.
/Home/Alerts
What to click: Review alert cards, then open weather context.
What should happen: Area, ward, severity and sandbox weather signals.
Why it matters: Connects individual reports to public resilience messaging.
/Home/Connectors
What to click: Review Gemini diagnostics and connector order.
What should happen: Enabled/key-present/model/cooldown/fallback status without secrets.
Why it matters: Demonstrates honest integration posture.