Epic: Adopt the course platform and evolve Course into Course → Cohort

[alexeygrigorev]

Normative spec: 04 — Course-platform adoption and Course → Cohort

Outcome

Adopt the existing course-management platform without silently losing its business behavior, then perform an expand-and-contract evolution from edition-like Course records to reusable Course parents with Cohort deliveries.

Boundaries

This is not a rewrite. Proven enrollment, submission, peer review, scoring, leaderboard, complaints, certificates, calendars, dashboards, APIs, and operational workflows remain characterized while architecture and authorization are improved deliberately.

Epic completion gate

• Literal-copy adoption baseline and unchanged characterization suite pass.
• Production-like schema/data upgrade proves Course → Cohort without data loss.
• Every current learner/API/cadmin behavior is retained, explicitly changed, or explicitly retired with approval.
• Complete Studio/admin API parity and legacy-host compatibility pass.

Dependencies

Depends on #1; structural migration depends on the standalone copy/adoption baseline issue.

Child issues

• Decision: Record adoption—not rewrite—of the existing course platform #13
• Decision: Confirm cohort-owned curriculum for the first consolidation release #14
• Decision: Approve the legacy course-edition family mapping #15
• Decision: Inventory course API consumers before legacy-host redirects #16
• Copy the existing course platform verbatim and establish its characterization baseline #30
• Migrate edition-like Course records to reusable Course → Cohort #51
• Replace global course staff access and plaintext API tokens with scoped capabilities #52
• Add Course/Cohort lifecycle, public routes, and complete cohort duplication #53
• Preserve course registration, enrollment, learner profile, dashboard, and calendar flows #54
• Preserve cohort homework, answer, submission, scoring, and statistics behavior #55
• Preserve cohort projects, peer assignment/review, voting, and scoring #56
• Preserve cohort score breakdowns, leaderboards, privacy, and complaints #57
• Preserve graduates, certificates, and historical Wrapped records #58
• Move all course operations into Studio and the admin API #59
• Preserve legacy course HTML/API compatibility and rehearse full data migration #60
• Provision and activate the courses.datatalks.club redirect Lambda safely #71