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.
Keeping records on clients does not imply differential privacy
Example
Let the database be a finite record set, use add/remove adjacency, and let a distributed system release the exact number of records after each client has kept its own record locally. This deterministic count release is not -differentially private for any finite and any .
Example references
Facts & Assumptions
Given: The database domain and exact count mechanism in the Example.
Differential privacy, databases, and add/remove adjacency: differential privacy requires the event inequality for every ordered neighboring database pair and every measurable output event.
Measurable spaces and measurable sets, Probability measures and probability spaces, and Measure kernel and probability kernel: a deterministic count release is a probability kernel into the countable output space equipped with its power-set sigma algebra.
Proof technique: direct.
Proof
Let , , and let . These databases are add/remove neighbors. For the measurable event , and .
The required privacy inequality in the order would read , which is false whenever . Therefore the exact count mechanism is not -differentially private for the stated parameters.
Depends on
Used by
Nothing in the library uses this result yet.
Dependency tree · two levels
8 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.