Skip to main content

Module graph

Module graph 

Source
Expand description

Task dependencies from what tasks.md documents, and which tasks are ready.

Edges come only from structure and from IDs written in task text; nothing is inferred:

  • Phases. Foundational waits on all earlier phases; each user-story phase waits on the earlier non-story phases only, so stories are independent of each other; polish, convergence and unrecognised phases wait on all earlier phases.
  • Subsections. A ### subsection waits on the earlier subsections of its phase (tests before implementation).
  • [P] runs. A [P] task waits on the previous non-[P] task; a non-[P] task waits on the whole preceding [P] run, or on the previous task when there is no run.
  • Explicit. depends on T012 / after T012 in the task text.

In declared mode (the Format line documents (depends on …)) the written references are the complete order within a phase: subsection and [P] edges are dropped, phase order is kept.

In chain mode (OpenSpec) a group waits on every earlier group and a task on the one before it in its group; written references are added.

Dangling references and cycles are errors; the tasks involved are blocked.

Enums§

PhaseKind
What a phase heading says the phase is.

Functions§

classify
Classifies a phase by its heading and whether its tasks carry story labels.
schedule
Builds the schedule of parsed, with graph.* diagnostics.