Skip to content

Injective object

A categorical object into which every morphism defined on a subobject extends across the containing monomorphism.

Version
v2 · 2026-09-19 · History
Domain-specific #
5043
Domain group
Formal Sciences
Origin domain
Mathematics
Subdomain
Category Theory → Mathematics

Core Idea

An object Q is injective when every map from the domain of a monomorphism into Q factors through that monomorphism by an extending map from its codomain. The right lifting property against all monomorphisms makes Q absorb compatible maps from subobjects without obstruction. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

The load-bearing residual is not the broad topic of category theory. It is Injectivity is relative to the ambient category or selected class of monomorphisms and does not mean an injective underlying function..

How would you explain it like I'm…

The Always-Finish Crayon Box

Imagine you started coloring just one part of a big picture, using colors from a special crayon box. With this special box, you can always finish coloring the whole picture so that the part you already did stays exactly the same. That special crayon box is like an injective object.

The Always-Extendable Object

In math, sometimes a small thing sits neatly inside a bigger thing. Suppose you have a way of sending the small thing into some object Q. Q is called injective if you can always stretch that sending-rule to cover the whole bigger thing, while keeping it the same on the small part. Q never blocks you from extending. The word 'injective' here doesn't mean what it means for functions that never send two inputs to the same output; it is about this extending power.

Extension Along Monomorphisms

In a category, a monomorphism is the abstract version of 'A sits inside B as a sub-part'. An object Q is injective if, for every monomorphism m: A → B and every map f: A → Q, there is at least one map g: B → Q with g∘m = f. In other words, the triangle commutes. The extension need not be unique; it only has to exist. Watch out for a common confusion: this is not about Q being an 'injective function'. Being injective depends on which category you are in and which monomorphisms you test against.

 

An object Q in a category C is injective if, for every monomorphism m: A → B and every morphism f: A → Q, there exists g: B → Q with g∘m = f. Equivalently, the map Q → terminal object has the right lifting property against all monomorphisms. Informally, Q absorbs maps from subobjects with no obstruction to extending them. Only existence is required, not uniqueness. The notion is relative to the ambient category, or to a chosen class of monomorphisms. Changing the category can change which objects are injective, and the term has nothing to do with Q's underlying function being injective. To verify the property, fix the category, quantify over all monomorphisms and all maps into Q, and exhibit an extension in each case. Counterexamples arise where some extension fails.

Scope of Application

Injective object belongs to category theory and is useful where the analyst can specify a category, candidate object Q, every monomorphism X→Y, morphism X→Q, an extension Y→Q, and commutative triangle, then evaluate for every monomorphism and every map into Q, at least one extension exists making the triangle commute. The scope is broad within that domain but bounded by the need for for every monomorphism and every map into Q, at least one extension exists making the triangle commute. The entry records a descriptive analytical identity; practical use requires the governing domain's evidence, standards, and safety obligations.

Clarity

The abstraction clarifies a crowded vocabulary by making for every monomorphism and every map into Q, at least one extension exists making the triangle commute the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name Injective object can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated.

Manages Complexity

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Injective object. Injective object compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning

  1. Identify the carrier. State what the elements, states, objects, or observations are: a category, candidate object Q, every monomorphism X→Y, morphism X→Q, an extension Y→Q, and commutative triangle. Reject examples whose alleged carrier belongs to a different problem.
  2. Lock the constitutive rule. Express for every monomorphism and every map into Q, at least one extension exists making the triangle commute independently of one notation or implementation.

Knowledge Transfer

Knowledge transfers strongly among subfields of category theory because they reuse a category, candidate object Q, every monomorphism X→Y, morphism X→Q, an extension Y→Q, and commutative triangle, The right lifting property against all monomorphisms makes Q absorb compatible maps from subobjects without obstruction., and type the carrier, state every parameter and convention in the definition, test that for every monomorphism and every map into Q, at least one extension exists making the triangle commute, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions

Local relationship map for Injective objectParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Injective objectDOMAINPrime abstraction: Function (Mapping) — is a kind ofFunction(Mapping)PRIME

Current abstraction Injective object Domain-specific

Parents (1) — outgoing typed relations

  • Injective object is a kind of Function (Mapping) Prime

    What makes it its own entry: Injectivity is relative to the ambient category or selected class of monomorphisms and does not mean an injective underlying function.

Hierarchy path (1) — routes to 1 parentless root

Neighborhood in Abstraction Space

Injective object sits in a crowded region of the domain-specific corpus (5th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Categorical Constructions & Dualities (33 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-25