Learning management platform

Institutes teaching a structured syllabus end up stitching together a video host, a messaging group, a spreadsheet of marks and a payment record that lives somewhere else entirely. Nobody can answer 'is this student on track' without opening four systems, and the cost of delivering video quietly becomes the largest line item nobody planned for.

Model the syllabus, the cohort and the assessment as first-class entities rather than as folders of files, so progress is a query rather than a reconciliation. Video delivery is treated as an infrastructure decision with a cost model attached, chosen against measured egress rather than a provider’s landing page.

• —Cohorts and structured syllabus with sequencing and prerequisites
• —Assessment with marking, moderation and per-student progress
• —Video lessons with access control and resumable playback
• —Attendance and engagement visible per cohort and per student
• —Enrolment and payment status tied to access

1. NOTE.01

   Syllabus, cohort and enrolment are separate entities. A cohort is an instance of a syllabus with its own calendar, which means the same course can run twice without duplicating content or losing last term’s marks.

2. NOTE.02

   Video is served from object storage behind signed, expiring URLs rather than from the application. Egress cost was modelled per provider before the choice was made — that comparison is written up in the engineering notes.

3. NOTE.03

   Assessment records are immutable once moderated; corrections are new rows with a reason, so a mark can always be explained after the fact.

4. NOTE.04

   Access control resolves from enrolment state at request time rather than being copied onto content, so a lapsed payment revokes access without a batch job.

• TypeScript
• Next.js
• PostgreSQL
• Object storage