{"resourceId":"fairhaven-ma-select-board-ai-policy-five-principles-20261015","versions":[{"version":"external-18a9e435ab5fb5ceeedd41172b7273da874544c3b02263cf805fb67179919250","resource":{"id":"fairhaven-ma-select-board-ai-policy-five-principles-20261015","title":"Fairhaven, Massachusetts Select Board adopts an IT-drafted staff AI policy with five principles, pending public works board and town counsel review","organization":"Town of Fairhaven, Massachusetts","sector":"Municipal governance and staff AI use","geography":"Fairhaven, Massachusetts, United States","publishedAt":"October 15, 2026","publicationDate":"2026-10-15","eventDate":"2026-10-13","sourceName":"Fairhaven Neighborhood News","sourceLabel":"Independent local news report","sourceUrl":"https://fairhavenneighborhoodnews.com/fairhaven-select-board-okays-ai-policy-closes-stm-warrant/","evidenceClass":"independent-reporting","outcomeClass":"emerging","topics":["governance-procurement","data-security","operating-model"],"finding":"On Oct 13 the Fairhaven Select Board adopted the IT director's more comprehensive draft AI policy over a board member's earlier draft, adding her preamble and excluding school employees, who have their own policy. Adoption is pending review by the autonomous Board of Public Works and town counsel. The policy sets security requirements, acceptable use and approved tools chosen by data sensitivity. Five principles: the employee owns the output; tool choice follows data sensitivity, not convenience; no AI system makes the final determination affecting a resident; transparency by default so residents know when AI shaped something affecting them; and anything entered into a public AI service is treated as disclosed. The IT director said answers must be vetted because AI is not always accurate and called the policy a living document.","sledRelevance":"Shows a small New England town adopting a principle-based policy where resident transparency and data-sensitivity tool selection are explicit, and where autonomous boards and school departments fragment who is covered.","evidence":"Neighborhood News article opened in full via curl HTML save; both draft policies are said to be in the 9/28 and 10/13 meeting packets, which were not opened.","architectureImplications":"Tool selection by data sensitivity implies at least two tiers (public AI services for public information, vetted tools for sensitive data) and department-level vetting of software.","governanceImplications":"Adoption is conditional on Board of Public Works and town counsel review; school department and BPW coverage are separate, so a single town-wide policy is not yet in force.","securityPrivacyImplications":"Treat public AI inputs as disclosed; security vetting determines approved tools; no technical controls described.","caveats":"Local weekly report; policy text and packet not opened; final adoption pending review; no list of approved tools reported.","streamIds":["local-government"],"roles":{"sales":"Sales framing: Fairhaven pairs a no-final-determination rule with a default duty to tell residents when AI shaped something affecting them. Discovery should ask how the town will implement that disclosure and which tools pass security vetting. A bounded engagement could build a data-sensitivity tool matrix and disclosure template. The evidence does not support claims of time savings or that the policy is final, since BPW and counsel review remain. Interpretation: small towns need packaged, low-cost governance artifacts.","engineering":"Engineering framing: Fit is a two-tier tool model separating public AI services from vetted tools for sensitive data. Integration needs a way to label AI-assisted outputs for resident transparency. Prerequisites are a data-classification scheme and department vetting criteria; constraints include separate school and BPW governance. Proof of value is a vetted-tool list mapped to data classes and a working disclosure label. Interpretation: lightweight controls and labeling fit better than heavy platforms for a town this size.","delivery":"Delivery framing: Complete BPW and town counsel review, publish the approved-tool list, and train staff on the five principles and disclosure duty. Ownership sits with the IT director with the town administrator. Acceptance criteria should include final legal sign-off, a published tool list and a disclosure practice applied to resident-facing documents. Risks include coverage gaps across autonomous boards and drift as tools change. Interpretation: treat the living-document review cadence as a delivery requirement."},"roleDetails":{"sales":{"customerProblem":"Town needs safe staff AI use with resident transparency but little dedicated capacity.","stakeholders":["Select Board","Town Administrator","IT Director","Board of Public Works","Town counsel"],"discoveryQuestions":["How will residents be told AI shaped a decision?","Which tools pass security vetting?","Will BPW adopt the same policy?","Who updates the living document?"],"valueHypothesis":"Clear tiers and disclosure rules may reduce risky public-AI use; no outcome data.","potentialEngagement":"Short engagement producing a data-sensitivity tool matrix, disclosure template and staff briefing.","unsupportedClaims":["Time or cost savings","That the policy is final","That disclosure is already practiced"]},"engineering":{"fit":"Small municipalities choosing tools by data sensitivity.","architectureIntegration":"Two-tier tool allowlist with labeling of AI-assisted resident-facing outputs.","prerequisites":["Data classification scheme","Department vetting criteria","Inventory of tools in use"],"constraints":["Schools and BPW governed separately","No resident-affecting final AI determinations","Public AI inputs treated as disclosed"],"security":"Security vetting gates tool approval; specific controls not described.","proofOfValue":["Vetted tool list mapped to data classes","Disclosure label used on sample documents","Spot-check of staff verification"]},"delivery":{"work":"Finish legal and BPW review, publish tools, train staff, set review cadence.","dependencies":["Town counsel","Board of Public Works","IT Director","Department heads"],"ownership":"IT Director with Town Administrator.","skillsAdoption":"Staff must vet AI answers; training approach not reported.","governanceCheckpoints":["Counsel sign-off","BPW decision","Periodic living-document review"],"acceptanceCriteria":["Proposed: final adoption recorded after counsel review","Proposed: approved-tool list published","Proposed: disclosure practice documented for resident-facing outputs"],"risks":["Coverage gaps across boards","Policy drift","Disclosure duty not operationalized"]}},"retrievedAt":"2026-10-16T22:20:30-05:00","enrichedAt":"2026-10-16T22:40:00-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Employees personally accountable for AI output; training not described.","procurementImplications":"Departments must vet software; approved-tool list based on security review.","operatingModelImplications":"Resident-affecting final determinations stay human; transparency by default creates a disclosure duty when AI shapes resident-facing work.","sourceVerification":{"openedUrl":"https://fairhavenneighborhoodnews.com/fairhaven-select-board-okays-ai-policy-closes-stm-warrant/","referenceExcerpt":"No AI system makes the final determination affecting a resident.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}