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.
Binary Kraft criterion for finite positive codeword lengths
Statement
For a finite list of positive integers , there is a binary prefix code on having codeword lengths if and only if
Facts & Assumptions
Given: A finite source alphabet and positive integer lengths .
Kraft inequality and effective prefix-code allocation: Every prefix-free set satisfies ; conversely, a computably enumerable request list with total weight at most one admits an effective prefix-free allocation of the requested lengths.
Finite binary source codes, extension, and expected length: A binary code assigns a nonempty finite binary word to each source symbol.
Binary prefix codes and their code trees: A binary prefix code is nonsingular and no codeword is a proper prefix of another.
Proof
If a prefix code has lengths , its finite set of codewords is prefix-free by [F3]. Apply the first assertion of [F1] to that set; the codewords are distinct by nonsingularity, so its Kraft sum is exactly .
Suppose . Enumerate the finite request list in increasing order of ; this is a computable enumeration, and the requested lengths are positive by hypothesis. The converse in [F1] allocates distinct prefix-free binary words of those lengths. Assign the word allocated to request as . Their positive lengths make a binary source code by [F2]. Distinctness gives nonsingularity and prefix-freeness gives [F3], so the requested binary prefix code exists.
Depends on
Used by
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
- Stanford EE376A, Information Theory Course Notes, Chapter 4: Lossless Compression (standard reference, not scraped)
- MIT OpenCourseWare 6.450, Memory-less sources, prefix free codes, and entropy (standard reference, not scraped)