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.
Counting Complexity and Sharp-P: Examples and Counterexamples
1 · Prerequisites
- Construction of the Natural Numbers
- Construction of the Real Numbers via Cauchy Sequences
- Construction of the Real Numbers via Dedekind Cuts
- Countability and Uncountability
- Counting Complexity and Sharp-P
- Finite Counting, Factorials and Binomial Coefficients
- Formal Languages, Encodings, and Decision Problems
- Foundations of the Real Numbers for Analysis
- Linear Recurrences and Rational Generating Functions
- P, NP, coNP, and Polynomial Reductions
- Relations, Functions, and Quotients
- Resource Bounds and Machine Invariance
- Sequences and Limits
- The ZFC Axioms and the Basic Set Constructions
- Turing Machines, Configurations, and Computation
2 · Summary
This draft page develops the assigned conventions and keeps every resource, type, and quantifier explicit.
3 · Logical flowchart
4 · Definitions, theorems and proofs
None yet.
5 · Examples, counterexamples and false statements
A two-branch computation and its parsimonious tableau formula
Statement
On empty input, let make one nondeterministic choice , record in its state, and accept. Its two accepting paths give two legal padded tableaux, and the exact Cook--Levin encoding has exactly two satisfying assignments.
Facts & Assumptions
Given: the displayed one-choice machine .
The Cook--Levin construction can be made parsimonious. by The Cook--Levin construction can be made parsimonious.
Verification
The paths are start $\xrightarrow{0}$ accept-with-tag-$0$'' and start accept-with-tag-''. Padding repeats the final configuration, so these give two and only two legal accepting tableaux.
In the exact encoding of [L1], the tableau variables are uniquely fixed by one of these tableaux and every auxiliary variable is constrained by a biconditional with the subformula it names. Equivalently, after eliminating those uniquely determined variables, the formula is the tautology with declared variable . Its two assignments correspond bijectively to the two paths.
Therefore the source accepting-path count and the formula's satisfying- assignment count are both exactly .
Deciding satisfiability by a NumberSAT oracle query
Statement
For with declared variables , one NumberSAT query returns (binary ), so a nonzero test decides that is satisfiable.
Facts & Assumptions
Given: the displayed formula and declared-variable list.
NumberSAT is the exact number of satisfying declared assignments. by NumberSAT.
Verification
The formula is equivalent to : the assignments and satisfy it, while and do not. Thus [L1] gives , returned as .
Testing the returned integer against zero accepts, which is correct because the displayed satisfying assignments exist. The single exact query summarizes all four assignments.
This is the promised finite instance of the route.
NumberSAT is not a Boolean membership predicate
Statement
With declared variables , let and . Then NumberSAT returns and , respectively, although the SAT membership predicate returns yes on both.
Facts & Assumptions
Given: the two displayed formulas and their declared-variable lists.
NumberSAT is a numerical function rather than a Boolean predicate. by NumberSAT.
Counterexample
Exactly three assignments satisfy . Exactly the two assignments with unequal bits satisfy . Hence [L1] gives outputs and , neither in the Boolean codomain .
Both counts are positive, so the associated SAT predicate maps both inputs to yes. It therefore discards information that NumberSAT retains.
These explicit values show that NumberSAT is a numerical function, not a Boolean membership predicate.