From the Student Success edition of September 29, 2026
Argus CS2 study: 45.7% Spring 2026 homework patterns flagged as LLM-assisted; exam correlations worsen
Purdue University (Racovan, Rawat, May, Turkstra) · Higher education computer science / academic integrity · United States (Purdue University large-enrollment CS2)
- Publisher
- arXiv
- Original publication
- Submitted to arXiv 28 September 2026 (cs.CY)
- Source retrieved
- 2026-09-30
What happened
Argus combines behavioral and stylistic indicators to surface possible LLM-assisted C programming homework across six Spring CS2 offerings. In Spring 2026, 267 of 584 students who completed the first midterm (45.7%) were flagged after manual review. Average H-scores were negatively correlated with performance on in-person closed-note exams, with correlations strengthening in more recent offerings. Authors stress that erroneous accusations carry high stakes and that any automated detection system must include structured human review; H-scores are a behavioral proxy, not verified proof of AI use.
Why it matters
Critical scrutiny companion to GenAI tutoring/adoption expansions: large-course homework assistance patterns are common, associate with weaker proctored performance, and demand due-process human review—not automatic discipline dashboards. Student-success leaders should pair AI help tools with assessment redesign and integrity processes that protect students from false positives.
Evidence and measured results
Longitudinal static-analysis of anonymized CS2 homework across six Spring offerings with the same instructor; Spring 2026 deployment with manual review of flags; correlations of H-score to midterm/final exam percentages. Observational; preprint.
Limitations and uncertainty
Single course/instructor; proxy labels; false-positive risk acknowledged; correlations ≠ proven causation of learning loss; CS2 C-programming context; preprint.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-30; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Large CS courses see widespread suspected LLM homework help while needing fair integrity processes and unaided learning measures.
- Stakeholders
- CS department
- academic integrity office
- provost
- student success
- teaching & learning
- Discovery questions
- What share of graded work is take-home vs proctored?
- Who reviews integrity analytics before student contact?
- How do AI tutor policies interact with homework rules?
- Value hypothesis
- Human-reviewed integrity analytics plus assessment redesign can surface learning risk without automatic misconduct findings.
- Potential engagement
- Shadow-mode Argus-like review for one CS2-style course with documented human-review SLA and exam-outcome monitoring.
- Unsupported claims
- Verified individual AI use from H-score alone
- Causal proof H-score causes exam decline
- Cross-course detector portability without revalidation
Pre-sales engineering
Role takeaway
- Fit
- Large programming courses with versioned homework submissions and separate proctored exams.
- Architecture and integration
- Submission ingest → feature/H-score service → instructor review queue → SIS/conduct only after human decision; audit trail.
- Prerequisites
- historical homework corpus
- instructor review capacity
- clear academic-policy mapping
- Constraints
- proxy not ground truth
- false positives
- single-instructor evidence base
- Security
- Code and scores as education records; least-privilege reviewer access; no auto-sanction API; retention limits.
- Proof of value
- Manual-confirm rate among flags
- Time-to-review SLA
- Correlation monitoring without auto-discipline
Delivery
Role takeaway
- Work
- Configure detector, train reviewers, communicate policy to students, redesign assessments where needed.
- Dependencies
- faculty time
- integrity office procedures
- student appeal channels
- Ownership
- Course instructor of record with academic integrity office for escalations.
- Skills and adoption
- Reviewers interpret behavioral proxies; students taught legitimate vs prohibited AI help.
- Governance checkpoints
- Policy sign-off before flags contact students
- weekly false-positive review
- end-term process audit
- Acceptance criteria
- No misconduct finding without human review
- Published student-facing AI homework rules
- Proctored measures retained for competence
- Risks
- Mass accusations
- Chilling effect on help-seeking
- Over-trust in H-score
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?
If deploying integrity analytics, separate detection scores from disciplinary workflows; require human-review queues, explainable features, and audit logs. Prefer assessment designs (proctored/written) that measure unaided competence alongside homework help tools.
Governance
Who approves, reviews and stays accountable for outcomes?
Policy must forbid sole-reliance on automated LLM-use flags for misconduct findings; publish review SLAs and student appeal paths. Align AI-tutor permissions with graded-work rules so help-seeking design does not silently become an integrity trap.
Security and privacy
What data, permissions and controls need testing?
Homework and behavioral traces are sensitive education records. Minimize retention of full code in detector pipelines; restrict access to instructors/conduct officers under school-official rules; guard against biased false positives in large courses.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
False-positive integrity flags can disproportionately harm students without advocacy capital; human review and clear appeal paths are equity requirements. Faculty workload for review is a real staffing cost of detection.
Procurement
What should contracts, pricing and exit terms secure?
Do not buy integrity products that auto-accuse. Require human-in-the-loop workflows, explainability, and independent evaluation on local corpora. Separate tutoring-tool procurement from detection-tool procurement with aligned policies.
Operating model
Which teams own the service once it runs?
Operate GenAI student help and integrity analytics as linked but gated systems: help tools with progressive assistance; detectors with review queues; proctored assessments as competence anchors.
Publication history
- 2026-09-29Student Success · Issue 233 resources
Stable resource ID: racovan-argus-llm-assisted-cs2-integrity-20260928