Context
The recurrence separates the mathematical frontier from any particular data structure used to represent it.
Hypotheses and scope
- The machine uses the finite real-time top-rewriting interface of FPRD-D33.
- Stack tops are written on the left and acceptance is by final control state.
Proof or evidence
Splitting a run before its last transition gives one direction; appending the selected transition gives the converse. The Lean package checks the recurrence, readout, epsilon theorem, and push, pop, local, branch-union, mismatched-top, and initial-acceptance examples.
Verification notes
The theorem names, executable verifier, examples, top-of-stack orientation, and exact-input readout were reconciled with the proof note. No epsilon or post-input transition is hidden in the statement.
Limitations
- Lean does not verify the visibly pushdown projection theorem or the external PEG/scaffold correspondence.
- Exact frontier evolution alone gives no bounded width, allocation, or access theorem.
Notes
Lean 4.30.0 checks the executor, recurrence frontier_append_singleton_iff, readout accepts_iff_final_frontier, epsilon theorem, and concrete push, pop, local, branch-union, mismatched-top, and initial-acceptance examples. Lean does not verify FPRD-T91, VPA determinization, regular-frontier normalization, LMR, or any CFL-to-PEL conclusion.