Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: Michael Shulman <shu...@sandiego.edu>
To: Eric Finster <ericf...@gmail.com>
Cc: "Martín Hötzel Escardó" <"escardo..."@gmail.com>,
	"Homotopy Type Theory" <"HomotopyT..."@googlegroups.com>
Subject: Re: [HoTT] Re: Where is the problem with initiality?
Date: Tue, 5 Jun 2018 13:04:02 -0700	[thread overview]
Message-ID: <CAOvivQwcp9f5gEnNSAo7xfBrWcHG7PFTYWxs+=vgstLftrY-CA@mail.gmail.com> (raw)
In-Reply-To: <CAGYJgtYTURbs98_c4CES7C5nJ6i7RjDycF4ykPWUWk61zifBoA@mail.gmail.com>

On Sat, Jun 2, 2018 at 8:06 AM, Eric Finster <ericf...@gmail.com> wrote:
> Assuming there is an infinity category of elementary infinity-topoi, then I
> can ask the same question as before: is the initial such guy a 1-category.
> This is what, to me, the previous conjecture about categories with families
> was about.
> But now this time you use the word "presented", so I'm not sure if you are
> making a similar statement or not.

Right, presentation is the crucial point.  Let me try to say the same
thing again.

There are three kinds of structures under discussion:

1. 1-categories with families / fibration 1-categories
2. oo-categories with families / fibration oo-categories
3. oo-categories

There is an evident inclusion of (1) into (2), and also an "inclusion"
of (3) into (2) by taking the families to be arbitrary objects in
slices.  And there is also a sort of "reflection" operation from (2)
back into (3) that creates new higher cells out of arrows into path
objects, which I would expect to be some kind of left adjoint to the
"inclusion".  I'm not being precise about what extra structure these
things have, and what the functors between them are, so this is really
just a heuristic that I would expect to be true for any well-behaved
"doctrine" of extra structure that we could add to them.

If the doctrine in question includes things like effective oo-colimits
or univalent universes, then the initial object of (3) will not be a
1-category.  However, the initial object of (1) will always be a
1-category by definition.  The big conjecture is that the inclusion of
(1) into (2) preserves this initial object.  The "reflection", being a
"left adjoint", ought then to preserve initial objects, and therefore
take this initial structured 1-CwF (regarded as a structured oo-CwF)
to the initial structured oo-category -- in particular, making it no
longer a 1-category by adding higher cells coming from arrows into
path objects.

Of course, there will also be *other* objects of (2) that are also
reflected onto the inital object of (3), such as for instance the
inclusion of that initial object itself into (2).  The point is that
the initial object of (3) *can be presented by* the initial object of
(2), which *happens to coincide with* the initial object of (1).

Does that help?

> I guess my position would be that, if we don't allow ourselves to think of a
> HIT presentation as syntax for a higher object, if we insist that the word
> syntax be reserved for set level objects, then higher objects *don't have
> syntax by definition*!
> That seems surprising, since the point of this list seems to be that we have
> found ways to manipulate them syntactically.  :)

Right -- the way that we manipulate them syntactically is by
*presenting* free/initial ones with set-level objects.

> Moreover, there's another reason that this would be strange:
> I mean, after all, kind of the whole point of introducing higher algebraic
> objects is that these objects carry explicit witnesses for all of the
> relations they satisfy.
> And our usual way of equipping objects with this kind of witness is to
> invent syntax for it.
> So shouldn't it somehow be exactly the opposite: shouldn't we think of
> higher objects as *more* syntactic than their set theoretic counterparts?
>
>> Whatever we call them,
>> such things are certainly interesting!  But I'm dubious that we could
>> use them as a foundation for mathematics unless there is also an
>> untyped extrinsic syntax that can be typechecked into them (which
>> might or might not require them to be decidable).
>
>
> Yes, indeed.  Interesting and puzzling.
> And I get your point here.
>
> E.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Homotopy Type Theory" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to HomotopyTypeThe...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

  reply	other threads:[~2018-06-05 20:04 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-22  5:46 Michael Shulman
2018-05-22 16:47 ` Ambrus Kaposi
2018-05-23 16:26 ` [HoTT] " Thorsten Altenkirch
2018-05-24  5:52   ` Michael Shulman
2018-05-24  8:11     ` Thorsten Altenkirch
2018-05-24  9:53       ` Ambrus Kaposi
2018-05-24 17:26         ` Michael Shulman
2018-05-26  9:21           ` Thomas Streicher
2018-05-26 11:47             ` Michael Shulman
2018-05-26 16:47               ` stre...
2018-05-27  5:14                 ` Bas Spitters
2018-05-28 22:39 ` Michael Shulman
2018-05-29  9:15   ` [HoTT] " Thorsten Altenkirch
2018-05-29 15:15     ` Michael Shulman
2018-05-30  9:33       ` Thomas Streicher
2018-05-30  9:37         ` Thorsten Altenkirch
2018-05-30 10:10           ` Thomas Streicher
2018-05-30 12:08             ` Thorsten Altenkirch
2018-05-30 13:40               ` Thomas Streicher
2018-05-30 14:38                 ` Thorsten Altenkirch
2018-05-30 10:53           ` Alexander Kurz
2018-05-30 12:05             ` Thorsten Altenkirch
2018-05-30 19:07               ` Michael Shulman
2018-05-31 10:06                 ` Thorsten Altenkirch
2018-05-31 11:05                   ` Michael Shulman
2018-05-31 19:02                     ` Alexander Kurz
2018-06-01  9:55                       ` Martin Escardo
2018-06-01 17:07                       ` Martín Hötzel Escardó
2018-06-01 17:43                         ` Eric Finster
2018-06-01 19:55                           ` Martín Hötzel Escardó
2018-06-01 20:59                             ` András Kovács
2018-06-01 21:06                               ` Martín Hötzel Escardó
2018-06-01 21:23                                 ` Michael Shulman
2018-06-01 21:53                                   ` Eric Finster
2018-06-01 22:09                                     ` Michael Shulman
2018-06-02 15:06                                       ` Eric Finster
2018-06-05 20:04                                         ` Michael Shulman [this message]
2018-06-02  5:13                                 ` Thomas Streicher
2018-06-01 21:52                               ` Jasper Hugunin
2018-06-01 22:00                                 ` Eric Finster
2018-06-01 21:27                           ` Matt Oliveri
2018-06-02  5:21                             ` Ambrus Kaposi
2018-06-02  6:01                               ` Thomas Streicher
2018-06-02 14:35                           ` Thorsten Altenkirch
2018-05-30 13:30             ` Jon Sterling
2018-06-05  7:52             ` Andrej Bauer
2018-06-05  8:37               ` David Roberts
2018-06-05  9:46                 ` Gabriel Scherer
2018-06-05 22:19                 ` Martín Hötzel Escardó
2018-06-05 22:54                   ` Martín Hötzel Escardó
2018-06-05 22:12               ` Richard Williamson
2018-06-06 15:05                 ` Thorsten Altenkirch
2018-06-06 19:25                   ` Richard Williamson
2018-05-29 14:00   ` Jon Sterling
2018-05-30 22:35     ` Michael Shulman
2018-05-31 10:48       ` Martín Hötzel Escardó
2018-05-31 11:09         ` Michael Shulman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAOvivQwcp9f5gEnNSAo7xfBrWcHG7PFTYWxs+=vgstLftrY-CA@mail.gmail.com' \
    --to="shu..."@sandiego.edu \
    --cc="HomotopyT..."@googlegroups.com \
    --cc="ericf..."@gmail.com \
    --cc="escardo..."@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).