Curricula, courses and lessons
The tracks your corpus compiles into, and the lifecycle every piece moves through.
- Role-based tracks compiled from the documentation you already have
- Every lesson cites the source passages it was built from
- Draft, in review and published are separate states with separate permissions
The shape
```
Curriculum (role track, level)
└── Course
└── Lesson → cites source passages
```
The lifecycle
Every curriculum, course and lesson sits in exactly one state:
| State | Meaning | Who can move it on |
|---|---|---|
| Draft | Being written or just compiled | Author and up may submit it for review |
| In review | Waiting on a human decision | Reviewer and up may publish or send it back |
| Published | Visible to learners | Reviewer and up may unpublish or archive |
| Archived | Retired, not deleted | Author and up may take it back to draft |
Two rules hold everywhere, including for direct API calls:
- Nothing goes straight from draft to published. The step through review is not skippable.
- An author cannot approve their own work, and cannot quietly unpublish live content.
Levels
Foundations → Associate → Professional → Specialist. Foundations is typically open and unproctored; the higher levels are where assessment and credentials attach.
Frequently asked
What is a curriculum?
A role-based track — Admin, Developer, Support Engineer, Partner Implementer — at one of four levels: Foundations, Associate, Professional or Specialist. Inside it sit courses, and inside those, lessons.
Where do courses come from?
Either the compiler, which drafts them from a connected source, or an author writing them by hand. Both arrive as drafts; neither can skip review.
What does the citation count on a lesson mean?
How many passages of your corpus that lesson was built from. It is the provenance signal: a lesson citing nothing was not compiled from your documentation, and a reviewer should know that before approving it. Citations are also what lets a lesson be invalidated automatically when its source changes.
Who can see unpublished content?
Owners, org admins, enablement managers, authors and reviewers. Learners only ever see published content, and the database enforces that — an unpublished draft is invisible to them however the request arrives.