From the K–12 edition of September 28, 2026
Oregon ODE GenAI Guidance v3: human-centered use, productive struggle, and risks of AI relationships
Oregon Department of Education · State education agency guidance · United States — Oregon (transferable advisory principles)
- Publisher
- Oregon Department of Education
- Original publication
- June 2026 (Version 3)
- Source retrieved
- 2026-09-29
What happened
Oregon ODE’s June 2026 Generative AI in K-12 Classrooms Guidance (v3) centers human relationships and educator agency: GenAI should strengthen, not replace, authentic classroom relationships; humans stay in the driver’s seat; and leaders should create policy guardrails before GenAI enters classrooms. Dedicated sections address students depending too much on GenAI (cognitive offloading; protecting productive struggle; AI-resistant/AI-integrated assessment redesign) and concerns about forming human-like relationships with AI, citing continuum research from helpful use to emotional attachment reinforced by warmth/validation features, with younger users potentially more vulnerable. Privacy guidance stresses never entering PII into genAI systems and FERPA/COPPA competence.
Why it matters
Directly operationalizes the K12 stream’s developmental-risk and assisted-vs-retained-learning brief with SEA language usable beyond Oregon.
Evidence and measured results
Official 42-page SEA guidance PDF inspected in full; synthesizes external research (Brookings, UTS, RCTs) rather than running a new Oregon trial.
Limitations and uncertainty
June dated—older than last run but not previously archived; advisory not statutory; cited attachment/offloading studies vary in strength; why-now is alignment with same-day state-mandate operationalization and recent mastery themes.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-28; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Leaders need SEA-backed language to limit cognitive offloading and companion-AI attachment risks while still building AI literacy.
- Stakeholders
- superintendents
- curriculum
- counselors
- IT/privacy
- teachers
- families
- Discovery questions
- Where does your policy draw the line on companion/anthropomorphic student AI?
- How do teachers protect productive struggle when AI can finish the task?
- What signs of emotional attachment to AI trigger counselor/teacher intervention?
- Is PII banned from open genAI prompts in staff AUP?
- Value hypothesis
- If districts adopt Oregon-style human-centered guardrails before tool entry, they can pursue AI literacy without normalizing cognitive offloading or machine companionship.
- Potential engagement
- Guidance crosswalk workshop producing local policy language on productive struggle, companion AI limits, and staff PII rules.
- Unsupported claims
- That Oregon guidance is binding law outside Oregon
- Guaranteed prevention of AI emotional attachment via policy alone
- That all student AI use causes cognitive atrophy
Pre-sales engineering
Role takeaway
- Fit
- Advisory fit for U.S. districts writing human-centered GenAI policies; especially relevant where companion AI and screen/developmental debates are active.
- Architecture and integration
- Disable companion/persona modes for minors; default to task-bounded tutors; block PII in prompts; provide AI-off paths for struggle tasks.
- Prerequisites
- Local AI policy before classroom genAI
- Educator AI competency PD
- Privacy vetting of tools
- Family communication resources
- Constraints
- Guidance is non-prescriptive on a single pathway
- Evidence on long-term attachment/offloading still emerging
- Local capacity varies
- Security
- Never enter PII into genAI systems; FERPA/COPPA awareness; vetted tools only for student use.
- Proof of value
- Field observations show AI-off productive-struggle tasks retained
- Companion features disabled on student tenants
- Staff prompt audits find no PII leakage
Delivery
Role takeaway
- Work
- Adopt human-centered principles, ban or tightly review companion AI, train staff on offloading risks, and revise assessments for AI-resistant/AI-integrated designs.
- Dependencies
- board/policy cycle
- counseling protocols
- vendor feature flags
- PD time
- Ownership
- Curriculum/leadership own pedagogy guardrails; IT owns technical disables; student services own attachment-risk response.
- Skills and adoption
- Build educator AI competencies covering pedagogy, assessment redesign, and privacy habits before student scale.
- Governance checkpoints
- Pre-deployment policy gate
- Mid-year offloading/companion review
- Equity impact check on access and use
- Acceptance criteria
- Written companion-AI limits
- PII-in-prompt prohibition in AUP
- Assessment redesign samples for core courses
- Risks
- Students use consumer companion apps off-network
- Teachers equate AI fluency with mastery
- Over-restriction without literacy instruction
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Disable companion/anthropomorphic modes for students; preserve AI-off struggle paths; enforce PII-free prompting and vetted closed systems.
Governance
Who approves, reviews and stays accountable for outcomes?
Policy-before-tools sequencing; ongoing literacy and ethics PD; local adaptation within human-centered principles.
Security and privacy
What data, permissions and controls need testing?
No PII in open genAI; vetted compliant tools only; staff competence on FERPA/COPPA and AUPs.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Equity section warns AI may widen gaps without human-centered policies; durable skills framed as equity/civic necessities.
Procurement
What should contracts, pricing and exit terms secure?
Prefer tools supporting human-in-the-loop control, struggle-preserving pedagogy, and strict privacy—not engagement-maximizing companion designs.
Operating model
Which teams own the service once it runs?
Capacity-building (educator competencies) and policy guardrails precede classroom genAI scale.
Publication history
- 2026-09-28K–12 · Issue 235 resources
Stable resource ID: oregon-ode-genai-k12-guidance-v3-202606