{"resourceId":"oregon-eo-26-26-frontier-ai-procurement-standards-20260923","versions":[{"version":"external-d1f4999527589e4c499418c7f1373f9a6c73a9017d2206baa0cb59741baea98d","resource":{"id":"oregon-eo-26-26-frontier-ai-procurement-standards-20260923","title":"Oregon EO 26-26 directs third-party frontier AI safety reviews and kill-switch assessment for state procurement","organization":"Office of the Governor of Oregon (Tina Kotek) / State Chief Information Officer","sector":"State executive AI procurement and shared IT governance","geography":"Oregon, United States","publishedAt":"2026-09-23","publicationDate":"2026-09-23","eventDate":"2026-09-23","sourceName":"State of Oregon Executive Order No. 26-26 — Establishing Responsible Artificial Intelligence Procurement Standards for State Government","sourceLabel":"Official scanned executive order PDF (Governor’s Office) opened via public Drive link cited by contemporaneous news","sourceUrl":"https://drive.google.com/file/d/1FHCBOBdcaUNZ3_Zg2WxtSXZpYzP8tk1h/view","evidenceClass":"government-evaluation","outcomeClass":"emerging","topics":["governance-procurement","data-security","operating-model","infrastructure"],"finding":"Why now: on 2026-09-23 Governor Kotek signed EO 26-26, stating Oregon policy to seek frontier AI models that have received independent third-party AI safety review. The State CIO must, within 90 days, submit an implementation proposal covering a frontier-model definition; standards for adequate third-party safety review; evaluation of a kill-switch requirement’s viability; methods to assess reviewer independence/qualifications/methodology/transparency; integration into procurement and technology-use practices; exceptions when review is unavailable; ongoing monitoring; transparency recommendations; and any needed statutory/administrative/budgetary changes. Order is effective immediately, remains until terminated, and must be reassessed every three months. Builds on EO 23-26 AI Advisory Council work and existing Responsible AI Usage Policy.","sledRelevance":"Direct state-government procurement control for frontier models—transferable to other states designing purchase gates for advanced GenAI without waiting for federal standards; explicitly uses contracting power rather than only agency-use policy.","evidence":"Primary: four-page official EO PDF OCR’d after HTTPS download. Corroborated by KVAL (updated 2026-09-23) and EIN/Oregon DEQ release summarizing the same directives. No measured pilot outcomes in the order itself.","architectureImplications":"Expect procurement and enterprise architecture reviews to add third-party safety-review artifacts and possible kill-switch contractual clauses for frontier models; SCIO coordination across agencies; exceptions path for specialized/public-safety needs when review unavailable.","governanceImplications":"Shifts frontier AI buying toward documented independent assessment and quarterly gubernatorial reassessment; proposal may recommend statute/admin changes. Existing Responsible AI Usage Policy remains baseline for generative/agentic use.","securityPrivacyImplications":"Frames frontier AI risks to privacy, cybersecurity, public safety, and civil rights; third-party review and potential kill-switch aimed at containment/safety—not a substitute for agency data-handling controls already in Oregon policy.","caveats":"Standards and kill-switch requirement are not yet operational—only a 90-day proposal mandate. OCR of scanned PDF may contain minor transcription artifacts; prefer final oregon.gov posting when available. Political statements about federal leadership are not treated as empirical findings.","streamIds":["state-government"],"roles":{"sales":"Sales framing: Oregon just turned frontier-model buying into a third-party safety-review and possible kill-switch problem for state procurement. Lead with readiness to help SCIO/agencies shape the 90-day proposal—definitions, reviewer criteria, contract clauses—not with product demos that ignore independent evaluation. Bound any engagement to documenting current frontier purchases and gap-analysis against EO 26-26. Do not promise that a vendor’s self-attestation will satisfy Oregon’s forthcoming standards.","engineering":"Engineering framing: treat EO 26-26 as a forthcoming control plane on which frontier models may enter state stacks. Map existing model inventory to a draft frontier definition, identify where third-party eval artifacts would attach in RFP/contract flow, and stress-test kill-switch feasibility for hosted APIs versus on-prem. Proof-of-value is a scored sample of current GenAI contracts against independence/methodology/transparency criteria—not latency benchmarks.","delivery":"Delivery framing: stand up a cross-agency working group to feed the SCIO 90-day proposal, including procurement, privacy, cyber, and program owners. Acceptance should include a documented exception path and monitoring cadence matching the EO’s quarterly reassessment. Primary risk is agencies rushing frontier buys before standards exist, or treating kill-switch language as checkbox theater without testable shutdown procedures."},"roleDetails":{"sales":{"customerProblem":"States want frontier GenAI capabilities but lack agreed third-party safety-review and shutdown criteria in procurement.","stakeholders":["Governor’s office / SCIO","Agency CIOs","State procurement","Cyber/privacy officers","Budget staff"],"discoveryQuestions":["Which current contracts would meet a draft frontier definition?","What third-party evals do vendors already have?","Who owns kill-switch testing if required?","What exception path is needed for public-safety tools?"],"valueHypothesis":"A bounded 90-day proposal-support engagement can translate EO 26-26 into actionable procurement criteria without promising certified safe models.","potentialEngagement":"6–8 week frontier-procurement standards workshop and contract-clause drafting support for the SCIO proposal.","unsupportedClaims":["Guaranteed federal alignment","Vendor self-attestation equals independent review","Kill switch already proven in state production"]},"engineering":{"fit":"Fit for adding evaluation gates and contractual controls around frontier model APIs/platforms; unfit as a substitute for application-level safety testing.","architectureIntegration":"Insert review artifacts into IT investment/procurement gates; tag frontier models in inventory; design shutdown/disable paths per hosting model.","prerequisites":["Model inventory with capability tags","Procurement clause library","Reviewer evaluation rubric","Exception workflow"],"constraints":["Oregon executive-branch scope","90-day proposal clock","Federal/state law still apply","OCR/primary text may be refined on oregon.gov"],"security":"Independent review does not replace agency data-classification, logging, or access control for GenAI workloads.","proofOfValue":["Gap score of top 10 GenAI contracts vs draft criteria","Tabletop kill-switch test for one hosted model","Exception path exercise","Quarterly reassessment checklist"]},"delivery":{"work":"Facilitate SCIO proposal drafting, stakeholder interviews, and pilot clause insertion on a non-production or upcoming buy.","dependencies":["SCIO sponsorship","DAS procurement counsel","Agency application owners","Existing Responsible AI Usage Policy owners"],"ownership":"State CIO with Governor approval for policy implementation.","skillsAdoption":"Procurement officers need AI-eval literacy; engineers need shutdown runbooks.","governanceCheckpoints":["Draft frontier definition review","Proposal submission day 90","Governor approval gate","Quarterly EO reassessment"],"acceptanceCriteria":["Written proposal covering all EO-required elements","Published interim guidance for new frontier buys","Documented exception criteria","Monitoring plan named"],"risks":["Agencies buy ahead of standards","Kill-switch language without test evidence","Over-broad frontier definition blocking low-risk tools"]}},"retrievedAt":"2026-09-23T22:28:30-05:00","enrichedAt":"2026-09-23T22:33:54-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"EO focuses on procurement safety of frontier models rather than workforce accessibility; implementation should still preserve accessibility requirements already embedded in Oregon IT procurement.","procurementImplications":"Core impact is on purchase/contract criteria for frontier AI—third-party review evidence, possible kill-switch terms, exception handling, and transparency about state frontier-model use.","operatingModelImplications":"Creates a time-boxed SCIO-led standards build with agency cooperation duties and quarterly gubernatorial revisit—operating model is policy-then-implement, not an immediate ban.","sourceVerification":{"openedUrl":"https://drive.google.com/file/d/1FHCBOBdcaUNZ3_Zg2WxtSXZpYzP8tk1h/view","referenceExcerpt":"Evaluation of the viability of a \"kill switch\" requirement as one of the standards","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}