What is Understanding Verification?
Understanding Verification is a step Cruxion runs after a student's code passes, designed to check whether the student understood what they built, not just whether it ran. It exists because AI tools make it trivial to produce working code without understanding it, and a grading system that only checks output rewards that shortcut. Understanding Verification is built to reward comprehension instead.
How it works
Code passes automated tests
A student submits an assignment and it passes the standard automated checks. This is where most platforms stop.
The AI mentor asks follow-up questions
A Socratic AI mentor asks three questions about the submission, referencing the student's own variable names and their own specific approach, not a generic template question.
The student explains their own work
Because the questions are tied to the exact code submitted, a student who copied a solution or had AI generate it without understanding it cannot answer convincingly.
An Understanding Score is recorded
The result feeds an Understanding Score that determines whether the student progresses, separate from whether the code merely executed correctly.
Why this matters for AI-native education
An AI-native curriculum assumes students will use AI to build, that is the point. The open question is whether they understand what they shipped. Understanding Verification answers that question directly, on every assignment, instead of relying on occasional spot checks or trusting that a passing test is proof of learning.
See Understanding Verification in a real classroom
Start a pilot with a single course section and see how it changes what students actually learn.
Request a pilot