Finite replay of binary counting certificates #
The checker uses the existing finite configuration representation and ordinary native actions. Its validity flag is an option: invalid indices and nonzero terminal padding fail, including for the rejecting classifier. The empty communication interface introduces no oracle resource. The machine, its finite control, number of tapes and block width are fixed; polynomial time is in the encoded input/certificate pair, not uniformly in a supplied machine description.
Main definitions #
Turing.MultiTapeCTM.Checker.indexStep: a finite-storage occurrence or canonical padding step.Turing.MultiTapeCTM.Checker.output: finite replay followed by a genuine halting check.Turing.MultiTapeCTM.Checker.checkBinary: the binary verifier for either terminal verdict.
Main results #
Turing.MultiTapeCTM.Checker.output_eq_decodeCertificate: exact native replay correspondence.Turing.MultiTapeCTM.Checker.checkBinary_eq_certificateAccepts: exact binary/index correspondence.Turing.MultiTapeCTM.Checker.computableTidilyInPolyTime_checkBinary: the actual checker is polynomial-time, using finite dispatch and a linear encoded-storage loop invariant.
References #
The finite configuration, encoding and tidy calculus retain the source credits in their modules.
Counting semantics and canonical padding are developed in MultiTape.Counting.Certificate.
Existing finite native storage with no communication channels.
Instances For
One occurrence, or a forced zero after halting; failure is distinct from rejection.
Instances For
Finite local views give the same ordered occurrences as a represented native configuration.
Finite-storage replay computes exactly the previously proved certificate decoder's output.
The actual finite-storage transition checker is certified, including arbitrary invalid indices. Its fixed finite dispatch table is charged by the existing finite-domain compiler.
A replay step retains the existing linear storage bound, including forced terminal padding.
The checker stores unconsumed bits and either a live finite replay or a permanent failure.
Instances For
Consume one fixed-width block and replay its occurrence index. The saturation cap is fixed; for a full block it equals ordinary binary decoding.
Instances For
Execute one binary certificate block using the certified parser and finite replay step.
The actual replay loop is polynomial-time. Its invariant charges the input, every work tape, output and remaining certificate; there is no assumed simulation or counting certificate.
Read the final output only after an actual simulated halt.
On full-width certificates the actual loop is exactly the canonical index replay. Failure remains absorbing, so the equality also covers invalid occurrence indices and padding.
The compiled loop returns exactly the output of the canonical native decoder. The positive block width converts the supplied binary length into the declared number of machine steps.
Each terminal verdict uses the same exact validity condition as the canonical decoder.
Both the accepting and rejecting binary verifiers are polynomial-time on every input pair.