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 power-set functor is lax monoidal but not strong
Example
Let be the covariant power-set functor: on a function , it sends to its direct image . For sets , define
and let
pick the unique subset of the singleton set.
Facts & Assumptions
Given: The power-set construction and the cartesian monoidal structure on .
is the set of all subsets of (The power set ).
Lax, strong, and strict monoidal functors are distinguished by their structure maps and whether those maps are isomorphisms (Lax, strong, and strict monoidal functors).
is cartesian monoidal (Set, Cat, and every complete category are cartesian monoidal).
Verification
Direct images preserve identities and composition, so the displayed action on functions makes a functor. By [L1] and [L3], the map is well typed: if and , then . For functions and , one has , so is natural. The unit map is also well typed because a singleton set has exactly one subset equal to itself.
For subsets , , and , both sides of the lax associativity axiom send to the subset of consisting of all with , , and . The left and right unit axioms likewise send and back to . Hence is lax monoidal.
Take . The diagonal subset is not of the form for subsets and . So is not surjective, hence not an isomorphism.
Therefore the power-set functor is lax monoidal but not strong.
Depends on
Used by
Nothing in the library uses this result yet.
Dependency tree · two levels
13 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.