One variable's machinery, instantiated: the gates' and the matrix's legs #
The two abstract machineries of
DescriptiveComplexity.Draw.Data.var_run – the gates' run to the verdict
checkpoint and the per-round matrix pass – discharged at the program's own
rules (DescriptiveComplexity.Draw.Data.varRuleF at
DescriptiveComplexity.Draw.Data.varArgsOf): each is a walk-back into
the sub-machinery's first checkpoint, the assembled run
(DescriptiveComplexity.Draw.Data.gates_run,
DescriptiveComplexity.Draw.Data.matrix_run), and the walk-back at the
landing checkpoint.
The gates' leg of one variable's machinery: from the dispatch's landing one cell right of the marker, the walk-back, the whole gate sequence at a gated address, and the walk-back at the verdict checkpoint.
Dependency graph
The control after a failing gate sequence: the fail store at the failing block's entry, the flag clear.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Dependency graph
The gates' leg at a junk address: the walk-back, the passing prefix, the failing block, and the walk-back at the verdict checkpoint – the fail store applied, the flag clear.
Dependency graph
The background bundle, discharged at a boundary state: the five
slot equations DescriptiveComplexity.Draw.Data.var_run's kits read are
definitional in DescriptiveComplexity.Draw.Data.back, given the marker
and the order facts.
Dependency graph
The whole machinery at a junk address: entry, the failing gates, and the verdict checkpoint's clear flag routing straight to the exit with the stage slot erased – the VAL loop never entered.
Dependency graph
The control after a completed but failing gate sequence: the whole gates' thread – every block's file test passed and every block's machinery ran – with the flag clear because some block encoded no point.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Dependency graph
The whole machinery at a shaped but ungated address: every block passes its file test – the total dispatch carries each block's machinery through – but some block encodes no point, its witness not one-hot at the dispatched tag or its domain sentence failing. The gates complete with the flag clear, and the verdict checkpoint routes straight to the exit with the stage slot erased – the VAL loop never entered. The third landing an arbitrary address makes, beside the gated and the shape-failing ones.
Dependency graph
The whole variable machinery, run #
The state of one VAL-loop round: the entry state with the round's VAL content.
Equations
Instances For
Dependency graph
Two round states at the same register ask the same pass.
Dependency graph
A state written with the register it already holds is itself.
Dependency graph
Two round states' backgrounds agree off the VAL slot.
Dependency graph
The carry of a VAL round: the greatest element the register is clear at, everything above it set – what the increment's landing phase names.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Dependency graph
The carry is unique, so the chosen one is the hypothesis's.
Dependency graph
The exit control of one VAL round, at an entry control: the inner gates' thread over the round's register, then – at a passing round only, both flags set – the matrix thread on its output.
Equations
- DescriptiveComplexity.Draw.Data.roundFX RF hord vi st v mV semOf q a = dt.roundCtl RF hord ⋯ vi (dt.roundSt st (mV a)) v (semOf a) q
Instances For
Dependency graph
The VAL loop's entry-control thread: the fold's start at the cleared register, each round the matrix pass folded and stored at the carry's block.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Dependency graph
The leaf a round stores: the two gate flags' combination – False
if an ∃-level's block is not an encoding, the matrix's value only if every
∀-level's is.
Equations
Instances For
Dependency graph
The fold invariant of the VAL loop #
The VAL loop maintains the fold's contributions: at every round of
the enumeration, the accumulator vector of the control thread reads the
accCVal contributions of the inner quantifier prefix at the register's
inner blocks – the invariant that turns the machinery's exit verdict into
the prefix's value.
Dependency graph
The machinery's verdict is the inner prefix's value: at the exhausted register – every inner block full – the exit fold's bit is the alternating quantifier prefix over the inner blocks, applied to the matrix's value.
Dependency graph
The leaf, discharged #
A round's leaf is the matrix's realization: with the round's
semantic pack built by mkKindSem from the encoded valuation, the fold's
leaf after the matrix pass is the quantifier-free matrix's value at that
valuation – the concrete form of the invariant's hleaf hypothesis.
Dependency graph
One variable's verdict, semantically: with each round's pack built
by mkKindSem from an encoded valuation, the machinery's exit bit at the
exhausted register is the alternating quantifier prefix over the inner
blocks, applied to the quantifier-free matrix's realization. The remaining
interface (hPs) is the well-definedness of the matrix's value as a
function of the blocks alone – the encoding layer's obligation.
Dependency graph
The threaded twins of the VAL loop's two threads #
A round's exit state is its entry state unless the round's matrix ran a
stage atom, which normalizes SAV and TARGET
(DescriptiveComplexity.Draw.Data.roundEndSt). Whether it ran at all is
the gates' verdict, read off the control entering the round – so the two
have to be iterated together, one pair per round, exactly as the
spine's nodes are one scale up.
What is threaded is not the state but the two scratch registers
(DescriptiveComplexity.Draw.Data.roundEndSt_eq): every other register
is the machinery's entry state's, definitionally. That is what keeps the
semantic packs available – a pack reads the tape state through the levels'
register sets, i.e., through the mirror and VAL alone, so one family
indexed by the two registers serves every round, and it can actually be
built, which a family over arbitrary states could not be.
The two registers one round of the VAL loop can change.
Equations
Instances For
Dependency graph
The state a round is entered in: the machinery's entry state with the round's two scratch registers and the register it enumerates.
Equations
Instances For
Dependency graph
The VAL loop's thread: the two scratch registers beside the control, the fold's start at the cleared register, and at each cover the round's exit – the store taken against the background the round ends in.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Dependency graph
The scratch family of the VAL loop.
Equations
- DescriptiveComplexity.Draw.Data.varSTT RF hord vi st v mV semT fG a = (DescriptiveComplexity.Draw.Data.varPairT RF hord vi st v mV semT fG a).1
Instances For
Dependency graph
The tape family of the VAL loop – the state each round is entered in.
Equations
- DescriptiveComplexity.Draw.Data.varStT RF hord vi st v mV semT fG a = DescriptiveComplexity.Draw.Data.varRdSt st (DescriptiveComplexity.Draw.Data.varSTT RF hord vi st v mV semT fG a) (mV a)
Instances For
Dependency graph
The control family of the VAL loop, threaded – the twin of
DescriptiveComplexity.Draw.Data.varFM.
Equations
- DescriptiveComplexity.Draw.Data.varFMT RF hord vi st v mV semT fG a = (DescriptiveComplexity.Draw.Data.varPairT RF hord vi st v mV semT fG a).2
Instances For
Dependency graph
The state one round ends in – the next round's entry state at a cover, and the loop's exit state at the top.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Dependency graph
The exit control of one VAL round, threaded – the twin of
DescriptiveComplexity.Draw.Data.roundFX, at the state the round's
atoms actually run at.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Dependency graph
The registers a round leaves alone ride the whole loop – by construction now, since only the two scratch ones are threaded.
Dependency graph
A round leaves the register it was entered with.
Dependency graph
The VAL loop never touches a stage track: only the two scratch
registers are threaded, so the new tracks the spine writes ride the
whole loop.
Dependency graph
A round's exit state is the next round's entry state, once the next round's register is written over it.
Dependency graph
The thread starts at the entry state.
Dependency graph
The thread starts at the entry state.
Dependency graph
The control thread starts at the fold's start.
Dependency graph
The tape's cover equation: the next round is entered in this round's exit state, its own register written over it.
Dependency graph
The control's cover equation: the round's exit control, folded and stored at the block its increment carried.
Dependency graph
The threaded loop is the unthreaded one #
The VAL loop's rounds run at states that differ from the machinery's entry
state in SAV and TARGET alone, and every control they compute is blind to
that difference (DescriptiveComplexity.Draw.Data.roundCtlT_eq_roundCtl,
DescriptiveComplexity.Draw.Data.roundCtl_congr_scratch). What the
threading can change is the semantic pack, since a family indexed by the
scratch registers may pick different points at different registers; so the
bridge is stated at a pack that is one unthreaded pack transported
(semCastT), which is what a reduction supplies
(DescriptiveComplexity.Draw.Data.gatedSem, whose points are the
address's blocks and nothing else).
A round's entry state is the round state up to the two scratch registers.
Dependency graph
One unthreaded pack, at every state a round reaches: the round's own
state and the states its matrix threads all share the mirror and VAL of the
round state, so kindSemCast carries the pack to each of them.
Equations
- DescriptiveComplexity.Draw.Data.semCastT RF vi st v mV sem₀ p a hp b = dt.kindSemCast PR.zero PR.one vi ⋯ ⋯ (dt.kindOf vi b) (sem₀ a ⋯ b)
Instances For
Dependency graph
One threaded round is the unthreaded round: a round's own state is the round state up to SAV and TARGET, its matrix threads those two further, and the pack rides along – three transports that compose to none.
Dependency graph
The threaded round of the VAL loop is the unthreaded one, at the state the loop's own thread produced.
Dependency graph
The VAL loop's threaded control is its unthreaded control: round by
round, varFXT_eq_roundFX, the backgrounds agreeing because a round's exit
state is the round state up to SAV and TARGET. This is the bridge between
the control the machine's run produces and the control
DescriptiveComplexity.Draw.Data.accVerdict_leafP reads.
Dependency graph
The control the gates leave, at the reduction's own budgets – what both forms of the machinery's run start their VAL loop from.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Dependency graph
One variable's machinery, fully instantiated: from the entry checkpoint at the marker, through the gates at a gated address, the VAL clear and the rounds of matrix pass, exhaustion test and block-indexed increment, to the exit checkpoint – the fold spelled by the concrete threads, every leg the assembled runs of the layers below.
Dependency graph
One variable's machinery, fully instantiated – threaded: as
DescriptiveComplexity.Draw.Data.varMachine_run with no boundary
discipline assumed, so it applies at every address of a sweep and not
only at the one whose SAV and TARGET the advance happens to have left
behind. The rounds run at the states the thread produces, and the loop
ends in DescriptiveComplexity.Draw.Data.varStE at the top, which
differs from the entry state in SAV and TARGET alone.