A question, read back #
The mirror of DescriptiveComplexity.GameProg.altWin_ask: if the machine wins
from the entry of a question's prefix, the question holds.
What the bridge has to say, backwards #
- an arrival is a correct claim.
DescriptiveComplexity.SeekArrivesgives a cell whose symbol answered the test; unfoldingDescriptiveComplexity.GameProg.isTargetsays the symbol's bit is the claim, its region is the one the atom's copy names, and its address is the atom's arguments at the valuation. Since the tape's cell carries the bit the assignment gives it, the claim is right – and the region bookkeeping isDescriptiveComplexity.GameProg.cond_copyagain, read the other way; - the seek's test never fires on a mark, which the parametric layer had to assume and the program discharges by unfolding one existential;
- the tuple
SeekArrivescarries is not the one the forward direction builds, so the address it names has to be recovered fromargsOfand the agreement with the phase's valuation – which is the only place the two halves of a transition's tuple are pulled apart backwards.
The seek's test never fires on a mark: it asks for the symbol of a cell, which a sentinel's mark is not.
Dependency graph
The guard of a concluding transition reads only the valuation the phase declares.
Dependency graph
An arrival is a correct claim. The cell the seek stopped at holds the atom the challenge named, its bit is the one that was claimed, and the tape gives that bit by the assignment of the region the atom's copy points to.
Dependency graph
The matrix holds, read back from a winning claim phase: the vector the existential player claimed is correct at every atom the universal player could have challenged, and the residue it leaves holds.
Dependency graph
A question holds, read back: if the machine wins from the entry of a
question's prefix, the question's sentence is true of the two assignments the
tape carries. This is the converse of
DescriptiveComplexity.GameProg.altWin_ask.