added pointer to:

- David Wärn,
*Eilenberg-MacLane spaces and stabilisation in homotopy type theory*[arXiv:2301.03685]

39 looks good to me.

]]>Added the following new subsection:

It is possible to define torsors using a single-sorted algebraic theory. This is entirely analogous to how affine spaces can be defined either as sets with a free and transitive action of a vector space, or, equivalently, as sets equipped with operations that take arbitrary affine combinations with coefficients in a given ring.

More precisely, a **torsor** (also
known as a heap when stated in a single-sorted form)
is a set $T$ equipped with a ternary operation

such that

$t(a,a,b)=t(b,a,a)=b,\qquad t(t(a,b,c),d,e)=t(a,b,t(c,d,e)).$A **homomorphism of torsors** is a map of sets that preserves this operation.

The equivalence with the two-sorted definition is demonstrated as follows.

Given a $G$-torsor $T$, we send it to the set $T$ equipped with the ternary operation $t(a,b,c)=g(a,b)c$, where $g(a,b)$ is the unique element of $G$ such that $g(a,b)b=a$.

Given a torsor $(T,t)$, we send it to the pair $(LTrans(T),T)$, where $LTrans(T)$ is a subgroup of the group of bijections on the set $T$ comprising precisely the bijections of the form $c\mapsto t(a,b,c)$ for some elements $a,b\in T$. The group $G$ acts on $T$ by evaluation: $gt=g(t)$.

Mapping $(T,t)\mapsto (LTrans(T),T)\mapsto (T,t)$ gives back the same torsor $(T,t)$ that we started from.

Mapping $(G,T)\mapsto (T,t)\mapsto (LTrans(T),t)$ produces a torsor $(LTrans(T),t)$ that is naturally isomorphic to $(G,T)$ via the isomorphism

$(G,T)\to(LTrans(T),T),\qquad g\mapsto (t\mapsto gt),\qquad t\mapsto t.$ ]]>Example. Given two isomorphic objects $X$ and $Y$ in any category $C$, all isomorphisms between $X$ and $Y$ form a torsor (both for $Aut(X)$ and for $Aut(Y)$, which are mutually isomorphic but not canonically). This is an insight used in (M. Kontsevich, *Operads and motives in deformation quantization*, Lett.Math.Phys.48:35-72 (1999) arXiv:math/9904055 doi) explaining period matrices from the point of view of a coordinate ring of an affine torsor.

27

The precise meaning of this statement is unclear to me, but under the most obvious interpretation, this does not seem to be the case

I was not claiming that there is no equivalence of categories at all, but taking the point of view of Bergman’s book and most of the heap tradition, that a heap is canonically obtained by a forgetful functor from groups, while the group for a torsor is tipically external, set theoretically not sharing the underlying set with the heap. As you know, to get the group back with the same underlying set you have to specify the unit, it is like choosing a section of a principal bundle. The corollary is that every identity for the ternary operation of the heap follows from the 3 relations in the definition. It is less obvious to see that from the perspective of reconstructing the automorphisms as a functor to groups (which never reconstructs identically the identical set).

To see that it is less obvious to see there are no additional relations (less obvious for those who did not see it yet), let me tell you a personal story for the quantum case. In the quantum case, I observed the analogue of the theorem Hopf algebras are equivalent to copointed quantum heaps, and some related things, in 2000. Grunspan put his definition of “quantum torsor” (with a definition relative over a base, but the rest was over the field like in my case) a year or two later with an additional relation in the definition. He was working with an automorphism point of view and wrote 4 axioms in quantum case and proved reconstruction of a Hopf algebra of automorphisms, left or right. For his definition, it took Peter Schauenburg to write a separate paper to show that the relation 4 is not needed. From the point of view of choosing a character in my picture it is obvious and I never had an idea of a need for the strange 4th relation of Grunspan. Though this was a research of one evening (prompted by a lecture of an algebraic geometer in 1999 on moduli of bundles, mentioning some problem with automorphisms) I was a little bit disappointed that neither of them cited my result although I had correspondence with both immediately when their papers appeared and my thesis had been defended earlier. T. Booker and R. Street had a paper later on the wider context

- Thomas Booker, Ross Street,
*Torsors, herds and flocks*, J. Algebra 330 (2011) 346–374 pdf arXiv:0912.4551

