{"resourceId":"idaho-judicial-branch-ncsc-ai-governance-final-report-20261019","versions":[{"version":"external-b94a0f6529916f1322fdde17e640df47a1513b240b2d653702fe72ec0cd8e333","resource":{"id":"idaho-judicial-branch-ncsc-ai-governance-final-report-20261019","title":"Idaho Judicial Branch’s NCSC AI Governance Implementation final report shows the courts set aside their first AI pilot to finish governance, policy and evaluation work first","organization":"Idaho Supreme Court / Idaho Judicial Branch (with National Center for State Courts)","sector":"Courts / AI governance and acceptable use","geography":"Idaho, United States","publishedAt":"Final report dated August 2026; released by the Idaho Supreme Court on 2026-10-19","publicationDate":"2026-10-19","eventDate":null,"sourceName":"Idaho Supreme Court (report prepared by National Center for State Courts)","sourceLabel":"Idaho Judicial Branch AI Governance Implementation: Final Report (August 2026)","sourceUrl":"https://api.isc.idaho.gov/uploads/Media_Resources/1792423786957-8.31_Final_AI_Report.pdf","evidenceClass":"government-evaluation","outcomeClass":"mixed","topics":["governance-procurement","infrastructure","accessibility-workforce","operating-model"],"finding":"The NCSC-prepared final report says the project originally planned to select and implement a pilot AI application, but participants concluded governance, policy, evaluation and readiness work should come first, so the pilot was set aside; requirements started for it were paused. Deliverables include an internal AI acceptable use policy (acceptable and prohibited uses, privacy, human oversight, protection of judicial work product), an AI technical architecture and review process, a reference architecture framework for internally built or vendor AI, and a risk-based project lifecycle framework. The technology architecture team completed about 75% of planned activities and the stakeholder engagement team about 85%. A review of judicial canons concluded existing canons already give substantial guidance, favoring education over new ethics rules.","sledRelevance":"This is a primary account of a state court system deliberately choosing governance before deployment. It gives other courts a concrete sequence (policy, architecture review, lifecycle gate, then pilot) and shows that a pilot can be paused when governance is not ready.","evidence":"Opened the full PDF report linked from the Idaho Supreme Court’s Oct. 19 news release. Completion percentages and deliverables are self-reported by the project. A news story archived on 2026-10-14 (idahonews.com) previewed the report’s draft policy; this primary release adds the pilot decision, architecture frameworks and completion status. No outcome metrics exist because no AI tool was deployed under the project.","architectureImplications":"The branch created a reference architecture framework covering security expectations and integration requirements for internally developed and vendor AI, plus a technical review gate before approval or expansion.","governanceImplications":"Guiding principles were adopted by the Idaho Supreme Court earlier in 2026; the report proposes a standing AI advisory committee, which may also advise on bar rules for attorneys.","securityPrivacyImplications":"Policy discussion focused on confidentiality, data ownership, solution-provider restrictions and risks of public AI systems.","caveats":"Self-reported project report; no deployment or effectiveness data; recommendations not yet all adopted; previously previewed in news coverage.","streamIds":["public-safety"],"roles":{"sales":"Sales framing: Idaho’s courts chose to finish governance before buying or building any AI tool, and paused their first pilot. Court administrators elsewhere face the same choice. The bounded offer is help standing up an architecture review and lifecycle gate, not a tool sale. The report has no deployment results, so it cannot support claims about efficiency gains in courts.","engineering":"Engineering framing: the report defines a reference architecture and a technical review process every AI product must pass, internal or vendor. Pre-sales should map a proposed solution to those requirements: security expectations, integration standards, data ownership, solution-provider restrictions and human oversight. Proof should show a candidate tool clearing the review gate with documented evidence.","delivery":"Delivery framing: the work is operationalizing policy, architecture review and lifecycle governance so a first pilot can proceed safely. Dependencies include court IT, procurement and a standing advisory committee. The owner is the court administrative office under Supreme Court direction. Acceptance should be defined as completed review artifacts and a selected, approved pilot with success measures."},"roleDetails":{"sales":{"customerProblem":"Court systems want AI benefits but lack policy, architecture review and lifecycle gates to approve any tool.","stakeholders":["State court administrator","Chief Justice or judicial council","Court CIO","Procurement officer","Bar association liaison"],"discoveryQuestions":["Do you have an AI acceptable use policy for judges and staff?","Is there a technical review gate for AI tools?","Which AI features already exist in court software?","What business problem would a first pilot solve?"],"valueHypothesis":"A defined review gate and reference architecture can shorten the path to an approved first pilot.","potentialEngagement":"6-week AI governance operationalization: review process, reference architecture checklist and first-pilot selection criteria.","unsupportedClaims":["Efficiency gains from court AI","That governance-first delays are short","That vendor tools meet the framework"]},"engineering":{"fit":"State and county court systems evaluating AI in court operations.","architectureIntegration":"Map proposed AI solutions to a reference architecture covering security, integration, data ownership and human oversight, and run them through a technical review gate.","prerequisites":["Inventory of existing AI features in court systems","Acceptable use policy","Review board membership"],"constraints":["Judicial independence requirements","Confidential records","Public AI systems unsuitable for court data"],"security":"Keep court data out of public AI systems and require provider restrictions on data use.","proofOfValue":["Proposed: run one candidate tool through the review gate and record findings","Proposed: verify inventory of embedded AI features is complete"]},"delivery":{"work":"Operationalize the review process, maintain the reference architecture and select a first pilot with defined success measures.","dependencies":["Standing advisory committee","Court IT capacity","Procurement alignment"],"ownership":"Administrative office of the courts under Supreme Court direction","skillsAdoption":"AI literacy for judges and staff; education on how canons apply to AI use.","governanceCheckpoints":["Technical architecture review","Lifecycle stage gates","Supreme Court approval of policy changes"],"acceptanceCriteria":["Proposed: review gate completed for first pilot candidate","Proposed: success metrics defined before pilot launch"],"risks":["Governance work stalls adoption indefinitely","Embedded vendor AI bypasses review","Committee not sustained"]}},"retrievedAt":"2026-10-20T02:53:25Z","enrichedAt":"2026-10-20T02:58:42Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"The project included AI literacy and education work; the ethics review favored education and clarification over new rules.","procurementImplications":"The lifecycle framework supplements existing demand management, procurement, enterprise architecture and cybersecurity processes for AI projects.","operatingModelImplications":"Final AI policy decisions rest with the Idaho Supreme Court in its administrative role; a standing committee is proposed for ongoing advice.","sourceVerification":{"openedUrl":"https://api.isc.idaho.gov/uploads/Media_Resources/1792423786957-8.31_Final_AI_Report.pdf","referenceExcerpt":"participants ultimately concluded that governance, policy, evaluation, and readiness activities should be completed before moving forward with any implementation.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}