Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: Nicolai Kraus <nicola...@gmail.com>
To: Martin Escardo <escardo...@googlemail.com>,
	"HomotopyT...@googlegroups.com" <HomotopyT...@googlegroups.com>
Subject: Re: [HoTT] Conjecture
Date: Thu, 30 Mar 2017 23:49:49 +0100	[thread overview]
Message-ID: <dfcfdadd-2324-38c0-916b-f0fa3a10d292@gmail.com> (raw)
In-Reply-To: <98e87128-34a8-63a6-a055-8402498ef8b2@googlemail.com>

Interesting construction by Cory and you! And I think I can help
you with the factorisation that you asked for, as follows:

On 29/03/17 23:05, 'Martin Escardo' via Homotopy Type Theory wrote:
> Now, given a directed family (P_i,-,f_i:P_i->X), we want to construct
> its least upper bound.
>
> Its extent of definition is the proposition ||Sigma_i, P_i||, and the
> question is how we define
>
>     f:||Sigma_i, P_i||->X.
>
> We know how to define
>
>     f':(Sigma_i, P_i)->X
>
> [...]
>
> What if X is not a set?

(I assume that it is i : Nat in the above.)
We can construct the proof of constancy for f' by only going
"steps of length 1", i.e. we do it only using the equality proofs
of the form f'(i,_) = f'(i+1,_).
This constancy proof is coherent up to whichever level you want.
By arXiv:1411.2682 Thm 10.5, this means that you can replace the
condition "X is a set" by "X is 1-truncated" or "X is 17-truncated" or
any finite number you want (this uses funext, but nothing else).

With a different strategy, we can do better and drop all assumptions
on X. Given this family (P_i, -, f_i), we can define the HIT R with
constructors

   r : (i : Nat) -> P_i -> R
   s : (i : Nat) -> (p : P_i) -> (r i p) = (r (i+1) (t i p)

(where t i : P_i -> P_{i+1} comes from the proof that the family is
directed).
Now, we can show that R is a proposition. (One way is this: To show
R -> isContr(R), we can assume that we are given (r i p : R), and we
can prove that this is a centre of contraction.)

R is equivalent to ||Sigma_i, P_i||, and it's easy to construct R -> X.

Best,
Nicolai


  parent reply	other threads:[~2017-03-30 22:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27 21:57 Conjecture Martin Escardo
2017-03-29 21:08 ` [HoTT] Conjecture Nicolai Kraus
2017-03-29 22:05   ` Martin Escardo
2017-03-30 10:59     ` Michael Shulman
2017-03-30 19:22       ` Egbert Rijke
2017-03-30 23:02         ` Nicolai Kraus
2017-03-30 22:49     ` Nicolai Kraus [this message]
2017-03-31 16:09       ` Martin Escardo
2017-04-05 19:37         ` Martin Escardo
2017-04-06  0:23           ` Jon Sterling
2017-04-06  5:55             ` Martin Escardo
2017-04-06 12:40               ` Vladimir Voevodsky
2017-04-06 13:50                 ` Martin Escardo
     [not found]                   ` <81c0782f-9287-4111-a4f1-01cb9c87c7e8@cs.bham.ac.uk>
2017-04-06 16:09                     ` Martin Escardo
2017-04-06 11:52             ` Thomas Streicher
2017-04-07  9:49               ` Martin Escardo
2017-04-07 17:11                 ` Michael Shulman
2017-04-07 18:10                   ` Martin Escardo
2017-04-03  0:35 ` Conjecture Daniel R. Grayson
2017-04-03  2:20   ` [HoTT] Conjecture Favonia
2017-04-03  9:56   ` Nicolai Kraus
2017-04-03 11:50     ` Daniel R. Grayson

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=dfcfdadd-2324-38c0-916b-f0fa3a10d292@gmail.com \
    --to="nicola..."@gmail.com \
    --cc="HomotopyT..."@googlegroups.com \
    --cc="escardo..."@googlemail.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).