Skip to content

Inheritance

Version
v1 · 2026-08-24 · History
Prime #
919
Domain group
Applied Sciences & Engineering
Origin domain
Computer Science & Software Engineering
Subdomain
Type Systems Taxonomy → Computer Science & Software Engineering

Core Idea

A derived entity receives structure, behaviour, or claims from a parent along a lineage relation by default, while being permitted to add, override, or specialize some portion of what it received. The state of any derived system is parent contribution plus override delta.

How would you explain it like I'm…

Passed Down From Parents

A puppy gets a lot from its mom and dad dog — its floppy ears, its bark, its color — just by being their baby. But it isn't an exact copy; it can have its own special spots they didn't have. So it keeps most of what its parents passed down and changes a little to be its own self.

Get It, Then Tweak It

Inheritance is when a new thing gets structure, behavior, or stuff from a parent thing because of a family-like link, but is allowed to add to or change parts of what it got. There are three pieces. First, a lineage — a parent-to-child link that points one direction (a kid and its parents, an heir and the person who left them money). Second, default carrying-over — by default the child gets the parent's stuff without redoing it from scratch. Third, selective override — the child can change or add to some parts while still clearly being 'of the parent' in the parts it didn't change. That last piece is what makes inheritance creative instead of plain copying.

Transmit With Modification

