From the Student Success edition of September 10, 2026
Critical review offers questions for preserving learner judgment, not a validated dependency scale
Yiran Du and Yijia Yuan, University of Cambridge · Higher education teaching and learning · UK-authored review drawing on international literature; no study population
- Publisher
- Epistemic dependence in AI-mediated learning
- Original publication
- August 29, 2026
- Source retrieved
- 2026-09-11
What happened
The review distinguishes useful assistance from delegation that displaces learner judgment; it does not establish that frequent AI use causes harm.
Why it matters
Useful for U.S. college assessment design discussions, with no local prevalence or causal effect to transfer.
Evidence and measured results
Purposive synthesis of 60 works, searches updated July 2026. No new dataset, experimental baseline or effect estimate. Proposed diagnostic criteria require validation.
Limitations and uncertainty
Nonexhaustive conceptual review; hypotheses from adjacent domains are not demonstrated educational effects. Detailed table endpoint failed, so no table-only claims are used; main-text methods and limitations were accessible.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-11; this does not change the original publication date. Labels below come from the analysis itself.
Sales
Role takeaway
Academic leaders may struggle to distinguish legitimate assistance from work that conceals missing understanding. Convene faculty, students, disability services, librarians and assessment leads. Ask which learning outcomes require an explanation, whether students can challenge automated feedback and which current practices already support that skill. A bounded engagement could review one course's AI-assisted assessment and develop a pilot rubric. The value hypothesis is clearer and more defensible assessment, to be tested locally. This conceptual review is a discussion aid rather than evidence of institutional harm. Do not claim that high usage identifies dependence, that a new rubric is validated, or that restricting tools necessarily improves equity.
Pre-sales engineering
Role takeaway
Fit the proposal to a course workflow in which students can inspect evidence and record a reasoned response to feedback. Prerequisites include accessible source materials, clear permissions and faculty-approved examples. Build a small test collection containing unsupported claims, conflicting sources and ambiguous feedback; verify that citations resolve and access controls hold.
- Proposed proof of value
- students can challenge a wrong suggestion and complete a separate explanation task using agreed accommodations. Record unresolved cases without creating a permanent behavioral profile. The review cannot select a model or prove interface changes cause learning gains. Developer copilots may be examined with the same task-specific questions, but production agents require separate assurance.
Delivery
Role takeaway
An assessment lead should own the pilot, with faculty judging disciplinary reasoning and disability staff reviewing equivalent participation. Map permitted assistance, prepare student examples and train markers before the assignment opens. Dependencies include moderation time, approved data handling and a clear appeal route.
- Proposed acceptance criteria
- all sampled marks can be explained against published criteria; students can access a challenge route; agreed accommodations work; and a follow-up task is reported with missing responses. These are proposed service and evaluation gates, not observed effects. Risks include inconsistent marking, extra student burden and turning a conceptual framework into an unsupported misconduct detector. Review feedback before extending the approach.
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?
Pilot traceable evidence links and a student-visible route to challenge feedback. Test retrieval permissions and provenance separately from model fluency. No cloud, on-premises or hybrid architecture is validated; autonomous agents receive no deployment endorsement.
Governance
Who approves, reviews and stays accountable for outcomes?
Define which judgments a course expects students to perform, then make permitted assistance explicit. Evaluate policy effects before attaching penalties to a new rubric.
Security and privacy
What data, permissions and controls need testing?
Use minimal assessment artifacts rather than comprehensive surveillance. Protect personal reflections and accommodation records from unnecessary model processing.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Preserve assistive technologies when testing independent judgment, and compensate staff for rubric development and moderation.
Procurement
What should contracts, pricing and exit terms secure?
Request demonstrations of citation inspection, student challenge routes, configuration control and export before committing to a platform.
Operating model
Which teams own the service once it runs?
Place responsibility for educational decisions with course owners rather than expecting students alone to detect every system error.
What changed
New in all 182 archive records and identifier-specific search. August 29 review is newly archived evidence backfill, not a new September 10 event.
Publication history
- 2026-09-10Student Success · Issue 052 resources
Stable resource ID: du-yuan-epistemic-dependence-review-2026