cr
ClassRoots Content One place for the whole team
Curriculum & content workbench

Every chapter, from objectives to published journeys.

Four platforms build each chapter of CBSE maths, Grades 4 to 10. The Knowledge Graph writes its objectives and checkpoints. The Asset Platform holds the videos, applets and questions that teach them. Books reads every book for its questions. The Journey Relay builds and publishes the journeys. Each keeps its own stage; this page shows how they join.

ax
Asset Platform
assets.classrootsedu.in

The catalogue of every video, applet, lesson, journey and question across products, each described and searchable by meaning.

Hands on: the asset catalogue, keyed by content_key.

Open the Asset Platform →
kg
Knowledge Graph
kg.classrootsedu.in

The curriculum spine. Each chapter's subtopics, objectives and checkpoints are written from the book, approved by an SME, then tagged with their assets.

Hands on: the published chapter, keyed by objective id and checkpoint uid.

Open the Knowledge Graph →
bk
Books
books.classrootsedu.in

Every book we hold, read page by page, with each printed question and answer kept as printed. Practice lives here too: the question bank SMEs pass, and the engine that serves it.

Hands on: the question bank (qb_id) and the passed practice bank.

Open Books →
jr
Journey Relay
buildjourneyrelay.classrootsedu.in

Where journeys are built, one approved stage at a time: chapter pass, scope, spine, storyboard, build, then a UAT publish a person plays and approves.

Hands on: approved, published journeys, keyed GxxCxxSTnJn.

Open the Journey Relay →
The chapter pipeline

How the pieces come together

The goal is 96 chapters closed. A chapter closes when its journeys are published and its question bank is passed and live. Three rules hold the platforms together without merging them.

Each keeps its stageA platform is the record for the stage it owns. Nothing is rebuilt elsewhere.
One handoff eachEach platform hands on one thing, under a stable key, through a route others read.
Nobody writes into anotherA platform reads what it needs. A gap is fixed inside the platform that owns it.

Chapters to close

G414
G515
G610
G715
G814
G914
G1014
Total96

From the Knowledge Graph's chapter registry, 2 Nov 2026. G7 and G8 count both book parts.

What a chapter is, to a learner

The checkpoint is where everything meets. A journey teaches a subtopic's checkpoints; the question bank secures each one; a learner stuck in practice goes back to that objective's journey.

CHAPTER Fractions CBG06P1C07 one of 96 SUBTOPICS 7 in G6 Fractions a stretch of the book taught as one unit OBJECTIVES L-NM-351 … in teaching order, built on earlier ones CHECKPOINTS knowledge L1 · L2 · L3 stretch one skill each, a fixed six-digit uid shown as 356.2 splits holds checked by LEARN · JOURNEY cover → 3–5 nodes → takeaway each node: hook → encounter → apply a subtopic is cut into one or more journeys made from videos, applets and lessons on the asset platform, plus new applets all adaptivity lives inside the applets G06C07ST2J1_<slug> PRACTISE · QUESTION BANK questions on every checkpoint four forms for every question: own · options + hint · steps · see it done picks the next set after each answer secure: every objective right at top level minimums per checkpoint: 15 · 15 · 8 · 1 · 4 L1 · L2 · L3 · knowledge · optional taught by secured by stuck? open the objective's journey THE BOOK'S PAGES · SOURCE OF TRUTH The KG writes every objective from the printed pages; Books extracts their questions and answer keys; the relay re-reads the pages for each subtopic before it cuts journeys. written from questions
One chapter as a learner meets it. Checkpoints sit between the objectives and both learner paths.

How a chapter gets built

Books and the Asset Platform prepare their material on their own clocks, ahead of any chapter. The Knowledge Graph works one chapter at a time and publishes it. Then the question bank and the journeys run side by side, and both must finish before the chapter closes. The orange marks are the joins still being made, lettered as in the table below.

