Municipal Public Works Service Request Routing Specification

Role: Smart City Product Strategist and Municipal Systems Solutions Architect.

Context

• Participating departments: {{municipal_department_scope}}
• Incident taxonomy: {{incident_category_taxonomy}}
• Spatial logic: {{gis_routing_rules}}
• Performance baselines: {{sla_escalation_thresholds}}
• Transparency mandates: {{open_data_disclosure_rules}}
• Communication pathways: {{resident_notification_channels}}

Task

Author an end-to-end product functional specification for an automated municipal incident triage, spatial dispatching, and public-facing transparency module.

Method

1. Establish the validation rules for citizen reports based on {{incident_category_taxonomy}}.
2. Translate {{gis_routing_rules}} into spatial lookup and departmental dispatch logic.
3. Define automated routing matrices directing tickets across {{municipal_department_scope}}.
4. Design the lifecycle state machine including automated reminders based on {{sla_escalation_thresholds}}.
5. Specify outbound milestone messaging triggers across {{resident_notification_channels}}.
6. Detail automated redaction pipelines filtering PII before publishing to {{open_data_disclosure_rules}}.
7. Construct duplicate report detection algorithms utilizing reverse-geocoding and proximity thresholds.

Constraints

• MUST automatically redact citizen personal identifying information prior to syndication to {{open_data_disclosure_rules}}.
• MUST NOT route tickets without validated spatial coordinates or confirmed street addresses.
• SLA clocks must pause strictly during approved external dependency states.
• All status transitions must generate immutable, auditable log entries.

Output format

1. System Context & Departmental Taxonomy (Scope, boundaries, classifications)
2. Intake & Geocoding Logic (Coordinate validation, duplicate detection specs)
3. Triage & Departmental Dispatch Engine (Table: Taxonomy, Routing Rule, {{sla_escalation_thresholds}} Matrix)
4. Resident Engagement Lifecycle (State diagram & copy triggers for {{resident_notification_channels}})
5. Public Data Syndication Schema (JSON schema matching {{open_data_disclosure_rules}})

Self-review

• Confirm duplicate detection logic handles multiple reports for the same incident at one location.
• Verify all escalation pathways enforce {{sla_escalation_thresholds}} across all {{municipal_department_scope}}.
• Check that PII filtering thoroughly satisfies {{open_data_disclosure_rules}}.