{"resourceId":"main-ai-policy-template-software-clause-20260926","versions":[{"version":"external-5b820f740d056ea3282d1a0e7fa93f088d4227c892fcb28efd6e8469c68c23a9","resource":{"id":"main-ai-policy-template-software-clause-20260926","title":"Mississippi MAIN local-government AI policy template adds Sept. 26 software-created-with-AI governance clause","organization":"Mississippi Artificial Intelligence Network (MAIN) / Mississippi Gulf Coast Community College","sector":"Smaller local-government AI policy / capacity templates","geography":"Mississippi, USA (template for cities, counties, and other local governments)","publishedAt":"June 3, 2026 (page); MAIN editorial recommendation added September 26, 2026","publicationDate":"2026-06-03","eventDate":"2026-09-26","sourceName":"Mississippi Artificial Intelligence Network (MAIN)","sourceLabel":"Public-sector association / practitioner template","sourceUrl":"https://mainms.org/ai-policy-and-guidance-template-local-government/","evidenceClass":"public-sector-association","outcomeClass":"emerging","topics":["governance-procurement","operating-model","data-security","accessibility-workforce"],"finding":"MAIN’s AI Policy and Guidance Template for Local Government (published June 3, 2026) gives Mississippi cities and counties a proportionate framework covering acceptable use, public records, procurement, public safety, high-risk human oversight, resident-facing disclosure, and accessibility. Sample language states AI must not make final decisions affecting permits, code enforcement, benefits, utility billing or shutoffs, employment, public safety, or legal rights without authorized human review. Why-now: on Sept. 26, 2026 MAIN added an editorial recommendation that software, scripts, websites, integrations, low-code workflows, and agents created with AI—including software with no AI at runtime—must follow organization software/data/change-control rules; permission to use a coding tool does not authorize deployment.","sledRelevance":"Directly addresses smaller-government implementation capacity: a lean-staff template plus a fresh Sept. 26 clause on AI-generated software deployment—the gap beside this week’s city AI policies and chatbot launches.","evidence":"Opened MAIN template page; June 3 publication stamp and Sept. 26 editorial recommendation verified in page text. Template is explicitly not legal advice or a mandatory model.","architectureImplications":"Separates exploratory local/self-hosted model use from production; requires review before AI-built code hits shared deployment, privileged access, or resident-facing services.","governanceImplications":"Governing-body adoption, named staff owner, inventory of approved tools, and human oversight for high-risk decisions; Sept. 26 clause extends governance to AI-authored software change control.","securityPrivacyImplications":"Bans entering restricted/confidential/regulated data into unapproved AI; CJIS caution for public safety; public-records treatment of prompts/outputs; vendor training-rights scrutiny in procurement.","caveats":"Template/guidance, not an adopted ordinance; Mississippi-centric references (ITS, Public Records Act); no measured outcomes from adopting jurisdictions in the page itself; Sept. 26 clause is editorial recommendation with NIST SSDF foundation, not a legal mandate.","streamIds":["local-government"],"roles":{"sales":"Lean cities and counties need AI policy that fits a clerk-plus-attorney shop—not a 200-page program. MAIN’s June template (Sept. 26 update) gives sample rules that AI must not finalize permits, benefits, utility shutoffs, or public-safety actions, and newly stresses that AI-written scripts and agents still need change-control before deployment. Pitch a bounded policy adaptation and sanctioned-tool list; do not sell the template as legal advice or as proof of AI ROI.","engineering":"Fit is a governance and change-control framework for small jurisdictions using assistive AI and AI-aided coding. Prerequisites: governing-body adoption path, staff AI owner, approved-tool inventory, and review gates before resident-facing or privileged deployments. Constraints: limited IT; contracted vendors; Mississippi-specific statutes need local counsel remap elsewhere. Prove value with adopted policy, inventory completeness, and zero unreviewed AI-built production pushes in a sample month.","delivery":"Delivery is adapt-adopt-train: tailor the MAIN template with counsel, pass a local resolution, publish approved and prohibited uses, train staff, and add the Sept. 26 software-created-with-AI review step into existing change control before any automation goes live. Dependencies: attorney, clerk, IT or IT vendor, and department heads. Ownership: administrator-designated AI owner. Skills: staff who treat AI output as draft only. Risks: slogan principles without owners; shadow ChatGPT; deploying AI-built automations without review."},"roleDetails":{"sales":{"customerProblem":"Staff already use generative AI and AI coding aids while the jurisdiction lacks a proportionate adopted policy and deployment gate.","stakeholders":["Mayor/administrator","Council/board","Attorney","Clerk","IT or IT vendor"],"discoveryQuestions":["Has the governing body adopted any AI policy?","Who owns AI exceptions and the tool inventory?","How are AI-built scripts reviewed before production?","Which decisions are barred from AI finalization?"],"valueHypothesis":"Adapting MAIN’s template—including the Sept. 26 AI-created-software clause—gives lean governments a human-oversight and change-control baseline without a large PMO.","potentialEngagement":"Three-week small-city AI policy sprint: gap map to MAIN sections, draft resolution, approved-tool list, and AI-built software review checklist.","unsupportedClaims":["That using the template equals legal compliance","Guaranteed staffing savings","That MAIN endorsement replaces local counsel"]},"engineering":{"fit":"Strong for FAQ assistants and internal drafting under human review; weak for autonomous permitting or enforcement.","architectureIntegration":"Approved-tool pathway; local/self-hosted exploratory lane offline; production AI and AI-built automations under change control and identity access.","prerequisites":["Policy adoption","Named AI owner","Data classification","Change-control hook for AI-built code"],"constraints":["Lean IT","Vendor-managed systems","State-law localization needed outside Mississippi"],"security":"Keep restricted data out of public models; review vendor training rights; treat downloaded model weights as supply-chain code.","proofOfValue":["Adopted policy on file","Approved-tool inventory current","AI-built deployment reviews logged","High-risk uses have manual fallback"]},"delivery":{"work":"Workshop template sections, draft local policy, train staff, stand up inventory, and insert AI-software review into release process.","dependencies":["Attorney","Clerk/records","IT vendor","Department heads","MAIN training (optional)"],"ownership":"Administrator-designated AI governance owner; departments own use-case accuracy.","skillsAdoption":"Employees learn approved uses and that coding-tool permission is not production authority.","governanceCheckpoints":["Governing-body adoption","Annual policy review","Incident routing test","Procurement AI questions in purchasing"],"acceptanceCriteria":["Resolution or ordinance adopted","Staff owner named","Approved/prohibited use list published internally","First AI-built software review completed"],"risks":["Template copied without counsel","Shadow tools continue","Accessibility and records duties ignored"]}},"retrievedAt":"2026-09-28T22:20:57-05:00","enrichedAt":"2026-09-28T22:27:03-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Template ties AI tools to ADA Title II / WCAG expectations and role-based training—critical for small staffs and resident equity.","procurementImplications":"Adds AI-specific purchasing questions (training rights, storage, audit logs) and treats quiet AI features in existing software as review triggers.","operatingModelImplications":"Proportionate governance for lean governments: short policy plus procedures, human final authority on high-risk services, and change control for AI-built automations.","sourceVerification":{"openedUrl":"https://mainms.org/ai-policy-and-guidance-template-local-government/","referenceExcerpt":"MAIN editorial recommendation, added September 26, 2026. Adapt within existing approval processes.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}