BOOKS · OWN CLOCK KNOWLEDGE GRAPH · ONE CHAPTER ASSET PLATFORM · OWN CLOCK Register the book catalogue · dedupe · item_id Read the pages page map · units · figures Extract questions as printed, with answer keys Question bank merged across books · qb_id List from the CMS census · scope confirmed Brief each asset video · applet · lesson · question Embed and serve vectors · search · tree Asset catalogue content_key Register the chapter admin · thread, strand, SME Skeleton subtopics, objectives, order · Agents 1 + 2 SME sitting 1 · confirm skeleton Ladders checkpoints + the book's questions · uid Strand pass links across grades · Agent 4 SME sitting 2 · approve objectives Tag assets to subtopic + checkpoints · Agents 3 + 2 SME sitting 3 · sign off Published chapter what every line downstream reads · objective id · checkpoint uid d searched live QUESTION BANK JOURNEYS · RELAY by checkpoint uid read live Gather questions Books · KG · tagged pool · new Place on a checkpoint keyed by checkpoint uid Write the four forms hint · steps · see-it-done script SME passes · tagging + content b Bank complete minimums met on every checkpoint Chapter pass the steward reads the whole chapter Scope each subtopic pages + assets → cut into journeys Spine, storyboard, build learner flow · applets rebuilt Played in UAT · approved Journey published UAT, then PRD by engineering questions by qb_id tree + vector search, live e list what we made c Practice live the engine serves the passed bank Chapter closed
Time runs down the page. Sources are prepared once and reused across chapters; the Knowledge Graph runs per chapter with three SME sittings; after publish, the question bank and the journeys run in parallel.

What closed means

A chapter closes when all five are true, in this order. Steps 3 and 4 run side by side once step 1 is done.

  1. STEP 1ObjectivesThe chapter is signed off and published in the Knowledge Graph.The SME, at sitting 3
  2. STEP 2AssetsEvery subtopic has its assets tagged, with the checkpoints each teaches.Agents 3 and 2; the SME looks
  3. STEP 3QuestionsEvery checkpoint meets its minimum, each question passed for tagging and content.An SME or the admin
  4. STEP 4JourneysEvery journey the scopes cut is played and approved in UAT.Its creator, then the steward
  5. STEP 5LivePractice serves the chapter from the passed bank; journeys move to production.The admin; engineering

What each platform hands on

Nothing downstream reads a platform any other way, and no platform writes into another.

PlatformOwnsHands onKeyOwner
Knowledge Graphobjectives, checkpoints, asset tagsthe published chapterlo_id, checkpoint uidVinay, with each chapter's SME
Asset Platformlisted, described, searchable assetsthe asset cataloguecontent_keyVinay
Booksbooks, their pages, printed questionsthe question bankqb_idKishor
Practice (in Books)the served bank, its SME passes, the enginequestions passed on a checkpointquestion id + checkpoint uidVinay
Journey Relayjourneys, chapter pass to UAT publishapproved, published journeysGxxCxxSTnJn + CMS idAswin

The keys everyone joins on

Every handoff names a chapter by its Knowledge Graph code and a checkpoint by its uid. Display numbers are for people; no system joins on them.

ThingCanonical keyOther forms in use today
ChapterCBG06P1C07the KG's long id, G06C07 in the relay, G6-C07 in practice, Books' PREV- records
Objectivelo_idL-NM-356, readable and issued once
Checkpointsix-digit uid, e.g. 100037display 356.2, which moves when a ladder changes
Assetcontent_keyPRAC- for some practice questions
Bank questionbank question id (qb_id for a book question)BOOK-Q-…
JourneyG06C07ST2J1_<slug> + its CMS idnone

Joins being made

Each is a small change inside the platform that owns it, made by its owner. Until each lands, the step it proves can't be shown from data alone.

ChangePlatformOwnerProves
aWrite logins for practice passes and the Books Review Room; read-only logins for readersGateway (mcp-db)to be namedunblocks b
bPractice serves only passed questions; one pass store in sandbox_dbPractice, BooksVinay, Kishorsteps 3 and 5
cA "created by ClassRoots" source, so bank questions and journeys are listed as assetsAsset PlatformVinayreuse by key
dA version stamp on the published chapter, with a "changed since" readKnowledge GraphVinaywhen a copy is stale
eJourney questions carry their bank question idJourney RelayAswinwhich bank questions a journey uses

Next on this page: a live board of all 96 chapters against the five steps, read from each platform without changing any of them.