TutorLumin Syllabus Authoring Rules
Canonical TutorLumin syllabus manifests live under content/courses/.../syllabus.yaml.
Use one manifest shape for every lane:
- required manifest fields:
syllabusId,slug,subject,laneType,version,checklistItems - optional manifest fields:
level,locale,tags,teacherDefaults,checklistDefaults,sourceRefs - required checklist item fields:
key,title - optional checklist item fields:
summary,weight,masterySkill,statusModel,prerequisites,promptHints,artifactRefs
Defaulting rules:
- put lane-wide teaching metadata in
teacherDefaults - put lane-wide checklist behavior in
checklistDefaults - item-level fields override manifest defaults
- language lanes should usually default to
statusModel: mastery - course lanes should usually default to
statusModel: check
Current seeds using this shape:
content/courses/Chinese/Beginner/syllabus.yamlcontent/courses/French/Beginner/syllabus.yamlcontent/courses/Physics/Advanced/syllabus.yaml
Boundary rules:
- keep YAML canonical in TutorLumin content
- keep shared manifest contracts aligned in
tutor-ops/packages/contracts - keep detailed per-student progress and access state in the hosted learning projection, not in syllabus YAML and not in LDAP
Lesson Atoms (Concept / Context / Activity)
For many TutorLumin lanes (languages and STEM), we treat a “chapter” as a bundle of three reusable atoms:
- concept: the structure (grammar / theory)
- context: the situation (scene / theme / application setting)
- activity: practice + assessment (drills / quizzes)
This lets students mix and match atoms while still allowing coherent study paths and book-generation from a stable bundle ordering.