{"resourceId":"nashville-metro-ai-use-registry-20260909","versions":[{"version":"external-decd571e4ee9ac09efd0f0bf02c19eda9015af1010efda13b18f545fa8f554a6","resource":{"id":"nashville-metro-ai-use-registry-20260909","title":"Metro Nashville publishes public AI Use Registry accurate as of Sept. 9, 2026","organization":"Metropolitan Government of Nashville and Davidson County (Metro ITS)","sector":"County/metro transparency registry for municipal AI systems","geography":"Nashville/Davidson County, Tennessee, United States","publishedAt":"Metro AI Use Registry page stating inventory accurate as of 9/9/2026","publicationDate":"2026-09-09","eventDate":"2026-09-09","sourceName":"Nashville.gov (Metro ITS)","sourceLabel":"Public government AI system inventory with purpose, oversight, and status fields","sourceUrl":"https://www.nashville.gov/departments/information-technology-services/information-security/artificial-intelligence/metro-ai-use-registry","evidenceClass":"standards-guidance","outcomeClass":"emerging","topics":["governance-procurement","operating-model","data-security","accessibility-workforce"],"finding":"Metro Nashville's public Artificial Intelligence (AI) Use Registry states the inventory is accurate as of 9/9/2026 and will grow as systems are added. Entries describe purpose, department, vendor/platform, AI technology type, decision role, human oversight, and status. Examples spanning local-government services include Adobe AI and Microsoft Copilot (enterprise active, advisory/human-in-loop), Granicus Government Experience Agent Meetings Agent pilot answering public meeting/legislation questions from Legistar with source links and staff monitoring, Archistar AI PreCheck planned/evaluation for Codes building-permit completeness and zoning/building-code pre-checks with humans retaining final authority, CYVL pavement/ROW asset intelligence planned/pilot, and DocAccess accessibility remediation planned/pilot. Many entries explicitly label Decision Role as Advisory (Human in Loop) and Human Oversight as Staff Review Required. Why now: a living U.S. metro inventory dated nine days before this edition date models the transparency control Fort Worth's audit says is hard—and that chatbot procurements (e.g., Grand Rapids RFP due 9/24) should emulate.","sledRelevance":"Concrete U.S. local-government public AI registry covering permitting pre-check, legislative chat, accessibility, and staff copilots with explicit human-in-loop labels.","evidence":"Nashville.gov registry: accurate as of 9/9/2026; fields for purpose/department/oversight/status; Archistar permit PreCheck planned with human final authority; Granicus GXA Meetings Agent pilot with source links; Copilot/Adobe active advisory; multiple Staff Review Required labels.","architectureImplications":"Interpretation: Registry is metadata about heterogeneous systems (RAG chat, computer vision, copilots)—not a single platform—so integration patterns stay use-case-specific.","governanceImplications":"Interpretation: Publishing decision-role and oversight fields forces departments to declare whether AI is advisory; inventories must be dated and updated.","securityPrivacyImplications":"Interpretation: Entries that ban scoring/surveillance uses (e.g., Meltwater limits) show registry text can encode prohibited purposes alongside allowed ones.","caveats":"Registry is Metro self-description; statuses include planned/pilot/active without measured outcome metrics; some public-safety tools appear in the inventory but are not the focus of this local-government edition's analysis; accuracy date is 9/9/2026, not a same-day update.","streamIds":["local-government"],"roles":{"sales":"Metros buying chatbots or permit AI need a public inventory story as much as a demo. Nashville's dated registry shows how to list Archistar-style permit PreCheck and Granicus meeting agents with human-in-loop labels. Sell registry design and intake workflows; do not claim Nashville proved those tools' accuracy. Unsupported: that a registry alone prevents harm or that planned status equals production success.","engineering":"Fit is a living catalog with mandatory fields (purpose, decision role, oversight, status) feeding procurement gates. Architecture: form/CMS → review → publish; link each system to data classes and owners. Prerequisites: department inventory campaign, taxonomy, and update SLA. Constraints: self-attested statuses; mixed planned vs active; no embedded accuracy metrics.","delivery":"Run a registry sprint: collect entries, normalize oversight labels, publish with an as-of date, and require updates before go-live. Ownership: Metro ITS hosts; departments own entry truth. Acceptance: every resident-facing or permitting AI listed before production. Risks: stale entries and security-through-documentation theater."},"roleDetails":{"sales":{"customerProblem":"AI tools proliferate across departments without a public, dated inventory councils can trust.","stakeholders":["CIO/CISO","Codes/permitting","Clerk/Council office","311/digital services","Privacy/legal"],"discoveryQuestions":["What is the registry as-of date?","Are decision-role and oversight mandatory fields?","Must new chatbots be listed before launch?","Who verifies entry accuracy?"],"valueHypothesis":"A public dated registry plus human-in-loop labels improves accountability for permitting and resident AI buys.","potentialEngagement":"Registry schema, first inventory load, and pre-launch listing gate for chatbot/permit AI—not a model vendor bake-off.","unsupportedClaims":["Registry proves tool accuracy","Planned Archistar equals measured permit speedups","Human-in-loop labels guarantee review quality","All Metro AI is listed exhaustively"]},"engineering":{"fit":"Public AI system registry with oversight taxonomy across chat, CV, and copilots.","architectureIntegration":"Department submits entry → ITS/security review → publish HTML/API → update on status change.","prerequisites":["Field taxonomy","Department responders","As-of dating","Change process tied to procurement"],"constraints":["Self-attestation","No outcome metrics in entries","Mixed sensitivity of listed systems","Update lag risk"],"security":"Avoid publishing sensitive model/data details; still require internal risk reviews before public summary.","proofOfValue":["Percent of AI projects listed pre-production","Median update latency","Field completeness","Public as-of freshness"]},"delivery":{"work":"Inventory campaign, editorial review of entries, publish with 9/9-style as-of stamp, and gate go-lives on listing.","dependencies":["Metro ITS","Codes (Archistar)","Clerk/Council (Granicus)","Department AI owners"],"ownership":"ITS maintains the registry platform; departments own entry accuracy; security owns prohibited-use language.","skillsAdoption":"Train program managers to fill decision-role/oversight fields honestly.","governanceCheckpoints":["Pre-launch listing","Quarterly as-of refresh","Spot audits of active entries","Retirement of decommissioned systems"],"acceptanceCriteria":["As-of date displayed","Human oversight field populated","Permit/resident bots listed before production","Change log or refresh cadence documented"],"risks":["Stale registry","Rubber-stamp human-in-loop","Omitting shadow tools","Public confusion of planned vs active"]}},"retrievedAt":"2026-09-25T03:23:44Z","enrichedAt":"2026-09-25T03:23:44Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Interpretation: DocAccess-style AI accessibility tooling appearing in the registry shows workforce and ADA remediation as first-class AI use cases.","procurementImplications":"Interpretation: Require registry listing and oversight fields in chatbot/permit AI contracts before notice-to-proceed.","operatingModelImplications":"Interpretation: ITS-hosted registry with department-owned truth creates a clear RACI for sprawling AI portfolios.","sourceVerification":{"openedUrl":"https://www.nashville.gov/departments/information-technology-services/information-security/artificial-intelligence/metro-ai-use-registry","referenceExcerpt":"this inventory is accurate as of 9/9/2026.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}