Cruxion glossary

Plain-language definitions of the terms used across Cruxion, the AI-native engineering education platform. Each entry explains one concept in a sentence or two.

AI-native engineering education

An approach where students build with AI from the first semester and are verified to actually understand what they built, rather than AI being treated as something to detect and penalize or added as a final-year elective. Cruxion is built around this approach for Indian engineering colleges.

Understanding Verification

Cruxion's core mechanism for confirming that a student understood an assignment, not just that the code ran. After a submission passes automated tests, a Socratic AI mentor asks follow-up questions tied to the student's own code, and the student has to explain their own approach.

Understanding Score

The score Cruxion records from Understanding Verification. It reflects how well a student could explain and defend their own work, and it is separate from whether the code merely executed correctly. Progress through the curriculum depends on it.

Socratic AI mentor

The AI assistant in the Cruxion workspace. Instead of handing out answers, it asks guiding questions when a student is stuck, and after code passes it asks the verification questions that reference the student's own variable names and specific approach.

Apprentice tier

The first of Cruxion's three tiers. Apprentice builds foundations through interactive lessons where every concept is a small experiment, establishing understanding before fluency.

Engineer tier

The middle tier. Engineer is where students write code that runs and passes tests inside the three-pane workspace, with the Socratic AI mentor and Understanding Verification confirming they can defend every line.

Architect tier

The most advanced tier. Architect moves from writing functions to designing systems: cloud-native service design on AWS, GCP, and Azure for the CS track, and cloud-connected hardware for the EC track.

CS, ISE and AIML track

Cruxion's software track, covering Computer Science, Information Science, and AI and Machine Learning branches. It runs from foundations through coding with a Socratic mentor to system design and cloud engineering.

EC, ECE and EEE track

Cruxion's hardware track, covering Electronics and Communication, Electronics, and Electrical branches. It runs from a visual component lab and embedded C through to cloud-connected IoT systems built on real cloud infrastructure.

Three-pane workspace

The Cruxion coding environment: a problem statement on the left, a code editor in the middle, and the Socratic AI mentor on the right, together on every assignment.

Progressive hints (hint tree)

A curated set of graduated hints faculty can shape for an assignment, so guidance reflects where their own students actually get stuck rather than giving away the answer.

AST-based plagiarism detection

A check that compares the structure of student submissions, using the abstract syntax tree rather than surface text, to flag structurally similar work for faculty review instead of auto-penalizing students.

Cruxion Pulse

The daily-engagement layer of the platform. Pulse uses a short daily task feed, spaced-repetition review, streaks, badges, and a live section leaderboard to keep students practicing between graded assignments.

Section leaderboard

A live ranking that shows students how they stand against their own section, turning daily practice into something social rather than solitary.

Pilot

A scoped first deployment of Cruxion, usually starting with a single department or course section, so faculty and students can see the platform in real use before it expands.