Built for curious children who like puzzles, stories, science, math, making, and big ideas.
How Dungeon Academy
teaches, tests, and records.
A plain-language guide for parents: what kids do each day, how proof is assessed, what records mean, and what remains beta before broad enrollment.
25 teach-first rooms across math, science, physics, engineering, and AI foundations.
The $19/month family membership unlocks the full school, reports, planning, and saved records.
Proofs, weekly reports, credits, and mastery packets are designed for family review.
The same calm structure in every room
Professor Lyra introduces one idea with a model, vocabulary, and mistake shield.
Kids hear the rule before being tested.
A short guided check asks the learner to try the thinking move once.
The test stays locked until practice has happened.
The learner inspects room artifacts and gathers evidence.
The fantasy scene becomes a proof lab, not just decoration.
A dragon test asks for the same idea in a higher-stakes problem.
The challenge is meant to feel exciting, not random.
The answer files proof into the learner's academy record.
Parents can review what was learned and what comes next.
What counts as learning proof
A saved answer, evidence line, XP, and transcript entry.
A parent-readable summary with strengths, focus, and evidence cards.
A mastery artifact and rubric-style proof record.
Twenty-five proofs, five credits, and a capstone packet.
The product rules we keep building toward
Every serious challenge should have a lesson, model, practice step, and evidence path before assessment.
Progress should be based on explainable artifacts, not empty points or pressure loops.
Dragons, music, voice, art, and animation should make concepts easier to remember.
The school layer should give families plain-language reports, exportable records, and safety context.
When a system is temporary, manual, local, or unfinished, the product should say so clearly.
Who does what
Play the room, listen to the lesson, try the model, gather proof, and file the record.
Start with the demo, review the safety charter, decide on paid access, and check reports.
Provide lessons, media, feedback, parent records, and a safer path from beta to full school.
What parents should know right now
Full learning rooms, reports, and saved records should open only through parent-managed membership and confirmed entitlement.
Parent dashboard and learner records are in beta and should mature before broad enrollment.
Safety, privacy, and terms pages are public now; deletion, retention, vendor, and refund language still need professional review before major scale.
AI art, voice, sound effects, and animations are already present, with higher-end refreshes planned.
Use friction as signal, not failure
Replay the lesson, ask what the room is asking, and let them describe the first clue without answering yet.
Pause before the dragon test and ask for one evidence sentence: what changed, what did you notice, or what rule applies?
End the room after the reflection. A calm stop preserves the next session better than forcing completion.
Move toward harder proof, creative artifacts, logic, writing, or maker realms instead of adding repetition.
What to do before, during, and after class
Choose one room, set a short time box, and make sure the child knows hints are allowed.
Do not take over the mouse. Ask evidence questions only when the child is stuck or rushing.
Ask the child to show the proof artifact, then note confidence, curiosity, and next-step readiness.
Review the report, choose whether to slow down, keep pace, or move into a deeper path.
Read the guardrails, try the room, then choose membership.
The handbook is the parent-readable operating guide. The safety charter covers privacy posture, and enrollment explains the current paid beta gate.
