Each relation below starts at this concept.
This is an authored directed relation from the source endpoint to the target endpoint.
- Relation ID
category_to_cartesian- Relation type
- Add data
add-data - Direction
- source → target
- Endpoint roles
- source: Builds toward; target: Built from
- Authored annotation
- add finite products
Authored explanation
Choose a terminal object and binary products satisfying their universal properties.
How to interpret this relation type
Equip an existing carrier or structured object with additional chosen data, when such compatible data exists. Use a construction junction when several independently meaningful inputs must coexist on the same carrier or interact compatibly.
This is an authored directed relation from the source endpoint to the target endpoint.
- Relation ID
e_category_dagger- Relation type
- Add data
add-data - Direction
- source → target
- Endpoint roles
- source: Builds toward; target: Built from
- Authored annotation
- + dagger involution
Authored explanation
Add an involutive identity-on-objects contravariant endofunctor.
How to interpret this relation type
Equip an existing carrier or structured object with additional chosen data, when such compatible data exists. Use a construction junction when several independently meaningful inputs must coexist on the same carrier or interact compatibly.
This is an authored directed relation from the source endpoint to the target endpoint.
- Relation ID
category_to_finitely_complete- Relation type
- Impose axiom
impose-axiom - Direction
- source → target
- Endpoint roles
- source: Builds toward; target: Built from
- Authored annotation
- require finite limits
Authored explanation
Require every finite diagram to have a limit.
How to interpret this relation type
Keep the existing data and select the subclass satisfying an additional law, existence condition, finiteness condition, or other property.
This is an authored directed relation from the source endpoint to the target endpoint.
- Relation ID
story_category_to_functor_add_data- Relation type
- Add data
add-data - Direction
- source → target
- Endpoint roles
- source: Builds toward; target: Built from
- Authored annotation
- map categories structure-preservingly
Authored explanation
Choose a target category and specify object and morphism assignments that preserve identities and composition.
How to interpret this relation type
Equip an existing carrier or structured object with additional chosen data, when such compatible data exists. Use a construction junction when several independently meaningful inputs must coexist on the same carrier or interact compatibly.
This is an authored directed relation from the source endpoint to the target endpoint.
- Relation ID
category_to_groupoid- Relation type
- Impose axiom
impose-axiom - Direction
- source → target
- Endpoint roles
- source: Builds toward; target: Built from
- Authored annotation
- require invertible arrows
Authored explanation
Require every morphism to have a two-sided inverse.
How to interpret this relation type
Keep the existing data and select the subclass satisfying an additional law, existence condition, finiteness condition, or other property.
This is an authored directed relation from the source endpoint to the target endpoint.
- Relation ID
j_cosimplicial_object__category- Relation type
- Combine compatible structures
combine-compatible - Direction
- source → target
- Endpoint roles
- source: Builds toward; target: Built from
- Authored annotation
- ambient category
Authored explanation
Supply the category in which the diagram takes values.
How to interpret this relation type
Feed several structures into a construction junction and impose compatibility between them.
This is an authored directed relation from the source endpoint to the target endpoint.
- Relation ID
j_simplicial_object__category- Relation type
- Combine compatible structures
combine-compatible - Direction
- source → target
- Endpoint roles
- source: Builds toward; target: Built from
- Authored annotation
- ambient category
Authored explanation
Supply the category in which the diagram takes values.
How to interpret this relation type
Feed several structures into a construction junction and impose compatibility between them.
This is an authored directed relation from the source endpoint to the target endpoint.
- Relation ID
e_category_model- Relation type
- Add data
add-data - Direction
- source → target
- Endpoint roles
- source: Builds toward; target: Built from
- Authored annotation
- + weak equivalences, fibrations, cofibrations
Authored explanation
Add three morphism classes satisfying Quillen model-category axioms.
How to interpret this relation type
Equip an existing carrier or structured object with additional chosen data, when such compatible data exists. Use a construction junction when several independently meaningful inputs must coexist on the same carrier or interact compatibly.
This is an authored directed relation from the source endpoint to the target endpoint.
- Relation ID
category_to_monoidal- Relation type
- Add data
add-data - Direction
- source → target
- Endpoint roles
- source: Builds toward; target: Built from
- Authored annotation
- add tensor and unit
Authored explanation
Add a tensor bifunctor, unit object, associator, and unitors satisfying coherence.
How to interpret this relation type
Equip an existing carrier or structured object with additional chosen data, when such compatible data exists. Use a construction junction when several independently meaningful inputs must coexist on the same carrier or interact compatibly.
This is an authored directed relation from the source endpoint to the target endpoint.
- Relation ID
category_to_preadditive- Relation type
- Add data
add-data - Direction
- source → target
- Endpoint roles
- source: Builds toward; target: Built from
- Authored annotation
- add abelian hom-groups
Authored explanation
Give each hom-set an abelian-group structure and make composition bilinear.
How to interpret this relation type
Equip an existing carrier or structured object with additional chosen data, when such compatible data exists. Use a construction junction when several independently meaningful inputs must coexist on the same carrier or interact compatibly.
This is an authored directed relation from the source endpoint to the target endpoint.
- Relation ID
category_to_small_category- Relation type
- Impose axiom
impose-axiom - Direction
- source → target
- Endpoint roles
- source: Builds toward; target: Built from
- Authored annotation
- + set-sized objects and arrows
Authored explanation
Require the collections of objects and morphisms to be sets.
How to interpret this relation type
Keep the existing data and select the subclass satisfying an additional law, existence condition, finiteness condition, or other property.
This is an authored directed relation from the source endpoint to the target endpoint.
- Relation ID
category_to_thin- Relation type
- Impose axiom
impose-axiom - Direction
- source → target
- Endpoint roles
- source: Builds toward; target: Built from
- Authored annotation
- at most one arrow
Authored explanation
Require each hom-set to have at most one element.
How to interpret this relation type
Keep the existing data and select the subclass satisfying an additional law, existence condition, finiteness condition, or other property.