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.
Simon query lower bounds do not imply explicit-input gate lower bounds
Statement refuted
For the Simon decision promise, the classical-versus-quantum oracle-query separation implies that the same promise problem, with an explicit full truth-table input of length , has no deterministic algorithm running in time polynomial in .
Facts & Assumptions
Given: The same YES/NO function promise in two distinct access models: classical oracle queries, and a binary input containing the complete table.
Classical randomized Simon decision requires square-root-many queries: oracle-only classical randomized decision requires queries.
Simon rank test correctness and linear query cost: the quantum rank test uses queries under the same oracle promise.
Simon injectivity decision promise with XOR-oracle access: a table has addresses and output bits per address; the oracle model counts calls separately from an explicit table encoding.
The classes DTIME, NTIME, DSPACE, and NSPACE and Worst-case time and space complexity of a machine: deterministic polynomial time is measured in the length of the explicit binary input.
Circuit-family and computation cost model: named oracle calls and ordinary gate costs are separate resource coordinates.
Counterexample
Let and , the length of the unary-header table code. For each of the distinct address pairs, scan the table to retrieve both -bit outputs and answer NO if they coincide; answer YES if no pair collides. On a promised table this is correct, since YES functions are injective and every NO function has a collision.
One table scan and output comparison take transitions, so the pairs take time. Since , this is ; the explicit-table promise problem is therefore in deterministic polynomial time under [F4].
The oracle bounds in [F1] and [F2] charge calls to or , whereas the explicit-input algorithm charges table scans and ordinary computation as required by [F5]. The deterministic algorithm in step 2.1 contradicts the asserted absence of a polynomial-in- algorithm. Thus this oracle-query separation does not imply superpolynomial classical running time in the explicit-input length. This comparison does not refute an time bound measured in : the explicit table already has length .
Depends on
- Classical randomized Simon decision requires square-root-many queries
- Simon rank test correctness and linear query cost
- Simon injectivity decision promise with XOR-oracle access
- Circuit-family and computation cost model
- The classes DTIME, NTIME, DSPACE, and NSPACE
- Worst-case time and space complexity of a machine
Used by
Nothing in the library uses this result yet.
Dependency tree · two levels
30 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
- Ronald de Wolf, Quantum Computing: Lecture Notes, Chapter 3, Section 3.3.2 (standard reference, not scraped)
- Andrew M. Childs, Lecture Notes on Quantum Algorithms, Chapter 1, Section 1.6 (standard reference, not scraped)