Want to take part in these discussions? Sign in if you have an account, or apply for one below
Vanilla 1.1.10 is a product of Lussumo. More Information: Documentation, Community Support.
I have split off formally unramified morphism from unramified morphism. Then I added the general-abstract topos theoretic characterization, by essentially copy-and-pasting the discussion from formally smooth morphism (and replacing epimorphisms by monomorphisms)
Good. In the scheme context somebody should eventually take EGA IV and write various properties and theorems in that context.
Formal unramifiedness is a condition that is nonsense in the derived setting. It is a first approximation to formal etaleness and a that’s it (that is, in terms of the cotangent complex, it means that its zeroth homotopy vanishes.
I don’t believe that either the Kontsevich-Rosenberg or even the EGA version of formal smoothness is actually accepted in the context of derived algebraic geometry.
For instance, formal smoothness fails to be determined stalkwise.
Formal unramifiedness is a condition that is nonsense in the derived setting.
Yes, and for a good reason: in the -categorical context the statement “epi plus mono is iso” is nonsense. Formal smoothness has a good -version: is formally smooth if (the canonical morphism to the de Rham space) is an effective epimorphism (or similarly for the relative version). And analogously for formal etalness and equivalences. But the mono-condition that gives formally unramified in the 1-categorical context has no good analog.
I do not understand, what is the problem, could you guys explain it to me ? Is it in -only, or also in -context ? You started talking just vague , what is confusing when making statement about different categorical dimensions.
So in the 1-categorical context we look at the morphism
of any space into its de Rham space and consider three cases
it is an epimorphism, then we say is formally smooth;
it is a monomorphism, then we say is formally unramified;
or it is both, hence an isomorphism if we are in a balanced category, then we say is formally étale.
(Or rather, we look at the relative versions of these statements, so that the second two points become useful).
This is equivalent to what Kontsevich-Rosenberg consider, under the dictionary discussed here. Notice that there I write for .
Now when we lift this from 1-category theory to -category theory, the notions of epimorphisms and of monomorphisms multiply. The good notion of epimorphism that we seem to want to keep here is effective epimorphism in an (infinity,1)-category. So we say
A (derived) -stack is formally smooth if is an effective epimorphism.
A (derived) -stack is formally etale if is an effective epimorphism equivalence.
(Or rather, again, the relative versions of these statements.)
But now there is no direct analog of the above mono-condition. We could ask to be a k-truncated morphism for all . For this is an equivalence. So we could say as decreases from to -2 that we are approaching formal etalness.
Hey Urs, by the way, the determination of smoothness by requiring a map to be epi on the dR space only works with Noetherian hypotheses. This is because the nilradical is only a nilpotent ideal provided that R is noetherian.
We still need to go back to the entry de Rham space and fill in all the right technical qualifiers in order to correctly reproduce various traditional notions.
But I am currently taking a general perspective essentially equivalent to that of Kontsevich-Rosenberg’s: since I can define abstractly in great generality, I define formal smoothness in any context by this epi-condition. But then of course, I agree, one wants to carefully state the conditions under which this reproduces various traditional notions.
I have expanded the definition of formal smoothness/unramifiedness/étaleness in the general abstract context of “infinitesimal cohesion” here and added a note highlighting the subtlety about the unramified-condition discussed above.
sorry, that last addition that I mentioned is still not visible. The Lab has been slow all day, but now it takes many minutes to save long entries like that on cohesive -toposes. A steam engine computer would be faster. And apparently we are now actually at the point where it fails to safe at all. Maybe I need to split the entry. Or migrate to another software…
I have split the entry in two. I didn’t see another way out after unsuccessfully trying to safe it for about an whole hour. The paragraph that I had meant to point to above should now be visible here. Not a big deal, that was just meant as a side remark. A side remark that cost me an hour of experimenting.
1 to 12 of 12