In my memory, in the principal bundle community, Anders Kock spent much time on various axiomatics of division/translation operation for principal bundles in synthetic approach, working with $a^{-1}b$ notation and $a\backslash b$ notation, but still the fact that if one focuses on the ternary relation instead, only 3 relations are enough is not discussed I think.

]]>Re #30:

Now, groups are (equivalently) pointed, connected groupoids, while heaps are bipointed, connected groupoids. The underlying set of a heap is the set of isomorphisms from the first to the second point. There are two canonical maps from heaps to groups, the left and right automorphism group, and these are only merely isomorphic (unless they are abelian). So when we think of a heap as a group G together with a G-torsor, there’s a bias built in: we have two G-torsors and one is deemed “untwisted” and the other “twisted”, but we could have picked the opposite convention.

Yes, but this is entirely similar to the situation with rings and modules: every abelian group A has a canonical structure of a left End(A)-module and a right End(A)^op-module. The left action is privileged here because endomorphisms are composed from right to left.

Likewise, every heap H has a canonical action of LTrans(H) on the left and RTrans(H)^op on the right. Again, the left action is privileged here because endomorphisms are composed from right to left.

But I agree with the mathematical content.

]]>Yes absolutely, it looks good.

]]>Yeah, but there is a conflict with convention. I do think now one should say “pseudo torsor” for the possibly empty version. But all is good, I have added the pointer to the entry.

]]>Hi Urs, thanks for taking a look! Regarding the empty torsor, I probably should have drawn explicit notice to this, apologies! I made the change partly because it is obviously makes sense and is more elegant/can be formulated in a simpler logic without the inhabitedness condition, leading to a nicer category; and also because in recovering a group making a *choice* of point is important, and any choice is as good as any other, so requiring inhabitedness is sort of misleading from one perspective, especially if one has a constructive mindset, because it draws attention to one point over the others.

Added mentioning that non-inhabited torsors are also called *pseudo-torsors*.

I hope somebody finds the time to work this good material into the entry!

While that is underway, I see that long ago on MO here people suggested that “pseudo torsor” should be used for not-necessarily-inhabited torsors, to avoid confusion. The StacksProject agrees (here) and apparently this terminology goes back to EGA IV 16.5.15, though I have not checked.

But, yeah, some such terminological distinction would be good to retain, for clarity.

]]>Maybe a bit of philosophy can help; to paraphrase Quine: “No entity without (a notion of) identity”. That is, a (mathematical) notion comes with a notion of identity/isomorphism/equivalence. So two notions are the same if they present the same homotopy type. I think we agree on that.

The point is that the type of $G$-torsors does not embed into the type of heaps, which as noted above is equivalent to the total type of torsors, $Tors = \sum_{G:Group}G\text{-}Tors$. Just like the type of complex vector spaces doesn’t embed into the total type of modules, $Mod = \sum_{R:Ring}R\text{-}Mod$, because we pick up isomorphisms from the base in either case.

Now, groups are (equivalently) pointed, connected groupoids, while heaps are bipointed, connected groupoids. The underlying set of a heap is the set of isomorphisms from the first to the second point. There are *two* canonical maps from heaps to groups, the left and right automorphism group, and these are only merely isomorphic (unless they are abelian). So when we think of a heap as a group $G$ together with a $G$-torsor, there’s a bias built in: we have two $G$-torsors and one is deemed “untwisted” and the other “twisted”, but we could have picked the opposite convention.

Now, as also mentioned above, the type of heaps embeds into the algebraic type of associative Mal’cev structures. The empty such arises as the isomorphisms between disconnected objects in a groupoid.

]]>hyperlinking *shear map*

It’s really not important whether the articles are separate or not, there is never an objective way to make such design decisions.
Important would be, instead, that each article makes it crystal clear that there are different notions, and how, and to *point to the other article* – and any other related article – as need be.

So if you reconstruct the group as the set itself then you need a choice of a (unit) element to make it into the group canonically.

The precise meaning of this statement is unclear to me, but under the most obvious interpretation, this does not seem to be the case.

The functor F from heaps to torsors sends a heap H to the torsor (LTrans(H),H), where LTrans(H) is a group whose elements are maps of sets f: H→H of the form h↦t(a,b,h) for some a,b∈H. The group LTrans(H) acts on the set H from the left: (f,h)↦f(h), turning H into an LTrans(H)-torsor.

The functor G from torsors to heaps sends a torsor (G,H) to the heap H (with the obvious ternary operation).

