Res Agentica
Reading

No saved reading position.

Reading

No saved reading position.

Univalence: What It Means Here

Appendix D

3 min read
Aa
Text size

If two types are equivalent, can you substitute one for the other—and with what evidence? The univalence axiom identifies equivalence with equality in a specified type-theoretic universe. This appendix states the axiom and defines transport. Chapter 14 then asks what evidence a receiving operation needs when a deployed evaluator is used for a proposed substitution.

The Univalence Axiom

Univalence Axiom

For types AA and BB in a universe U\mathcal{U}, the canonical map idtoeqv:(A=B)→(A≃B)\mathsf{idtoeqv} : (A = B) \to (A \simeq B) is an equivalence. That is: (A≃B)≃(A=B)(A \simeq B) \simeq (A = B).

An equivalence supplies an identification in the univalent universe. A type family can transport along that path. This does not assert literal equality of external identifiers or unchanged application evaluators; the relevant data move through the identification.

Transport

Transport

Given a type family P:U→UP : \mathcal{U} \to \mathcal{U} and an identification p:A=Bp : A = B, transport is the function transportP(p):P(A)→P(B)\mathsf{transport}^P(p) : P(A) \to P(B). It moves data, proofs, and constructions across the identification.

Transport along an identity is supplied by identity elimination without assuming univalence. Univalence supplies an identification from a type equivalence; computation along that identification depends on the foundation. In axiomatic HoTT, some transported terms are "stuck" (they have the right type but don't reduce to canonical forms). Cubical type theory solves this by making transport a definable operation. The main text does not assume computational univalence.

Engineering Univalence (A16)

Engineering Univalence (A16)

To substitute BB for AA in a context expecting AA, you must provide a witnessed equivalence e:A≃Be : A \simeq B and, for each property PP the context relies on, an explicit transport certificate τP:P(A)→P(B)\tau_P : P(A) \to P(B) that computes the transported property. Within this proposed contract, substitution requires both to be checked for the actual scope, evaluator versions and intended use. A serialized certificate assertion is not its own verification.

AspectFull UnivalenceEngineering Univalence (A16)
FoundationHoTT / Cubical Type TheoryPractical systems
GuaranteeA type equivalence supplies an identification; transport follows by identity eliminationThe required property maps and their grounds must be supplied
ComputationConstructive settings supply computational rules; axiomatic terms may not reduceThe supplied operation must meet its declared verification and execution contract
RequirementEquivalence witnessEquivalence witness + transport certificates
Failure modeFailure to supply the required typed termFailed scope or property obligation; missing grounds and unfinished checking remain distinct

A16 is a proposed engineering discipline inspired by this substitution question, not a machine-checked implementation of the axiom. An implementation can exhibit particular property maps and checks without adopting univalent foundations. Its claim reaches the maps and conditions it actually supplies.

← Back to AppendicesBack to The Proofs →

Search the book

Use ↑ ↓ to move through results; Escape to close.

Search every published chapter, section and reference.

    In this chapter