Maths Map

Loading…
Loading…
Help — how this works & commands

Process flow

  1. Your child does a session on their own page — each answer saves straight to the database as they go.
  2. Finishing marks it submitted, waiting to be graded.
  3. Running /grade fetches that session and hands it to the grader — it marks every answer, diagnoses the wrong ones, and decides the verdict and what should happen next, reading the whole history on the topic, not just this one session.
  4. That grading is saved immediately — marks, feedback, and progress are never left waiting on what gets built next.
  5. The next session gets built: a full step-by-step lesson when something needs re-teaching, otherwise a practice, check or retest session at the right level.
  6. It's checked two ways — an automatic answer-key check, then an independent cold re-solve — before it's queued. A clean pass queues it automatically; anything doubtful (or a backtrack to an earlier topic) is held for review first.
  7. The new session goes to pending, ready for your child next time they open their page.

Commands

/grade Grade whatever has been submitted and queue what's next — the everyday command.
/next-session Build the next session when nothing is waiting to be graded (first session, or after a gap).
/status Read-only progress check — no changes made.
/setup-child Research the curriculum and set up a child's profile and topic list.
/run Start the local dev server for this dashboard and the child's session page.
/reset-child Dev/testing only — wipes sessions and progress for a clean re-test, keeps the approved topic list.