{"resourceId":"oregon-eo-26-26-tly-shall-seek-analysis-20260924","versions":[{"version":"external-57e6cd9715be6f8557e97b525eb39144cb281fe10380f174321e296bf40c5614","resource":{"id":"oregon-eo-26-26-tly-shall-seek-analysis-20260924","title":"TLY (Sep 24): Oregon EO 26-26 “shall seek to” use third-party-reviewed frontier models—policy and CIO drafting task, not vendor rule yet","organization":"The Leveraged Years (regulatory analysis of Oregon EO 26-26)","sector":"State frontier-AI procurement policy / executive order interpretation","geography":"United States — Oregon state government agencies (State CIO proposal due ~22 Dec 2026 by TLY count)","publishedAt":"2026-09-24","publicationDate":"2026-09-24","eventDate":"2026-09-23","sourceName":"The Leveraged Years","sourceLabel":"Oregon EO 26-26 Sets Frontier AI Review Policy","sourceUrl":"https://www.theleveragedyears.com/ai-regulation-news/oregon-eo-26-26-frontier-ai-procurement-third-party-review-2026","evidenceClass":"independent-research","outcomeClass":"cautionary","topics":["governance-procurement","operating-model","data-security"],"finding":"TLY’s Sep 24, 2026 analysis of Oregon Executive Order 26-26 (signed Sep 23, 2026) concludes the order binds state agencies to a policy that the State “shall seek to” purchase/contract/use frontier AI models that have received independent third-party safety review, plus a 90-day State CIO proposal covering definition, review criteria, kill-switch viability, reviewer independence, procurement processes, exceptions, monitoring, transparency, and needed statutory changes. TLY stresses no procurement standard exists yet, the order places no direct obligation on AI developers/vendors, FAQ “only if” wording is stronger than the signed order, and implementation follows only upon Governor approval of the CIO proposal (~22 Dec 2026 by TLY arithmetic).","sledRelevance":"Independent Sep 24 analysis that Oregon EO 26-26’s operative verb is “shall seek to” and imposes no direct vendor duty yet. Why now: EO primary text is archived, but this shall-seek/procurement-gap reading was never published after Oct 2 rejection—still the clearest SLED procurement caution.","evidence":"Opened the TLY HTTPS analysis via curl (UA SLED-research-bot/1.0) and text extraction; confirmed Published/Updated 2026-09-24; captured “shall seek to,” no-direct-vendor-obligation, FAQ “only if” contrast, nine-point CIO brief, and 22 Dec 2026 proposal timing as TLY’s stated arithmetic.","architectureImplications":"Until an approved CIO standard exists, architecture work is inventorying frontier model uses and documenting review status—not ripping out unreviewed models under a nonexistent ban.","governanceImplications":"Treat EO as policy + drafting instruction. Exceptions for emerging/specialized/public-safety uses are anticipated before the rule exists. Reassess cadence every three months per order.","securityPrivacyImplications":"Kill switch is an evaluation topic for the CIO proposal, not a current requirement; third-party safety review criteria remain undefined.","caveats":"Secondary regulatory analysis; TLY OCR’d a scanned Drive-hosted order; Secretary of State attestation line observation is noted by TLY without legal conclusion; 22 Dec date is analyst arithmetic not printed on the order.","streamIds":["state-government"],"roles":{"sales":"Position Oregon EO 26-26 via TLY’s Sep 24 read as a state procurement-policy signal—“shall seek to” use third-party-reviewed frontier models—while stressing no vendor rule or ban exists until a Governor-approved CIO proposal. Discovery should ask which frontier models are in use, what review evidence vendors can show, and who owns Oregon’s 90-day response. Bounded engagement: a 60-day frontier-model inventory and review-evidence pack timed to the CIO proposal window. Unsupported claims include that Oregon already bans unreviewed frontier models, that a kill switch is required now, or that FAQ “only if” language overrides the order.","engineering":"Fit is inventory + evidence collection for eventual procurement standards—not a forced cutover. Architecture should tag frontier vs non-frontier uses, store any third-party eval reports, and design exception paths matching the EO’s anticipated carve-outs. Prerequisites: model inventory, counsel definition watch, procurement liaison. Constraints: standards unwritten; TLY secondary. Proof of value is a complete inventory with review-status fields before Dec 2026.","delivery":"Delivery runs the inventory, stands a CIO-proposal watch, and prepares draft solicitation language marked contingent on approval. Dependencies: State CIO office, agency CIOs, procurement, vendors. Ownership of purchasing decisions stays with agencies under current policies until directed otherwise. Acceptance criteria: inventory complete; watch owner named; no absolute ban clauses issued prematurely. Risks: FAQ-driven over-compliance and ignoring exception needs for specialized systems."},"roleDetails":{"sales":{"customerProblem":"Agencies and vendors misread Oregon’s EO as an immediate frontier-model ban or vendor mandate.","stakeholders":["State CIO","Agency CIOs","Procurement counsel","Frontier vendors","Governor’s office"],"discoveryQuestions":["Which systems use frontier models today?","What third-party review evidence exists?","Who owns the 90-day CIO proposal input?","Where are specialized/public-safety exceptions likely?"],"valueHypothesis":"Inventorying frontier uses and review evidence before standards land reduces emergency re-procurement.","potentialEngagement":"60-day frontier inventory and review-evidence pack aligned to the CIO proposal window.","unsupportedClaims":["EO already bans unreviewed models","Kill switch required now","FAQ overrides signed order","Direct vendor obligations exist today"]},"engineering":{"fit":"Tagging and evidence-ready architecture awaiting approved standards.","architectureIntegration":"Model inventory to review-status metadata to procurement flags to future exception workflow.","prerequisites":["Inventory","Definition watch","Procurement liaison"],"constraints":["Unwritten standards","Secondary analysis","Scanned primary order"],"security":"Preserve eval reports and access controls; kill-switch design only if later required.","proofOfValue":["Complete frontier inventory","Review-evidence attached","Exception candidates listed"]},"delivery":{"work":"Inventory; proposal watch; contingent solicitation language; staff FAQ vs order briefing.","dependencies":["State CIO","Agency owners","Procurement","Vendors"],"ownership":"Agencies retain current purchasing practice until Governor-directed implementation.","skillsAdoption":"Brief buyers on “shall seek to” vs “only if” and on exception categories.","governanceCheckpoints":["Inventory complete","Pre-proposal agency input","Post-approval clause activation"],"acceptanceCriteria":["No premature absolute ban clauses","Watch owner named","Inventory filed"],"risks":["Over-compliance from FAQ","Under-preparing for approved standards","Missing specialized exceptions"]}},"retrievedAt":"2026-10-03T22:21:31-05:00","enrichedAt":"2026-10-03T22:21:31-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Procurement and agency CIO staff need shared briefings so FAQ headlines do not drive stricter practice than the order’s verb requires—while still preparing for approved standards.","procurementImplications":"Do not put “only independently reviewed frontier models” as an absolute RFP ban citing EO 26-26 alone; track the CIO proposal and Governor approval before hard clauses.","operatingModelImplications":"Three-link chain: CIO proposal → Governor approval → agency purchasing/contracting. Vendors feel impact only at link three.","sourceVerification":{"responseId":"curl-oregon-eo-26-26-tly-shall-seek-analysis-20260924-20261003","openedUrl":"https://www.theleveragedyears.com/ai-regulation-news/oregon-eo-26-26-frontier-ai-procurement-third-party-review-2026","referenceExcerpt":"Its operative verb is \"shall seek to\", and every standard a vendor would eventually have to meet is still unwritten.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}