A single, prioritized source for emergencies, road impacts, interruptions and important public notices.
The reference implementation never fabricates current incidents. Production items require an authorized source, severity, start time and expiry.
Ask a common municipal question. This demonstration does not call an external AI model or collect personal information.
| Requirement | Implementation | Status |
|---|---|---|
| Open-source CMS | Drupal 11 structured municipal content | Implemented |
| WCAG | 2.2 AA target, keyboard/focus/reduced-motion patterns | QA target |
| Search | Pages + source-grounded search/finder; document full-text architecture | Reference implementation |
| Emergency communications | Status centre + low-decoration emergency route + severity architecture | Demonstrated |
| Forms/e-services | Shared guided form system; permit and report-problem journeys | Demonstrated |
| Content governance | Roles, moderation, ownership and review metadata | Implemented |
| Canadian residency | Canadian production architecture required; current demo not claimed compliant | Production gate |
Final vendors, regions, service availability and data paths are verified with the Town before any production residency claim.
| System | Demo state | Production intent |
|---|---|---|
| Microsoft Entra ID | Not connected | SAML 2.0 staff SSO |
| Dayforce | Not connected | Careers/recruitment integration |
| Intelli | Not connected | Town-approved integration |
| SylogistGov | Not connected | Town-approved integration |
| Citywide | Interaction concept only | Report-a-problem/service request hand-off |
| SharePoint / Power Automate | Not connected | Internal workflow integration where approved |
