The matrix's stages: the atom runs in the sequencer's shape #
The sequencer (DescriptiveComplexity.Draw.seq_run) drives its stages
through one uniform interface: entry one cell to the marker's right, one
fixed walked track, exit at the next checkpoint. This file wraps the four
instantiated atom runs into that shape:
DescriptiveComplexity.Draw.elem_back– the walk-back a dispatch into an element loop owes (the machinery's own.e0stay rule);DescriptiveComplexity.Draw.Data.stageEndSt_eq– the boundary discipline: a stage atom entered with SAV and TARGET at the home address leaves the state unchanged, so the matrix's background is constant across its atoms;- the three wrappers
cmp_hStage/exp_hStage/stage_hStage, all at theSlot.val-walked presentation of one boundary state – the presentationDescriptiveComplexity.Draw.Data.var_runhands the matrix.
The element loop's walk-back #
The one leftward step a caller's rightward dispatch into an element loop owes: at its entry checkpoint, the walk back down to the marker.
Dependency graph
The boundary discipline #
A stage atom entered at the boundary leaves the state unchanged: with SAV and TARGET already at the home address, the restore restores what was there.
Dependency graph
The val-walked and the mir-walked presentations of one state
coincide: both are the naked background.
Dependency graph
The comparison atom, in the sequencer's shape #
The expansion atom, in the sequencer's shape #
The stage atom, in the sequencer's shape #
One gate block, in the sequencer's shape #
A passing gate block, entered by a dispatch: every register is well-shaped, so the file test passes, the domain evaluation runs on the block's decoded tag, and the block exits to the next checkpoint.