The gates' facts, from the marks #
What the gate machinery asks – the file tests' per-cell questions, the
witness one-hotness, the domain conditions – read off
DescriptiveComplexity.Draw.Data.back's marks and answered by the
encoding. The marks of a register cell spell the cell's own coordinates
(name), its padding (pdd) and its tag's block (blk), so a file
test's question is a statement about the cell, and a block value's
answers are statements about the value:
wellShapedG_back_iff/igTest_iff– the per-cell question is «if the cell is of the gated block and in the register, its tuple is a witness or a member shape», at MIRROR and at VAL;testOf_of_encMap,wit_of_encMap,domHolds_of_encMap,dspTagOf_encMap– at a block value that is an encoding, every gated hypothesis ofDescriptiveComplexity.Draw.Data.varMachine_runholds, and the dispatch is the point's tag;gate_trichotomy– every block value is an encoding, has an ill-shaped register cell, or is all-shaped with the one-hot-and-domain conjunct failing at the dispatched tag: the three legsDescriptiveComplexity.Draw.Data.varLeg_run/varLegFail_run/varLegUngated_runare exhaustive;igPassP_iff_isEnc– the inner loop's per-level verdict isDescriptiveComplexity.Draw.IsEncof the level's block value, the marks-to-shapes bridge the two-flag characterization was stated against.
Encoded tuples against the marks #
An encoded tuple is canonically padded: the layout inhabits the
first dd₀ coordinates, so everything above them is the designated
zero.
Dependency graph
A padded tuple whose name coordinates spell an encoded tuple is that
tuple: the coordinates above dd₀ agree because both sides are zero
there.
Dependency graph
The per-cell questions, read #
The shape clause of the marks is the shape of the cell's tuple: the padding mark together with a name-coordinate match is full equality with the encoded tuple.
Dependency graph
The outer file test's question, read off the marks: if the cell is of the gated block and belongs to MIRROR, its tuple is a witness or a member shape.
Dependency graph
The inner file test's question, read off the marks: the same at the VAL register.
Dependency graph
The shape clause of a block value #
The per-cell questions of a block answer for its value: every cell
of block b' in the register is well-shaped exactly when every member of
the block value is a witness or a member shape.
Dependency graph
The gated facts: at a block value that is an encoding #
At an encoding every cell passes the outer file test.
Dependency graph
At an encoding the witness is one-hot at the point's tag.
Dependency graph
At an encoding the dispatch is the point's tag.
Dependency graph
At an encoding the domain condition holds of the decoded assignment – the point carries it.
Dependency graph
The trichotomy: the three legs are exhaustive #
Every block value makes one of three landings: it is an encoding (the gated leg), some register cell of its block is ill-shaped (the shape-failing leg), or every cell is well-shaped and the one-hot-and-domain conjunct fails at the dispatched tag (the ungated leg).
Dependency graph
The inner loop's bridge: the per-level verdict is the gate #
Every cell of an encoded VAL block passes the inner file test.
Dependency graph
The inner loop's per-level verdict is the gate: a level passes – its file test, the one-hot witness at the dispatched tag and the domain condition there – exactly when its block value is an encoding. The marks-to-shapes bridge of the two-flag characterization.