The matrix's stages at an arbitrary file #
DescriptiveComplexity.Problems.Wide.DrawInstMat read at a coarse file: the
four atom runs – comparison, expansion, stage and gate block – wrapped into the
one shape the sequencer drives them through, entry one cell to the marker's
right at the Slot.val-walked presentation and exit at the next checkpoint.
Each wrapper is the clocked run of its atom with the walk-back the dispatch
owes, so each carries its atom's budget plus one step.
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 comparison atom, entered by a dispatch: from its entry
checkpoint one cell to the marker's right, at the Slot.val-walked
presentation, to the exit phase back at the same cell.
Dependency graph
The expansion atom, in the sequencer's shape #
The expansion atom, entered by a dispatch: from its first phase one
cell to the marker's right, at the Slot.val-walked presentation, to the
exit phase back at the same cell.
Dependency graph
The stage atom, in the sequencer's shape #
A stage atom entered at the boundary leaves the state unchanged, at an arbitrary file: with SAV and TARGET already the marks of the home address, the restore restores what was there.
Dependency graph
The stage atom, threaded: the same run as
DescriptiveComplexity.Draw.Data.ixStage_hStage with no boundary
discipline assumed – the random access writes the home address into SAV and
TARGET whatever they held, so its exit state is the normalized
DescriptiveComplexity.Draw.Data.ixStageEndSt.
Dependency graph
The stage atom, entered by a dispatch: at the boundary discipline – SAV and TARGET at the home address – the random access runs and restores the state, so the sequencer's background is untouched.
Dependency graph
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.
Dependency graph
A failing gate block: some register is not well-shaped, so the file test fails and the block leaves the whole gate sequence through the failing exit, the fail store applied at the marker's symbol.