Challenge · 01
Content scale
practice banks and curriculum metadata need consistent schemas and administration.
<- AI Systems Dossier
ENTRY NO. 03Technical learning product demoDemo availableFastAPI / React / curriculum / RAG configurationLEARNING PLATFORM / DEMO AVAILABLE
Nullfal
Identity · Practice and retrieval system
AI learning product with practice tracks, RAG explanations, progress events, and a live demo.
FastAPI / React / curriculum / RAG configuration
Evidence boundary
What is demonstrated, and where the claim stops.
Recorded testRepository factConfiguration
What this proves
- /A working learning product can combine curriculum administration, practice content, progress events, and retrieval configuration.
- /A dated repository artifact records passing API coverage for the tested endpoints.
- /The checked-in test dataset contains five tracks and 1,061 microdrills.
What this does not prove
- /Improved learner completion, retention, or mastery.
- /Psychometric validity or cohort-scale learning outcomes.
- /Published grounding quality or latency performance for the RAG layer.
Data boundary
A product demo backed by checked-in curriculum content and dated test artifacts. Learning outcomes have not been validated at cohort scale.
Evidence type
recorded test / repository fact / configuration
Learning outcomes and psychometric performance have not been validated at cohort scale.
Known limitations
- /The current README is not yet a complete one-command product quickstart.
- /RAG evaluation code exists, but no current result artifact is published.
- /The recorded test result is dated and is not a production service guarantee.
What production would require
- /Isolated demo identities, hardened code execution, and governed content workflows.
- /Repeatable end-to-end tests against seeded data and saved RAG evaluations.
- /Cohort instrumentation and a defined learning-outcome evaluation design.
Problem
Technical practice content, progress events, and reference retrieval need one coherent product workflow.
System Flow
4 stages · click to inspect
->
->
->
Click any stage to inspect
Signature Module · Practice and retrieval system
Inspect practice and retrieval
See how curriculum content, executable practice, progress events, and configured reference retrieval fit together.
Nullfal · practice and retrievalinspectable
CONTENTtracks · quests · microdrills
PRACTICEattempt · feedback · explanation
EVENTSprogress and learning analytics
RAG768-dim · 1,200-char · top-k 8configuration
BOUNDlearning outcomes not yet validated
Demonstrated Change
Demo scopeBefore
Curriculum, practice, progress, and reference material handled as separate concerns.
->
Demonstrated build
One demo product with tested APIs, structured practice content, and a configurable retrieval layer.
The demo brings authentication, tracks, quests, microdrills, analytics, and retrieval-backed reference flows into one product surface.
Learning outcomes and psychometric performance have not been validated at cohort scale.
Proof Signals
Classified evidence1,061
microdrills in test data
Recorded test
5
tested learning tracks
Recorded test
25/25
API tests passed
Recorded test
Every signal is classified as a repository fact, recorded test, configuration, or disclosed data boundary.
Why This Is Hard
3 engineering challengesChallenge · 02
Execution safety
coding exercises require clear sandbox boundaries before broader use.
Challenge · 03
Outcome honesty
product activity must not be presented as validated learning impact.
Engineering Depth
3 topics · click to expandThe repository includes authentication, curriculum administration, tracks, quests, microdrills, analytics endpoints, and a React frontend.
Key numbers
768-dimembedding configuration
1,200-charchunk configuration
Built withFastAPIReactMongoDBQdrantPython