WorkflowFigure

A process: who does what, in what order, and where it can go wrong.

Three structures stacked on one grid, and they are three because they answer three different questions a reader brings to a runbook.

Lanes are rows and answer WHO. A lane marked exception is the one band that gets a wash rather than a rule, and it earns the exception to the frames-are-rules law because nothing routes across it — it IS the ground for the failure path, not a frame drawn over the happy one.

Phases are columns across every lane and answer WHEN. Printed as captions on one header rule, because a phase is an axis label. Groups are frames inside a single lane and answer WHAT BELONGS TOGETHER — a planning loop, an evidence path.

THE MAIN PATH IS HEAVIER, and that is the whole hierarchy. mainPath lists the node ids a reader should be able to follow without thinking. Every edge between two consecutive ids on it is drawn at the emphasis weight whatever its own variant says, which is the one thing that turns fourteen boxes and nineteen arrows into a diagram with a subject. An error role goes the other way — dashed and soft — so the exception path recedes without disappearing.