Every concept, connected.
Explore relationships between ideas, select a concept, and move from the map into a source-grounded learning session.
Concept
Explore this concept in your course material.
Understand the why.
Ask questions about indexed material. Inspect source locations and challenge an explanation when the evidence is insufficient.
A fluent answer is not necessarily a supported answer. Inspect the quoted excerpt and its source locator before relying on it.
If indexed passages cannot substantiate the question, LUMEN should state the limitation instead of presenting an unsupported claim as course fact.
After practice, inspect the answer, grading criteria, source location, chosen intervention and any update to the learner estimate.
Test what you know.
Answer source-derived questions, inspect the grading criteria and review the source location. LUMEN updates a transparent topic estimate after submission.
Your source library.
Import supported materials, check ingestion results, and confirm the engine indexed usable text before beginning a grounded session.
Each citation should identify the originating file and page, slide, paragraph or timestamp. Extraction quality still affects answer quality.
Think in functions.
Plot a function, change its parameters and inspect how the curve behaves. This self-contained graphing workspace works without an external graphing API key.
Change the expression and coordinate, then predict how the curve changes. Use a course-grounded question in Learn to connect this exploration to your material.
Progress, with context.
Review recorded practice and transparent topic estimates. A prior estimate is not proof of mastery; interpret each score alongside attempts and uncertainty.
Confidence intervals are approximate summaries under a simple model.
A diagnosis requires a supported pattern, not a single wrong answer.
Observed correctness does not establish durable retention or transfer.
Evidence of quality.
Inspect live workspace counters and the documented evaluation protocol. Reproducible benchmark results must be generated by the test runner, not fabricated by the interface.
Measure whether known-answer queries retrieve the expected source chunk; report Recall@k and MRR with the test-set size.
Test answerable questions, unrelated questions, misleading term overlap and unsupported answer types.
Test answer keys, numerical tolerances, units and short-answer grading agreement.
Check that recorded answers update the expected topic and that changes do not break existing behavior.
From the project directory, install requirements and run the automated tests. Evaluation results should be regenerated against the exact release candidate.
python -m pytest -q python evaluate.py
Passing curated fixtures shows behavior on those fixtures only. It does not prove general accuracy or educational effectiveness.