You're reading the public-facing archive of the Category Theory Zulip server.
To join the server you need an invite. Anybody can get an invite by contacting Matteo Capucci at name dot surname at gmail dot com.
For all things related to this archive refer to the same person.
I've been refactoring the nlab pages for the various ways in which functors can interact with limits - preservation, reflection, creation, lifting. In this post, I'll use the equivalence-invariant definition of lifting, which only requires lifts of limiting cones to exist up to isomorphism.
With regards to creation of limits - is it true that a functor creates limits if and only if it both reflects and lifts them? Spelling this out in detail:
Thus, lifting and reflection together imply the following property:
It's easy to see that this property implies lifting. Moreover, it also implies reflection - if we have a cone for such that is limiting for , then we know there exists, up to iso, a unique whose image under is isomorphic to - in particular, is necessarily isomorphic to . But then, since is limiting, so is .
From what I can remember of my course, this property is equivalent to creation of limits. So I wanted to check - is it sensible to view "creation" as the conjunction of "lifting" and "reflection"? There's a separate issue as to whether you should require the limit to actually exist in the codomain.
Incidentally, MacLane's "strict" definition of creation of limits seems to be a strictified version of the property I laid out. It says:
So this gives me some confidence that "reflection + lifting" is the morally correct definition for creation. I know that this terminology is used for other kinds of structure besides limits and colimits; in those cases, is it still sensible to think of creation as reflection + lifting? I'm curious whether it might be useful to have an nlab page dedicated to explaining "preservation, reflection, lifting" of structure in the general sense.
(looks right to me!)
Thanks Morgan! I’ll update the nlab pages accordingly, and also make a dedicated page for “preservation, reflection, lifting of structure”
I noticed the nLab page defines what it means for a functor to create limits of a specific diagram in the domain . My initial reaction was, it would be more intuitive to define what it means for to create limits of a specific diagram in the codomain . There is no difference between these if we want to talk about functors creating a general class of limits. But in my head, we "lift" or "reflect" particular limit diagrams in the codomain to obtain limit diagrams in the domain. What do you think?
This is also how creation appears in practice. Monadicity theorems are about creation of specific colimits in the codomain, and (relatedly) monadic functors create colimits in the codomain preserved by the monad and its square .
Actually, maybe it's best to have both options available. It could make sense to speak of a functor reflecting/lifting/creating limits of a diagram in the domain as well as to speak of a functor reflecting/lifting/creating limits of a diagram in the codomain.
What definition do you suggest for a functor reflecting limits of a diagram in the codomain?
The definition of reflection in the domain is that you have , and that any cone for that is mapped to a limit cone for must already be a limit cone for .
If we instead have , it’s not clear to me how we phrase reflection?
Ah, sorry for being unclear. I would just say limits of a diagram in the codomain are reflected/lifted/created if, in the current terminology, limits of all diagrams in the domain sent to it are reflected/lifted/created.
For example a diagram is reflected if any cone to a diagram in the domain sent to a limit cone of is a limit cone.
The other definition is more general, but this definition matches my use cases more closely. I had defined creation this way in a paper I'm currently writing, but maybe that's not normal.
Hm so unfolding this - you have a diagram in the domain with a cone, and then applying gives a cone over . Presumably to say this is "sent to a limit cone of " we need and some specified natural transformation ? But now it seems you have many ways to specify such a natural transformation.
I would put .
Maybe people don't do this because it's not respected by equivalence. You could have something respected by equivalence by only requiring , similarly to what you said. Do you see any problem with that?
Hm, lemme think. So we have a diagram and a functor . We say that reflects limits of if, whenever you have a diagram with and a cone for that maps under to a limiting cone, then it was already a limiting cone for .
In other words, reflects limits for if and only if any diagram with has its limits reflected by . I guess that would be invariant under equivalence?
Maybe all you want is "F reflects limits of shape I"?
Yeah, that's what I'm thinking for the equivalence-invariant version. Though I had by default been using on the nose.
It's very possible nobody else but me finds this way more intuitive!
My motivation is that when we use creation of colimits in situations related to monadicity, we're talking about creation of colimits of specific diagrams in the codomain. (In particular, not just all diagrams of a specific shape.)
Hm, I think there’s a detail I’m missing - which diagrams for monadicity are we saying get created in the codomain?
The main result I know is that monadic functors create all limits, and create all colimits that T and TT preserve
A right adjoint functor is monadic if and only if it creates split coequalizers in the codomain.
https://ncatlab.org/nlab/show/monadicity+theorem
Another formulation is that a right adjoint functor is monadic if and only if it creates absolute colimits in the codomain.
Right but the definition here is really still the standard one right? You have a parallel pair in which, if you set , can be viewed as a diagram . Then you focus on a particular subset of these diagrams, those which are mapped to split coequalisers under .
Then the statement is that, if is -split, then creates coequalisers of , in the ordinary sense. Importantly I think "creates split coequalisers" could be misleading, since we're only guaranteed a coequaliser diagram in , not a split one.
The part that says "there exists a coequaliser of in which is preserved by " is saying that lifts coequalisers (i.e. colimits) for , and the part that says "any fork in whose image in is a split coequaliser must itself be a coequaliser" is saying that reflects coequalisers for , if I understand correctly.
That page on the nLab is using the standard definition, right. In contrast, I stated these results using the non-standard definition of creation of colimits in the codomain from this thread.
Yeah, "creates split coequalizers in the codomain" could be misleading. Less concisely, "creates coequalizers that are split coequalizers in the codomain" might be better. To me it's more understandable than "creates -split coequalizers", though others may disagree.
I think it's definitely more understandable but people wanted some kind of plausible shorthand.