How statement and proof provenance work
The first chip identifies the source of the statement or construction; the second identifies the source of its local proof or verification.
- Literature-sourced: the exact statement appears in a cited source; only wording and notation differ.
- AI-adapted: a semantically identical restatement of literature-sourced material, modulo indexing, notation, and boundary cases adopted by the library.
- AI-generated: a genuinely novel statement formulated by AI, with no source for the claim itself.
These labels describe origin, not correctness: citations and verification chips remain separate evidence.
Space-bounded universal simulation
Statement
There is a fixed deterministic universal simulator with the following space bound. Given a machine description and input of total binary length , if the simulated machine uses at most all-tapes cells, then uses all-tapes cells, with an absolute constant for the fixed coding below. Consequently, for each fixed its bound is ; the constant may depend on . It is uniformly for machines over one fixed alphabet.
The machine description uses the explicit finite transition-table encoding of A fixed effective binary encoding of deterministic one-tape Turing machines, extended to multitape machines by listing the tape count and every transition on a tuple of scanned symbols. Input symbols are listed in binary with delimiters. Space counts cells on all tapes as in The classes DTIME, NTIME, DSPACE, and NSPACE. No constructibility or halting-time bound is needed.
For hierarchy applications a supplied cell limit may instead cap the entire encoded simulation workspace of this fixed simulator, including its temporary scratch. Its bounded version aborts before exceeding that limit and uses all-tapes space. For each fixed , if , the bounded version eventually completes every simulated transition without a space abort. No uniform encoding of arbitrary variable-alphabet symbols is asserted.
Facts & Assumptions
Given: an explicitly coded deterministic multitape machine , its input, and a simulated run visiting at most cells in total.
Proof
Decode and retain the description and input using space. Write . Represent each simulated tape by the consecutive cells from its left boundary to its furthest visited cell, storing a -bit symbol and a head-marker bit in each cell block. Separate tapes by delimiters. Every tape has at least its initial cell visited, so their number is at most . Store the current state by its binary index, of length at most . Unvisited input symbols can be recovered from the retained input when a tape block first reaches them. Thus the complete representation has length .
For a simulated transition, scan the tape blocks to collect the marked symbols, look up the unique matching transition in the retained explicit table, and scan again to update symbols and markers. Keep old and new marker tracks distinct until the update is finished, so a head moving along a sweep is updated only once. A new rightmost cell is appended when necessary; at a left boundary clamp a left move. The scanned-symbol tuple and update tuple use bits, and counters or copies of the current representation use at most the same order. Reuse all scratch after each update. Induction on simulated transitions gives the correct represented configuration at each completed update, without retaining the history.
This is an algorithm on a fixed finite alphabet and a fixed finite number of simulator tapes: variable simulated tape blocks reside on those tapes as delimited data. Every stage uses cells, with a constant independent of . For fixed , is constant, giving ; if the alphabet is fixed in advance, the same constant works uniformly for its machines.
To cap the encoding, maintain a binary counter for the number of cells allocated to its tapes, including update scratch, and abort before that count exceeds . The counter and supplied binary limit use additional cells, so the bounded version uses space. For each fixed there is a constant bounding all workspace in steps 1.1--2.1 by ; when this lies below eventually. Hence the cap does not truncate those simulations.
Depends on
Used by
Dependency tree · two levels
7 results within two dependency steps of this one, each drawn at its shortest distance from it. An arrow runs from a result to what uses it, so the chart reads left to right and ends at this result, which carries a heavier outline. Every node is a link to that result. Click elsewhere on the chart to enlarge it.
Sources
- Arora and Barak, Computational Complexity, §1.2.2, Claims 1.8--1.9 (standard reference, not scraped)