Concept, answer, evidence line, XP, and what the learner did next.
What learners
can prove.
Dungeon Academy should be fun, but the fun needs evidence behind it. Each room should leave a proof trail a parent can understand.
Progress means explanation, transfer, and a record families can read.
Strengths, focus area, proof examples, and parent-readable next steps.
Five related proofs plus a short mastery statement.
Twenty-five proofs, five credits, capstone notes, and readiness for the next realm.
Printable or downloadable artifacts once backend export is hardened.
The learning loop in normal words
The promise is not “your kid clicked through a game.” The promise is that each room turns play into visible thinking: a challenge, a proof, a reflection, and a parent-readable next step.
A room gives them a problem, story pressure, tools, hints, and a reason to care.
The report says what concept was practiced, what proof was made, and what to try next.
Evidence across rooms shows whether the learner can explain, transfer, and repair mistakes.
Artifacts become a family-visible trail: diagrams, reflections, prototypes, model cards, and capstones.
Five competencies in the first realm
Choose operations, model quantities, explain units, and check whether an answer is reasonable.
Rune math receipts, diagram notes, fairness checks, and answer defenses.
Make observations, compare variables, support claims, and name what evidence does or does not prove.
Claim-evidence cards, experiment notes, variable checks, and lab reflections.
Trace force, motion, energy, light, and cause-effect before choosing a result.
Motion sketches, prediction logs, unit labels, and rule explanations.
Define constraints, test a prototype, find weak points, and explain a better revision.
Prototype briefs, stress-test notes, failure analysis, and improvement plans.
Recognize patterns, question training examples, explain predictions, and notice unsafe or unfair outputs.
Oracle audits, feature labels, example sets, model cards, and safety notes.
Outcomes should become artifacts, not vague confidence
Kids remember what they build. Parents trust what they can inspect. These are the proof objects each subject should keep producing.
Show the operation, unit, diagram, and reasonableness check behind an answer.
Write a claim, name the evidence, separate observation from guess, and explain limits.
Build or sketch a prototype, test what failed, then propose a better version.
Explain what a model used, where it might be unfair or wrong, and how to check it.
Combine several rooms into one project with proof, reflection, vocabulary, and next steps.
What counts as ready
Needs a model, hint, or second example before the proof is stable.
Solves the current challenge and can name the main rule or evidence.
Gives a parent-readable why, catches common mistakes, and uses correct vocabulary.
Applies the same habit in a new room, subject, or harder puzzle.
Combines multiple ideas into a project, packet, or final mastery defense.
Before moving forward, check the proof trail
The learner has heard the model, tried one guided move, and gathered enough evidence.
The record has a concept, proof line, learner action, and parent-readable next step.
The learner can explain the why without racing past the evidence.
The STEM record shows proof habits, stamina, and curiosity for deeper work.
Credibility means saying what is real now
This page describes the beta enrichment outcomes and evidence model; formal accreditation claims are not made.
Transcript-style records are product artifacts until policy, consent, exports, and account recovery are production hardened.
Reports should be understandable without forcing parents to decode game mechanics.
The rubric should help families choose pace, not push kids into empty streaks or anxiety loops.
Teach the idea, gather proof, then report what changed.
This page turns the fantasy school into a clearer academic promise: every playful room should produce evidence, language, and next steps.
