Skip to content

Conversation

@jdchristensen
Copy link
Collaborator

The first commit adds faithfulness of the Yoneda embedding, which is used in the next parts. It also adds duals for the 0gpd results, which I hadn't added before.

The next two commits make progress towards showing that the join gives a symmetric monoidal structure. I think all that is missing is the pentagon.

@jdchristensen jdchristensen requested a review from Alizter October 17, 2023 01:42
Require Export WildCat.Square.
Require Export WildCat.PointedCat.
Require Export WildCat.Bifunctor.
Require Export WildCat.Monoidal.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Completely forgot we had this! Looks like there are some incomplete (aborted) results in there still.

(** ** The hexagon axiom *)

(** This describes the transformation on [TriJoinRecData] corresponding to precomposition with [functor_join idmap (join_sym C B)], as in the next result. *)
Definition trijoinrecdata_id_sym {A B C P} (f : TriJoinRecData A B C P)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can be defined ealier in TriJoin right?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It could go in TriJoin, but I think it fits better in JoinAssoc. functor_join idmap (join_sym _ _) is like the twist equivalence, but in the second and third variables, instead of the first and second. So I think it fits in the file where the twist equivalence is studied. It's also a fairly specific result, so is probably best kept close to where it is used.

Copy link
Collaborator

@Alizter Alizter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great stuff!

@Alizter
Copy link
Collaborator

Alizter commented Oct 17, 2023

@jdchristensen Will you try to prove the pentagon next? I had a look and it seems we will probably need a QuadrupleJoin helper with its own induction principle like we do for Tri. It might be possible to get by with just trijoin_ind but maybe there is a pattern for an n-fold join we can exploit here. It would be useful for higher coherences if we ever need it. But honestly I don't think we will ever right down a 2-monoidal category anytime soon, tricats are just too complicated.

@jdchristensen
Copy link
Collaborator Author

Will you try to prove the pentagon next?

@Alizter I'd like to have it, to complete the story, but I'm not sure how to handle the quadruple join. The triple-join induction principle was a lot of work, and while I figured out ways to avoid much of the path algebra, there were still a few cases that needed a 3-cell to be filled. I don't think it would be fun to figure out a 4-cell. I'll think about whether there's a way to push through the pentagon without developing the general theory of quadruple joins...

@jdchristensen jdchristensen merged commit 687e370 into HoTT:master Oct 17, 2023
@jdchristensen jdchristensen deleted the join-hexagon branch October 17, 2023 15:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants