Supabase: L&D courses, modules, and progress

Audience: L&D program owners, CSOs, anyone interpreting Forge / reporting data
Status: Active (2026-04-13)
Technical deep dive: knowledge/platform/docs/ld-supabase-learning-schema.md


Why this exists

The database now matches the course → module → lesson mental model we use in curriculum design. Platform ticket PLT-1284 tracks the schema work.

Lesson-level rows are not in Supabase yet; lesson content stays in this vault under programs/courses/. Next steps on the product side (lesson progress, vendor certs) remain in the Platform handoff.


What is stored today

ConceptIn SupabaseExample
Courselearning_coursesfoundation, accelerator (one row each today).
Modulelearning_modulesQuickstart: M1–M5. Accelerator: DB rows may still use A1–A2 module codes while product reporting catches up to the six-module AI Accelerator vault course.
Link module → courselearning_modules.parent_courseEvery current module points at the course that matches its track.
Progresslearning_progressOne row per person per course or per module (never both on the same row).

Important: The old table module_progress was removed. Anything that queried it must use learning_progress with module_id set for module-level progress.


How to think about reporting

  • “Where is someone in the Quickstart course?” — Still driven by module-level rows in learning_progress (and, when we add it, lesson-level data). The summary view team_learning_summary continues to use module rows for “modules completed” and “current module.”
  • “Did someone start the course as a whole?” — Can be recorded with a course-level row in learning_progress (course_id = Quickstart course, module_id null) when the product writes it; not required for existing summary logic.
  • Vendor certifications — Not modeled in these tables yet; see the handoff doc for the intended states when built.

Seeds (current courses)

course_codeMeaning
foundationBrainforge AI Quickstart
acceleratorBrainforge AI Accelerator (prerequisite: Quickstart course in DB)

Who to ask

  • Schema / API / Forge: Platform team (#engineering or L&D’s thread with Platform).
  • Curriculum structure: L&D (Brylle) — ../README.md.

Last updated: 2026-04-13