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.
Ph complete language forces collapse
Statement
If a language is polynomial-time many-one hard for all of PH, then PH collapses to a finite level. In particular, implies such a collapse.
Facts & Assumptions
Given: the objects and hypotheses in the statement above.
For each fixed , both and are closed under polynomial-time many-one preimages and polynomially many uniformly indexed conjunctions and disjunctions. Precisely, if the language of pairs lies in the class and for a polynomial-time computable polynomial bound , then both “every such ” and “some such ” define languages in that class. Complements interchange and , and each is contained in both classes at level . These assertions also hold with one fixed base oracle. (Ph quantifier block closure).
For fixed , implies . Also implies . (Sigma k equals pi k implies ph collapse).
TQBF lies in PSPACE, and every language in PSPACE polynomial-time many-one reduces to TQBF. Therefore TQBF is PSPACE-complete. (TQBF is PSPACE-complete).
Proof
Choose a fixed with , padding upward if necessary. Every belongs to PH by padding and reduces to , hence lies in by preimage closure. Complementing gives the reverse inclusion, so the finite-level collapse theorem applies.
Under , TQBF belongs to PH and every PH language reduces to it, by its exact PSPACE-completeness statement. It therefore serves as in the first step. No strict containment between PH and PSPACE is assumed.
Depends on
Used by
Nothing in the library uses this result yet.
Dependency tree · two levels
4 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–Barak, Computational Complexity, 2007 draft; §5.2.2 Claim5.7 and Remark5.8, p93. (standard reference, not scraped)