claimroutineinferred_dep
Padding preserves acceptance probability exactly
Padding makes on accept with exactly 's probability
links the library's answer to the language of
Claim·§13.3 Padding and exact preservation of acceptance probability·inside thmEffective compiler from randomized to deterministic logspace
Statement (paper)
Under the stated hypotheses on (halting within steps, using at most work bits), all eligibility checks pass for the padded input of length , no resource cutoff changes a promised source run, and hence exactly, with no conditioning or additional approximation. In particular the decision of is the decision required for .
In plain English
If halts within steps and uses at most work bits, then on the padded input of length the interpreter passes all its eligibility checks and never cuts off a run. Hence exactly, so the decision of is the decision needed for .
Why it's here
The padded length is chosen so that the interpreter's step and work-tape limits from the compiler-interpreter lemma are at least 's promised bounds. Every run of is then simulated faithfully with no truncation, and the two acceptance probabilities agree exactly, with no conditioning or approximation. This lets the later steps apply the library algorithm to and read off the answer for on .
Classified routine:
Standard padding argument: the padded length is chosen so that the fixed interpreter's resource limits from lem-compiler-interpreter exceed M's promised bounds. Faithful, untruncated simulation then follows by direct bookkeeping, as in classical universal-machine and padding arguments.
Uses
Used by
Sources
PaperOpen
- Section
- §13.3 Padding and exact preservation of acceptance probability
- Page
- —
- Label
—- Line
sections/compiler.tex:256
Leannot aligned
Phase 2 aligns this node to a Lean declaration.
Friction
- infoinferred_depoutline: "Padding preserves acceptance probability exactly" rests on lem:compiler-interpreter