module-planner

Module Planner

Triggers & routing

• Trigger: module plan, tutorial modules, course outline, module planning, module_plan.yml.
• Use when: tutorial's C2, already has outline/concept_graph.yml, need to converge the concept DAG into a module sequence.
• Skip if: there is no concept graph yet.
• Network: none.
• Guardrail: each module must have objectives, outputs, running-example step; do not write long prose.

Turns the concept graph into the teachable module sequence used by later tutorial stages.

Input

• outline/concept_graph.yml

Output

• outline/module_plan.yml

Contract

The module plan must define:

• ordered modules
• id, title
• objectives
• concepts
• outputs
• running_example_steps

Script boundary

scripts/run.py should:

• topologically order concepts
• cluster them into coherent modules
• attach measurable objectives and concrete outputs

Keep graph traversal and clustering heuristics in shared tutorial tooling, not in the wrapper script.

Acceptance

• outline/module_plan.yml exists
• every concept node is covered by at least one module
• every module has objectives and outputs

Non-goals

• source grounding audit
• exercise writing
• tutorial drafting