Curriculum Readiness
This curriculum is being published in slices. Some areas are learner-ready now. Others are still public blueprints.
Use the readiness labels below before you treat a semester or module as complete curriculum.
Status Labels
| Label | Meaning |
|---|---|
Implemented | Learner-ready. The teaching path is written, the assessments are usable, and the page is free of placeholder residue. |
In Progress | Publicly visible but partial. Some learner-ready material exists, but the semester or track is not complete yet. |
Blueprint | Structural only. Scope and sequencing exist, but the content is not ready to act as the main learning path. |
Publication Bar
No page should be marked Implemented unless it has:
- clear scope and objectives
- a real concept path
- usable exercises or assessment
- concrete artifact expectations
- no template prompts, placeholder blocks, or raw generation residue
Current Curriculum Status
| Semester | Status | Notes |
|---|---|---|
| Pre-Semester Launchpad | Implemented | Complete starting path for study systems, tooling, and Git workflow |
| Semester 0: Orientation & Foundation | Implemented | Complete orientation block with project, checkpoint, cumulative review, and exam |
| Semester 1: Mathematical & CS Foundations | In Progress | Public exemplar available for Module 1: proofs and discrete structures |
| Semester 2: Algorithms & Data Structures | Blueprint | Roadmap and structure exist, but not learner-ready |
| Semester 3: Software Design & Patterns | Blueprint | Roadmap and structure exist, but not learner-ready |
| Semester 4: Systems Programming | Blueprint | Roadmap and structure exist, but not learner-ready |
| Semester 5: OS & Networking | Blueprint | Roadmap and structure exist, but not learner-ready |
| Semester 6: Databases & Distributed Systems | Blueprint | Roadmap and structure exist, but not learner-ready |
| Semester 7: Software Architecture & Domain Design | In Progress | Public exemplar available for Module 1 and the architecture review project brief |
| Semester 8: System Design & Technical Leadership | Blueprint | Roadmap and structure exist, but not learner-ready |
| Semester 9: Cloud Infrastructure & DevOps | Blueprint | Roadmap and structure exist, but not learner-ready |
| Semester 10: Capstone Integration | Blueprint | Roadmap and structure exist, but not learner-ready |
How To Use This
- Start with pages marked
Implemented. - Use
In Progresspages only where the public sidebar points you to a specific module or artifact. - Treat
Blueprintpages as planning documents, not finished coursework. - If a semester is not clearly marked
Implemented, assume you should not rely on it as a full learner path yet.