Inheritance is the structural pattern of a derived entity receiving structure, behavior, or claims from a parent entity by virtue of a *lineage* relation, while being permitted — often required — to add, modify, or override some portion of what it received. Three load-bearing commitments: lineage (a directed, asymmetric parent-to-derivative relation — child class and superclass, heir and decedent, subspecies and species, statute and constitutional predecessor); default carrying-over (by default the parent's properties apply without re-derivation — a child class gets its parent's methods, a beneficiary gets the estate, an organism gets its parents' alleles); and selective override and extension (the derivative can specialize or augment parts while remaining recognizably 'of the parent' along the un-overridden parts — and this override is what makes inheritance generative rather than mere copying). A frequent fourth feature is substitutability: a derived entity can stand where the parent was expected (Liskov substitution, a subspecies counting as the species in a census). The move it supplies is *transmit-with-modification along a lineage*: continue what came before, specialize where context requires — distinct from mere copying (the parent persists), composition (sub-parts independently chosen), and pure assignment (no lineage).

 

Inheritance is the structural pattern of a derived entity receiving structure, behavior, or claims from a parent entity by virtue of a lineage relation, while being permitted — often required — to add, modify, or override some portion of what it received. The three load-bearing commitments are these. Lineage: a directed, asymmetric relation between a parent and a derivative — child class and superclass, descendant and ancestor, heir and decedent, subspecies and species, statute and constitutional predecessor. Default carrying-over: by default the properties of the parent apply to the derivative without re-derivation — a child class gets its parent's methods, a beneficiary gets the testator's estate, an organism gets its parents' alleles, a junior court gets binding precedent. Selective override and extension: the derivative can specialize, override, or augment parts of what was inherited while remaining recognizably 'of the parent' along the un-overridden parts, and this override is what makes inheritance generative rather than mere copying. A fourth, frequently-present feature is substitutability: a derived entity can stand where the parent was expected — Liskov substitution in software, a subspecies counting as the species in a census, a junior court speaking with the authority of its lineage. The substrate-independent move the prime supplies is transmit-with-modification along a lineage relation: the default is 'continue what came before,' the override is 'specialize where the context requires,' and the state of the system at any moment is the cumulative result of inheritance plus override across the lineage. The pattern is structurally distinct from mere copying (the parent persists), composition (sub-parts independently chosen), and pure assignment (no lineage relation). The term carries family-and-property-law connotation, but the lineage-default-override skeleton beneath it is substrate-neutral.

Tensions in Practice

Broad Use

  • Object-oriented programming: a subclass inherits its superclass's methods and overrides selected ones, constrained by Liskov substitutability.
  • Biology: Mendelian, polygenic, epigenetic, and cultural inheritance transmit traits down a lineage.
  • Law: property passes by will or intestacy, titles by succession, and binding precedent down a court hierarchy.
  • Taxonomy: Linnaean and cladistic classification carry traits down a phylogenetic tree as IS-A relations.
  • Religion: apostolic succession, rabbinic ordination chains, and isnād chains in hadith transmission.
  • Real estate: water rights, easements, and covenants inherited with land and binding successive owners.

Clarity

It makes visible which parts of a system are still the parent and which are specialized child, exposing the defaults a derivative "got for free" and never questioned.

Manages Complexity

Instead of restating every child fully, you describe the parent once and only the delta — the reason taxonomies and class libraries are compact, paid for with standing downward coupling.

Abstract Reasoning

It supports substrate-neutral questions: what is inherited by default, what is overridden and why, is the override substitutable, and how brittle is a deep or multi-parent lineage.

Knowledge Transfer

  • Software → organizations: "composition over inheritance" — replace brittle lineage-by-default with explicitly assembled parts — recurs in modular org design.
  • Software ↔ evolution ↔ law: the diamond problem, homologous-vs-analogous traits, and multiple-doctrine reconciliation are one shape solved by C3 linearization, cladistic parsimony, and lex specialis.
  • Law ↔ genetics ↔ software: lineage repair — overruling a precedent, correcting a deeply-inherited allele, refactoring a base class — is recurringly hard because so much inherited from the defective parent.

Example

A tax code inheriting concepts from common law and Roman law, adding a "qualified business income" deduction as a delta while inheriting the rest, has the same structure as Mammal.feed_young inherited by Primate and overridden by Human.

Relationships to Other Abstractions

Local relationship map for InheritanceParents 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.InheritancePRIMEPrime abstraction: Dependency — is a kind of, typicalDependencyPRIMEDomain-specific abstraction: Yo-yo Problem — presupposesYo-yo ProblemDOMAINDomain-specific abstraction: Copying Mechanism — is a kind ofCopyingMechanismDOMAINDomain-specific abstraction: Line of hereditary succession — is a kind ofLine of heredit…DOMAINDomain-specific abstraction: Lineage (genetic) — is a kind ofLineage(genetic)DOMAINDomain-specific abstraction: Matrilineal Succession — is a kind ofMatrilinealSuccessionDOMAINDomain-specific abstraction: Mitosis — is a kind ofMitosisDOMAINDomain-specific abstraction: Most recent common ancestor — is a kind ofMost recentcommon ancestorDOMAINDomain-specific abstraction: Saisine — is a kind ofSaisineDOMAINDomain-specific abstraction: Sequence homology — is a kind ofSequencehomologyDOMAINDomain-specific abstraction: Shelter Rule — is a kind ofShelter RuleDOMAINDomain-specific abstraction: Transfer learning — is a kind ofTransferlearningDOMAINDomain-specific abstraction: Virtual class — is a kind ofVirtual classDOMAIN

Current abstraction Inheritance Prime

Parents (1) — outgoing typed relations

  • Inheritance is a kind of, typical Dependency Prime

    Inheritance is the specific dependency of a derivative on a parent ALONG A LINEAGE, with default carry-over and substitutability — a specialization of bare dependency ('not dependency in general').

Children (12) — abstractions linked here by typed relations

  • Copying Mechanism Domain-specific is a kind of Inheritance

    At each step, the new vertex is a derivative of a sampled prototype for purposes of adjacency: neighborhood structure carries over by default or probability, with selective deletion, addition, or rewiring.

  • Line of hereditary succession Domain-specific is a kind of Inheritance

    Line of Hereditary Succession instantiates Inheritance because it governs prospective transfer of entitlement through descent while adding an ordered candidate line.

  • Lineage (genetic) Domain-specific is a kind of Inheritance

    A genetic lineage literally transmits structure from ancestors to descendants while mutation, segregation, and recombination provide selective modification; the evidential and population-genetic apparatus supplies the specialization.

  • Matrilineal Succession Domain-specific is a kind of Inheritance

    Matrilineal Succession strictly specializes Inheritance.

  • Mitosis Domain-specific is a kind of Inheritance

    Mitosis literally presupposes transmission of replicated chromosomal structure down a cell lineage; it adds a eukaryotic segregation mechanism rather than being generic Inheritance.

Hierarchy path (1) — routes to 1 parentless root

Not to Be Confused With

  • Inheritance is not Composition because inheritance derives an entity from a parent along a lineage (is-a-kind-of, default carry-over) whereas composition assembles a whole from independently chosen sub-parts (has-a).
  • Inheritance is not Hierarchy because inheritance is a transmission that carries structure downward with override whereas a hierarchy is a static ranking of levels; the hierarchy is the shape, the inheritance is the carrying-over.
  • Inheritance is not Specialization because specialization is only the override component whereas inheritance also carries the un-overridden defaults forward by default and supports substitutability.