, Priya 👋
You're at the top of the supply chain — everything you author here ships downstream to students across live cohorts. drafts are waiting on you.
across live cohorts
Tracks — the catalog
A track is a bound curriculum: a set of outcomes, mini-courses and assessments that cohorts subscribe to. Each carries a target pillar — the verification hook downstream.
Edit metadata, reorder the milestone path, attach mini-courses, and set the target pillar. Publishing pushes this track to bts_tracks so it appears in the Student app.
▶ Students play this the moment you publish · video id
Each chapter becomes a lesson the student plays, deep-linked to its timestamp — concepts divide exactly like the YouTube chapter list.
Completing this track yields a verifiable refId the student can escalate to faculty.
Cohorts
A cohort delivers a published track to one class — its students, instructor, and schedule. Create the cohort, then assign the roster that receives the content.
Mini-courses
The consumable lesson unit — video, text or quiz — that the Student course player renders. A track bundles several.
Library
One cross-cut catalog over everything Studio has shipped — tracks, mini-courses, cohorts and quiz banks.
Analytics
How shipped content performs — engagement, the completion funnel, and per-cohort progress. In the real build these reverse-read Student completion signals.
| Cohort | Track | Students | Completion |
|---|---|---|---|
Sample profiles
Generate PII-clean demo student profiles for QA and walkthroughs. Every record is flagged is_sample = true.