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.
Record-level versus client-level adjacency
Example
Model a database as a finite-support count function , where is the record universe, and call two databases neighbors when one is obtained from the other by adding or removing one record occurrence. Suppose one client contributes 100 identified record occurrences to a database. Removing or adding any one of those occurrences is one neighboring step, while changing the database by the client’s entire 100-record contribution is not one neighboring step. A client-level guarantee therefore requires a client-level adjacency relation that treats that full contribution as one change and a proof using that relation.
Example references
Facts & Assumptions
Given: A finite-support count database and 100 identified record occurrences contributed by one client.
Database is a finite-support record-count function, and two databases are neighbors exactly when one is obtained from the other by adding or removing one record occurrence.
Scope distinction: the page definition is central record-level add/remove privacy and does not itself define client-level privacy.
Verification
List the client’s 100 occurrences as , with repetitions allowed. For , let . Then and differ by adding one occurrence, so [F1] makes each consecutive pair neighbors.
The count-function difference between and has total absolute count , counting repeated contributions with multiplicity. A single add/remove neighbor pair has this total equal to by [F1]. Hence the full contribution is not a record-level neighboring step. Treating it as one step changes the adjacency relation, and [F2] says that any claimed client-level guarantee needs that relation and a proof under it.
Depends on
Used by
Nothing in the library uses this result yet.
Dependency tree · two levels
5 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
- Cynthia Dwork and Aaron Roth, The Algorithmic Foundations of Differential Privacy (standard reference, not scraped)
- Salil Vadhan, The Complexity of Differential Privacy, 2017 manuscript (standard reference, not scraped)