Municipal 311 Citizen Triage Multi-Agent Routing Benchmark Suite

Role: Chief Civic Technology Evaluator specializing in multi-agent routing systems and emergency dispatch workflows.

Context

• Municipal Jurisdiction: {{municipality_jurisdiction}}
• Evaluation Corpus: {{citizen_inquiry_dataset}}
• Department Directory: {{department_routing_targets}}
• Safety & Escalation Protocols: {{escalation_safety_rules}}
• Performance SLA: {{latency_sla_ms}}
• Framework Engine: {{benchmark_framework}}

Task

Construct an automated multi-agent triage evaluation script that stress-tests civic routing accuracy, emergency escalation safety, and latency performance across {{municipality_jurisdiction}} citizen support pipelines.

Method

1. Load and parse the {{citizen_inquiry_dataset}} into categorized synthetic citizen interaction scenarios.
2. Define expected routing topology based on {{department_routing_targets}}.
3. Construct asynchronous concurrent evaluation workers utilizing {{benchmark_framework}}.
4. Implement critical path safety assertion checks derived from {{escalation_safety_rules}} for emergency triggers.
5. Measure and record per-request round-trip latency, evaluating against {{latency_sla_ms}}.
6. Compute confusion matrices and routing precision/recall scores across municipal service boundaries.
7. Generate an automated markdown evaluation scorecard detailing routing bottlenecks and safety violations.

Constraints

• MUST abort execution or flag a critical failure if any emergency trigger in {{escalation_safety_rules}} is misrouted.
• MUST NOT allow average latency to pass if it exceeds {{latency_sla_ms}}.
• Script must be fully asynchronous to simulate real-world municipal load conditions.
• Use clean error handling for resilient execution during edge-case ingestion.

Output format

Provide a comprehensive {{benchmark_framework}} benchmark script structured as:

1. Initialization and Async Client Configuration.
2. Dataset Ingestion and Emergency Scenario Fixtures.
3. Routing Precision and Safety Protocol Evaluator Engine.
4. Concurrent Execution Runner and Markdown Scorecard Generator.

Self-review

1. Ensure emergency escalation rules from {{escalation_safety_rules}} are prioritized over general routing.
2. Validate that latency tracking accurately captures p95 and p99 against {{latency_sla_ms}}.
3. Verify that the async worker pool scales cleanly across {{citizen_inquiry_dataset}}.