Everything the team builds, in one place.
The knowledge graph holds the curriculum — learning objectives, concept graphs and journeys. The asset platform holds every video, question and interactive the team has produced, with its description and embedding status. Two systems, one login, one shared vector space so an SME can see the structure and the content it teaches together.
The curriculum spine. Where learning objectives, concept graphs, misconceptions and journeys are authored, reviewed and signed off by SMEs.
- LOs, KGs & journey listings by grade and chapter
- Misconceptions, worked examples, teaching guidance
- SME review, tagging & sign-off workflow
The content catalogue. Every video, practice question, journey and interactive across products — each described, embedded, and tracked from listing to final.
- Full catalogue by product, syllabus, grade & kind
- Extraction pipeline: transcribe → describe → embed
- Descriptions, timestamped moments & embedding status
▸ How the two fit together
The two platforms stay separate systems — the KG authors the curriculum, the asset platform is the catalogue and the embedder. They are joined by one thing: the tag that links an asset to the LO or journey it teaches.
One embedding engine embeds everything into the same vector space — assets, their timestamped moments, and (read from the KG) LOs and journeys — so a student's question, the LO it maps to, and the asset that answers it are all directly comparable. That is what lets the right thing surface: a whole journey when the doubt is structural, a single video moment when it's specific, a filtered list when it's practice.