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.
Hadamard linearity constraint system
Definition
Let and let be a fixed table, in the conventions of The BLR linearity test over F_2. The Hadamard linearity constraint system is the constraint system of arity at most over the alphabet of Assignment tester and rejection ratio whose variables are the table coordinates — one variable per cube point, so — and whose constraint list contains, once for each ordered pair , the ternary constraint with variable tuple and relation the addition being modulo two. The list is a list, so constraints belonging to different pairs are counted separately even when they coincide as tuples.
Since range over the whole cube, the variable tuple of a constraint may repeat coordinates — for instance for the pair , and for — and the satisfaction rule of a constraint system is the substitution rule: the tuple is satisfied by a labeling exactly when , coinciding coordinates being read as the single symbol assigned to them. The same substitution covers the degenerate cases: the pair forces , and for the cube has one point, the list has the single constraint with tuple , and the system is satisfied exactly by the table .
Value and rejection probability. For a labeling of — that is, an arbitrary table — the fraction counts the satisfied constraints among the listed pairs, and . For the fixed table we write the rejection probability of the linearity system, which is exactly the BLR rejection probability of in the sense of The BLR linearity test over F_2: the pair is drawn uniformly in the test and the listed constraint at that pair is violated precisely when the test rejects. In particular a uniformly random constraint of the system involves the three coordinates and is checked with three table queries and random bits.
Perfect completeness. Every linear table passes. If for some , then for all the distributivity of the dot product over addition in gives , so every constraint of the system is satisfied and . The system is explicit: its constraint tuples and its single fixed relation table are enumerated by the displayed rule, and its size is determined by alone.
Remarks
- One constraint per test, not one per violation pattern. The system records multiplicity: the pairs and give two constraints, and a pair with still gives one constraint. This is what makes equal — not merely comparable — to the rejection probability of the sampled BLR test, and it is the convention used by the exponential-base tester of An exponential-size constant-query base assignment tester, where every random choice of the verifier is materialized as one constraint.
- Relation to the proximity definition. The system constrains table coordinates, not inputs of a circuit: in the language of Assignment tester and rejection ratio the whole cube of table positions is the auxiliary part of the variable set, and the rejection probability is the quantity the soundness clause controls. The distance of a table from the linear tables is a property of the labeling of these coordinates, and BLR rejection is proportional to distance from linearity is the statement that the violated fraction is at least that distance.
- No random sampling is part of the definition. Sampling the pair is a way of estimating the value of an explicit, fully listed system; the system itself is deterministic and independent of any randomness, and it is produced by enumerating the pairs, which is polynomial in the size of the listing but exponential in as a description of requires.
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: A Modern Approach, §18.4.1 Definition 18.22 and Theorem 18.23, printed pp. 363-364. (standard reference, not scraped)
- Irit Dinur, The PCP theorem by gap amplification, §5 (Hadamard encoding and linearity tests), printed pp. 17-18. (standard reference, not scraped)