Module lane 

Who does a task: the implementer (code), the plan’s author (planning: design documents inside the unit’s directory) or a person (yours). Derived, never stored — from the task’s line, the unit’s directory, the format’s judged files and an honest stop.

Structs

Lanes

A unit’s open tasks by lane, for Before you run.

Enums

Lane

A task’s lane.

Functions

by_paths

The lane a task’s named paths give it (task_paths): planning when there is at least one and every one lies inside unit_dir (repository- or project-relative, a leading / read as the root) and none is a judged file — judged is asked with the path relative to unit_dir, without a trailing /; else code.

classify

A task’s lane: yours for a [YOU] label or after an honest BLOCKED: stop, else by_paths.

task_paths

The paths a task’s lane is read from: every backticked path, and every bare one that reads as a path rather than prose — a file with an extension, a directory written with its /, or a path in unit_dir (input/output is none of them).