in reviewhumanPR #134Coordination
feat: TownOps triage scenario with multi-agent coordination
Adds a complete town operations triage scenario for the NANDA Town hackathon.
Description
The pitch.
## Town Operations Triage Plugin Adds a complete town operations triage scenario for the NANDA Town hackathon. ### Files Added - \`scenarios/town_ops.yaml\` — Multi-agent town operations triage scenario with 6 specialized agents (triage, dispatcher, resident, resolver, coordinator) - \`templates/agents/townops-triage-agent.yaml\` — Triage agent template for classifying citizen-reported issues - \`templates/agents/townops-resident-agent.yaml\` — Resident-facing agent for plain-language status updates - \`docs/townops-plugin.md\` — Comprehensive documentation with architecture, API integration, and testing guide ### Integration - Works with [TownOps Skill](https://github.com/Rohan5commit/townops-skill) — a deployed agent-usable town operations triage API - Live demo: https://townops-skill.vercel.app - API Inspector: https://townops-skill.vercel.app/api-inspector - SKILL.md: https://townops-skill.vercel.app/skill-viewer ### Scenario Details - **Tier 2** (LLM-powered agents) - **6 agents**: triage-agent, 2x zone-dispatcher, resident-agent, resolver-agent, coordinator - **8 issue types**: Pothole, Streetlight Outage, Tree Hazard, Water Leak, Noise Complaint, Road Closure, Garbage Collection, Graffiti - **5 zones**: Downtown, Residential North/South, Commercial East, Industrial West - **SLA tracking**: Critical (2h), High (12h), Medium (48h), Low (168h) - **5% message drop** for resilience testing ### Judging Dimensions - **Correctness**: Pipeline triages → dispatches → resolves → notifies citizens - **Test Rigor**: Deterministic seed, SLA compliance metrics, trace output - **API Fit**: Uses standard NANDA layers (transport, comms, identity, registry, auth, trust, payments, coordination, negotiation, memory, privacy, datafacts) - **Docs**: Full architecture docs, API reference, integration guide - **Novelty**: Real-world municipal operations use case with severity-based SLA escalation - **Persona Fidelity**: Each agent has clear role boundaries and communication protocols
Try it
Open PR on GitHubView diffCheckout locally
git fetch origin pull/134/head:pr-134
git checkout pr-134