Skip to main content

Curriculum Readiness

Readiness is tracked in content/portal/readiness-matrix.json, which is the canonical source for semester status.

Use the readiness labels below before you treat a semester or module as complete curriculum.

For the higher-level promise, read Confidence Contract. For the practical route, use Path Levels.

Status Labels​

LabelMeaning
BlueprintStructural only. Scope and sequencing exist, but the content is not ready to act as the main learning path.
ScaffoldedPublicly visible with structure and some content, but not yet complete or reviewed enough to promise as coursework.
Learner-readyThe teaching path is written, the assessments are usable, and the page is free of placeholder residue.
ReviewedLearner-ready material has also passed editorial, technical, and assessment review.
Battle-testedReviewed material has been used by learners and revised based on observed friction.

Publication Bar​

No page should be marked Learner-ready 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​

SemesterStatusNotes
Pre-Semester LaunchpadLearner-readyComplete starting path for study systems, tooling, and Git workflow
Semester 0: Orientation & FoundationLearner-readyComplete orientation block with project, checkpoint, cumulative review, and exam
Semester 1: Mathematical & CS FoundationsLearner-readyLearner-facing mathematical foundations path is the current fundamentals exemplar
Semester 2: Algorithms & Data StructuresBlueprintRoadmap-visible algorithms structure; do not treat as the promised learner-ready path yet
Semester 3: Software Design & PatternsScaffoldedPublic structure and content exist, but the semester still needs readiness review before learner-ready use
Semester 4: Systems ProgrammingScaffoldedPublic structure and content exist, but the semester still needs readiness review before learner-ready use
Semester 5: OS & NetworkingScaffoldedPublic structure and content exist, but the semester still needs readiness review before learner-ready use
Semester 6: Databases & Distributed SystemsScaffoldedPublic structure and content exist, but the semester still needs readiness review before learner-ready use
Semester 7: Software Architecture & Domain DesignScaffoldedIncludes exemplar architecture modules; the whole semester still needs readiness review before learner-ready use
Semester 8: System Design & Technical LeadershipBlueprintRoadmap-visible system design and leadership structure; do not treat as the promised learner-ready path yet
Semester 9: Cloud Infrastructure & DevOpsBlueprintRoadmap-visible cloud and DevOps structure; do not treat as the promised learner-ready path yet
Semester 10: Capstone IntegrationBlueprintRoadmap-visible capstone structure; do not treat as the promised learner-ready path yet

How To Use This​

  • Start with pages marked Learner-ready, Reviewed, or Battle-tested.
  • Follow learner-ready-or-better pages in prerequisite order; use scaffolded or blueprint pages only as planning context.
  • Do not skip directly to advanced semesters unless you already have the prerequisite background and artifacts.
  • Use Scaffolded pages only where the public sidebar points you to a specific module or artifact.
  • Treat Blueprint pages as planning documents, not finished coursework.
  • If a future semester, module, or track is not clearly marked Learner-ready, Reviewed, or Battle-tested, assume you should not rely on it as a full learner path yet.

Confidence Rule​

Do not judge the curriculum by total page count.

Judge it by whether the current path has:

  • clear objectives
  • guided concept pages
  • practice and assessment
  • visible artifacts
  • honest readiness labels

If those are present, use the page as coursework. If they are absent or the status is Blueprint, use the page only as a map.