Brainforge Knowledge

ld-supabase-progress-tracking-handoff

3 min read

L&D Progress Tracking — Platform Handoff

Status: Handoff (non-technical product brief)
Owner: L&D (Brylle Girang)
Audience: Platform team
Last updated: 2026-04-13

Schema implementation status (2026-04-13)

The course → module layer is live in Internal AI Core (same Supabase project as team), under PLT-1284:

  • learning_courses — course catalog (seeded: foundation, accelerator).
  • learning_modules.parent_course — links each module to its course.
  • learning_progress — unified progress table (replaces module_progress); rows are either course-scoped or module-scoped.

Platform reference: knowledge/platform/docs/ld-supabase-learning-schema.md
L&D summary: knowledge/people/learning-development/engineering/supabase-progress-schema.md

Remaining from this handoff (not in PLT-1284): lesson-level tables, vendor certification progress, optional dedicated brainforge-ld project if we split workloads later.

What we need built

A dedicated Supabase project (brainforge-ld) wired into The Forge platform to track team member progress across the Foundation course and Vendor Certifications.

Note (2026-04-13): L&D catalog and progress currently live in Internal AI Core; a separate brainforge-ld project is still optional and not provisioned in the org list used for MCP. Treat the note above as the interim hosting decision until Platform splits projects if needed.

The four questions it must answer

  • Who has started? — team members who opened at least one lesson or cert page
  • Where are users? — which lesson within which module each person is currently on
  • Who completed modules? — team members who finished all lessons in a given module
  • Who completed a course or certification? — team members who finished all modules in a track, or passed a vendor exam

Content structure to track

Foundation Course (Course → Module → Lesson)

8 modules, 30 total lessons:

  • Module 1: Cursor + GitHub Setup (3 lessons)
  • Module 2: Delivery Standards × AI (3 lessons)
  • Module 3: Cursor Deep Dive (8 lessons)
  • Module 4: GitHub for Brainforge (5 lessons)
  • Module 5: The Forge (4 lessons)
  • Module 6: Cloud Agents (2 lessons)
  • Module 7: Applied Task (2 lessons)
  • Module 8: Certification (3 lessons)

Plus optional Accelerator modules (A1: 4 lessons, A2: 4 lessons).

Vendor Certifications (no sub-lessons — tracked at the certification level)

  • Omni Platform Certification
  • Omni Quickstart Certification
  • SnowPro Core
  • SnowPro Advanced: Data Engineer
  • SnowPro Specialty: Gen AI
  • Claude Certified Architect: Foundations (WIP)

Progress states

Foundation lessons:

  • in_progress — user opened the lesson
  • completed — user clicked “Mark as Complete”

Vendor certifications:

  • studying — user opened the cert study page
  • exam_booked — user has scheduled their exam date
  • passed — user confirmed they passed
  • failed — user attempted and did not pass

How progress gets recorded

TriggerWhat gets recorded
User opens a lesson pageLesson marked in_progress
User clicks “Mark as Complete” on a lessonLesson marked completed
All lessons in a module are completedModule completion recorded automatically
All required modules in a track are completedTrack/course completion recorded automatically
User opens a cert study pageCert marked studying
User logs an exam dateCert marked exam_booked with date
User confirms they passedCert marked passed with timestamp

Reporting queries it enables

QuestionHow
Who started the Foundation course?Query lesson progress — any in_progress or completed row
Where is a specific person in the course?Latest lesson with in_progress status, sorted by module + lesson order
Who completed Module 3?Query module completions for 03-cursor-deep-dive
Who has not started yet?Cross-reference team table in Internal AI Core against lesson progress
Who passed SnowPro Core?Query cert progress where status = 'passed' and cert = snowpro-core
Who is studying but hasn’t booked an exam?Query cert progress where status = 'studying'

Graph View