Learning Twin
The substrate. Per-topic mastery + Bloom's level + Lexile + accommodation context, updated after every submission. Nothing else in the AI surface runs without it.
Loading...
Most “personalised” ed-tech sorts students into bins and calls it a day. CurioPilot builds a per-subject mastery model — the Learning Twin — and calibrates every activity, hint, and recommendation against it.
Most “adaptive” ed-tech sorts a child into one of three buckets — easy, medium, hard — based on a single quiz score. Then it serves the next activity from that bucket. That’s not personalisation; that’s a difficulty knob with a smile.
Real personalisation needs a per-topic, per-subject, per-Bloom’s-level mastery model that updates after every interaction. It needs to track what kind of mistakea student just made, not just whether they got it wrong. It needs to know that “ignored remainder in long division” is procedural, fixable in two minutes; “doesn’t grasp fractions as parts of a whole” is conceptual, weeks of work.
That’s the Learning Twin. It’s not a marketing layer; it’s the substrate the rest of the AI features run on.
Five nodes, run on every activity. Every iteration writes to TraceLayer.
Submission + hint requests captured.
Bloom's classifier + misconception detector run on the submission.
Per-topic mastery + Lexile + accommodation context refresh.
Next 3 topics surface with a 'why' tooltip.
Difficulty, format, and reading level pinned to ZPD.
Each feature is consent-gated and audit-logged. The shield means it’s enforced in code by TraceLayer.
The substrate. Per-topic mastery + Bloom's level + Lexile + accommodation context, updated after every submission. Nothing else in the AI surface runs without it.
Pulls the student's current ZPD, Lexile, and active misconceptions, then drafts a 5–10 item set calibrated to the next-best topic. Teacher edits + approves before a student sees it.
Hints, not answers. Subject-scoped, Bloom's-aware. Walks through reasoning step by step when a student is genuinely stuck — but won't write the essay or do the maths.
Inline feedback on argument structure, evidence, and clarity. Never rewrites the student's voice. Surfaces specific reverse-outline suggestions a teacher can adopt with one click.
30/60/90-day topic plans drafted from the Twin, with a 'why this order?' rationale per step. Re-plans automatically when mastery jumps or stalls.
One architecture, three audiences. All three pass through the same consent gates. All three log to TraceLayer.
Hint-giver, never answer-giver. Subject-scoped, Bloom's-aware. Will walk through reasoning step by step when a student is genuinely stuck — but won't write the essay or do the maths.
Plain-English chat for parents. "What did Maya struggle with this week?" "Why is this activity recommended?" One-click actions: schedule a check-in, switch to a calmer topic, change the consent state.
Friday digest with six action cards ranked by impact. Drafts reteach lessons, parent updates, conference briefs. Teacher edits + approves; nothing leaves the platform without a human signing off.
Every “won’t” below is enforced in code, not just policy. Most of them refuse to compile if violated.
Each item above is enforced by TraceLayer + the build-time PII attestation. Read the full compliance posture at /compliance.
After every submission. The Bloom's classifier and misconception detector run on the response, then per-topic mastery, Lexile, and accommodation context refresh in roughly 800ms. Every update writes a row to TraceLayer with the input hash, model version, and confidence score.
30-minute walkthrough with you, your IT, and your DPO. We’ll build a Twin from a sample student dataset and show you how it updates in real time.