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.
The objectwise cokernel presheaf can fail to be a sheaf
Statement refuted
For a morphism of sheaves of abelian groups, the objectwise cokernel presheaf is automatically a sheaf.
Facts & Assumptions
Given: The circle , the sheaf of continuous real-valued functions, and the subsheaf of locally constant integer-valued functions.
Cokernel sheaves are obtained by sheafifying the objectwise cokernel presheaf (Kernel sheaves are objectwise, while cokernels and images are sheafified).
Counterexample
Let be the presheaf cokernel of the inclusion , so for each open . Cover by the arcs and , and choose continuous angle functions and with . On , the difference is locally constant integer-valued, so the classes and agree on the overlap.
If these local classes came from a global class , then on each arc the difference would be integer-valued and continuous, hence constant because is connected. On the two connected components of , this would force the same constant difference to be both and , which is impossible. Therefore the compatible local classes of step 1.1 do not glue in the presheaf .
So the objectwise cokernel presheaf is not a sheaf. By [F1], this is exactly why one sheafifies it to obtain the true cokernel sheaf. The statement is false.
Depends on
Used by
Nothing in the library uses this result yet.
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
- The Stacks Project, Section 17.3 (standard reference, not scraped)
- Ravi Vakil, The Rising Sea, Proposition 2.6.1 (standard reference, not scraped)