{"resourceId":"savannah-ai-framework-proposal-20260908","versions":[{"version":"external-3866bc7e50b4fc1ecb4a8dd537e9f0bef6c81163475ca4ae8a4567519b70794b","resource":{"id":"savannah-ai-framework-proposal-20260908","title":"Savannah alderman proposes public AI inventory and human-appeal rules after data-leak concerns","organization":"City of Savannah","sector":"Municipal governance, procurement and data protection","geography":"Savannah, Georgia, United States","publishedAt":"September 8, 2026 WTOC report","publicationDate":"2026-09-08","eventDate":null,"sourceName":"WTOC","sourceLabel":"Independent local television reporting of alderman proposal and mayor response","sourceUrl":"https://www.wtoc.com/2026/09/08/savannah-alderman-pushes-ai-framework-city-government-after-data-leaks-healthcare-information/","evidenceClass":"independent-reporting","outcomeClass":"emerging","topics":["governance-procurement","data-security","operating-model","accessibility-workforce"],"finding":"Savannah Alderman Nick Palumbo proposes a four-pillar AI framework—public system inventory, human sign-off/appeal for consequential decisions, ban on vendor training on city data, and procurement-time privacy/bias review—after describing unconstrained departmental generative AI use; Mayor Van Johnson agrees policy must be codified.","sledRelevance":"Illustrates smaller-city implementation capacity: political push for accountability after trust shocks, drawing on peer city examples (Seattle, Lebanon NH) via NLC networks before ordinance text exists.","evidence":"Quotes describe Microsoft licensing without departmental limits; pillars listed from alderman’s public post; workshop with council planned; cybersecurity CEO warns about unsupervised autonomous use. Leak anecdote motivates urgency but is not a completed AI forensics finding in the piece.","architectureImplications":"Would require a maintained public register of AI systems by department and procurement gates that constrain data flows to vendors/models.","governanceImplications":"Moves from ad hoc departmental AI to inventory, human-in-the-loop for rights-affecting decisions and procurement review—still proposal-stage.","securityPrivacyImplications":"Explicit focus on preventing vendor training on city/resident data and reducing leak impact through selective data use.","caveats":"Not enacted; enforcement funding and technical inventory method unspecified; personal leak narrative is incomplete as AI causal evidence.","streamIds":["local-government"],"roles":{"sales":"Interpretation: Mid-size cities after trust incidents need discovery on whether any AI inventory or procurement AI clauses exist today. Engage council sponsors, CIO/IT, procurement, legal and department directors using Microsoft/OpenAI tools. Ask who can list every AI system and what happens on consequential automated sorting. A bounded engagement can draft an inventory schema and procurement questionnaire before ordinance fights. Value is controllable adoption and resident appeal rights—not a freeze on all AI. Do not sell guaranteed breach prevention.","engineering":"Interpretation: Fit is policy and register infrastructure more than a model. Integrate an AI-use registry with procurement and identity/access processes. Prerequisites: department attestations, vendor data-use clauses and human-review workflows for permits/property/routing decisions. Constraints: proposal-only; Microsoft sprawl already present. Security centers on training-data bans and least-data prompts. Proof of value is a complete public inventory and tested appeal path—not tool count reductions alone.","delivery":"Interpretation: Delivery starts with a council workshop, then registry build and procurement checklist pilots. Dependencies include IT asset owners, procurement officers and legal. Ownership: council for policy; CIO for registry; departments for attestations. Train staff that consequential outputs need human sign-off. Governance checkpoints at workshop, draft ordinance and first procurement using the checklist. Acceptance: public list exists; appeal path documented. Risks include symbolic policy without inventory hygiene and chilling beneficial low-risk uses."},"roleDetails":{"sales":{"customerProblem":"Departments use generative AI under enterprise licenses without a public inventory, data-use limits or resident appeal path.","stakeholders":["City council / aldermen","Mayor","CIO/IT","Procurement","Department directors","Residents"],"discoveryQuestions":["Can anyone list every AI system in use today?","Which decisions lack human appeal?","What do vendor contracts say about training on city data?","What is the workshop-to-ordinance timeline?"],"valueHypothesis":"Inventory-plus-procurement gates can reduce unmanaged AI risk while allowing reviewed productivity uses.","potentialEngagement":"Facilitated council workshop producing a draft AI register schema and procurement bias/privacy questions.","unsupportedClaims":["Framework prevents all future leaks","Proposal equals enacted law","Peer-city pillars transfer without local legal review"]},"engineering":{"fit":"Public AI-use registry and procurement control points; optional technical monitoring later.","architectureIntegration":"Tie registry to department ownership, SaaS inventory and identity; enforce contractual non-training clauses in vendor configs where possible.","prerequisites":["Department AI attestations","Procurement questionnaire","Human-review workflow design"],"constraints":["Policy not yet adopted","Existing Microsoft/generative sprawl","Limited forensic detail on cited leak"],"security":"Minimize data in prompts; prohibit vendor training on city data; document retention for AI outputs in records systems.","proofOfValue":["Complete public inventory v1","Procurement reviews completed on new buys","Documented human-appeal path for named decision types"]},"delivery":{"work":"Run council workshop, stand up registry MVP and pilot procurement AI review on upcoming purchases.","dependencies":["Legal drafting","IT asset/SaaS inventory","Procurement staff","Department liaisons"],"ownership":"Council sponsors policy; CIO operates registry; procurement enforces pre-award review.","skillsAdoption":"Train departments to declare tools and route consequential AI-assisted decisions to humans.","governanceCheckpoints":["Workshop outcomes","Draft ordinance/policy","First quarterly inventory refresh"],"acceptanceCriteria":["Public list live","Human appeal documented for permits/property/routing examples","Vendor training ban in standard clauses"],"risks":["Workshop without follow-through","Incomplete attestations","Over-broad bans blocking low-risk tools"]}},"retrievedAt":"2026-09-18T03:06:50Z","enrichedAt":"2026-09-18T03:06:50Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Human-appeal requirements protect residents who cannot or will not use AI channels; staff need clear escalation skills when AI sorts permits or requests.","procurementImplications":"Shifts AI diligence to pre-award privacy/bias questions and contractual limits on training/resale of city data.","operatingModelImplications":"Moves from unmanaged departmental experimentation to attested inventory and council-visible governance—capacity must match ambition.","sourceVerification":{"openedUrl":"https://www.wtoc.com/2026/09/08/savannah-alderman-pushes-ai-framework-city-government-after-data-leaks-healthcare-information/","referenceExcerpt":"It’s the Wild West, it’s anything goes, any platform or generative AI usage they want","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}