The composition GF is the identity functor.

The composition FG is the functor from torsors to torsors that sends a torsor (G,H) to the torsor (LTrans(H),H).

The identity functor is naturally isomorphic to FG via the isomorphism (G,H)→(LTrans(H),H) that is given by the identity map on H and the isomorphism of groups G→LTrans(H) that sends an element g to the map of sets H→H given by h↦gh.

Thus, the categories of heaps and torsors are equivalent. There are no noncanonical choices of unit elements needed here.

]]>or alternatively – if you take the underlying set – then up to a choice of unit.”The identity map…”

Yes, no choices for identity if you reconstruct it as an automorphism, but alternatively if you take a group and make the ternary operation then the forgetful functor forgets only the unit element. So if you reconstruct the group as the set itself then you need a choice of a (unit) element to make it into the group canonically. For torsor the group is given by the definition, while here you have to choose a point. This is the point of view of say, Bergman’s book cited under heap. Similarly in nc case, you have to add a character to get from a quantum heap to a Hopf algebra.

]]>while for heap the group is determined only up to automorphism, or alternatively – if you take the underlying set – then up to a choice of unit.

Up to a *unique* automorphism. Given a heap H, the corresponding group has as its underlying set
all maps H→H of the form h↦t(h,a,b) for some a,b∈H.
The identity map H→H is the identity element in the group.
This construction is completely canonical, there are no choices involved.

In (dual) noncommutative case is even worse as there are left and right automorphisms, and Grunspan has some example where this is essentially different.

This is entirely analogous to how there are left and right modules over a noncommutative ring, which further reinforces the analogy.

]]>I do not think that it is the same as your example with modules and rings. Module has its ring as part of the data, while for heap the group is determined only up to automorphism, or alternatively – if you take the underlying set – then up to a choice of unit. In (dual) noncommutative case is even worse as there are left and right automorphisms, and Grunspan has some example where this is essentially different.

]]>We have separate articles for presheaf and a functor, a separate article for action and for a module (and even representation) and a separate entry for principal bundle and for torsor. Edit: and groupoid versus Brandt groupoid (original algebraic equivalent of connected groupoid as partial binary structure). (This was all consciously made separate).

The point of view, generality and tradition is different. There are specifics of universal algebra for heaps while torsors are a more categorical and geometric topic. I think that mixing all the details from algebraic tradition in already complicated entry torsor will not do any good, nor will help people who want to consult only algebra.

]]>Re #21: But this is like saying that we should have a separate article for a module over a fixed ring R, and a separate article for a module over an arbitrary ring, i.e., the category whose objects are pairs (R,M), R∈Ring, M∈Mod_R, and morphisms (R,M)→(R’,M’) are pairs (f:R→R’,M→f*M’).

Indeed, the situation for heaps and torsors is entirely analogous: a torsor is over a fixed group G and a heap is over an arbitrary group.

The article heap even says so explicitly in Section 4:

In fact, the category Heap is equivalent to the following category Tors: its objects are pairs (G,H) consisting of a group G and a G-torsor H, and its morphisms are pairs (ϕ,f):(G,H)→(G’,H’) consisting of a group homomorphism ϕ:G→G’ and a ϕ-equivariant map f:H→H’.

By the way, this statement is not quite correct: if a G-torsor is allowed to be empty, then we have many nonisomorphic empty torsors, one for each isomorphism class of groups. On the other hand, if a G-torsor is required to be nonempty, than the empty heap does not correspond to such a pair (G,H).

]]>Well, heap is not quite the same thing as torsor in general, at least it is different point of view, tradition and context. The usual term in universal algebra is associative Mal’cev structure.

For example, torsor is relative to a fixed group, and then you can think of a relative case (torsor for a sheaf of groups) etc. while heap is an algebraic structure.

Next, when we talk about category of torsors you usually mean a category for a given group $G$, while the category of heaps is category where morphisms may change the group in the sense that the morphism corresponds to a pair of an equivariant morphism of groups and a compatible map on the level of torsors.

]]>If you have energy for a major reorganization… But if you could just add prominent cross-links and import whatever is worth importing, it would already be an improvement.

]]>I found out that we already have it explained here: https://ncatlab.org/nlab/show/heap#heaps_and_torsors.

Do we need a separate article “heap” describing essentially the same thing as a torsor? Should the two articles be merged?

]]>Please do add that to the entry, if you have the energy!

]]>