Skip to content

Cadet branch

A genealogical branch descended from a dynasty's younger child or non-senior line, distinct from the senior line favored by the relevant succession and inheritance convention.

Version
v1 · 2026-09-08 · History
Domain-specific #
3572
Origin domain
genealogy dynastic history and succession
Subdomain
genealogy dynastic history and succession

Core Idea

Cadet branches can acquire appanages, titles or new realms and can become senior when older lines fail; male-line wording is historical and varies with gender, legitimacy and house-law rules. A succession rule ranks siblings or lines, the senior heir continues the principal house, and a younger descendant founds a collateral lineage whose identity persists through genealogy, title and political recognition. 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.

Scope of Application

Cadet branch belongs to genealogy dynastic history and succession and is useful where the analyst can specify the typed genealogy dynastic history and succession carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, then evaluate the dynasty and jurisdiction, period and house law, common ancestor, senior and junior child, gender and legitimacy rules, line of descent, primogeniture or partition practice, appanage and titles, naming, extinction and succession back to seniority are explicit.

Clarity

The abstraction clarifies a crowded vocabulary by making the dynasty and jurisdiction, period and house law, common ancestor, senior and junior child, gender and legitimacy rules, line of descent, primogeniture or partition practice, appanage and titles, naming, extinction and succession back to seniority are explicit the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test.

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 Cadet branch. Cadet branch 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: the typed genealogy dynastic history and succession carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets. Reject examples whose alleged carrier belongs to a different problem. 2.

Knowledge Transfer

Knowledge transfers strongly among subfields of genealogy dynastic history and succession because they reuse the typed genealogy dynastic history and succession carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, A succession rule ranks siblings or lines, the senior heir continues the principal house, and a younger descendant founds a collateral lineage whose identity persists through genealogy, title and political recognition., and type the carrier, state every parameter and convention in the definition, test that the dynasty and jurisdiction, period and house law, common ancestor, senior and junior child, gender and legitimacy rules, line of descent, primogeniture or partition practice, appanage and titles, naming, extinction and succession back to seniority are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions

Local relationship map for Cadet branchParents 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.Cadet branchDOMAINPrime abstraction: Branching and Merging — is a kind ofBranchingand MergingPRIME

Current abstraction Cadet branch Domain-specific

Parents (1) — more general patterns this builds on

  • Cadet branch is a kind of Branching and Merging Prime

    The proposed strict upward parent is prime:branching_and_merging.

Hierarchy paths (2) — routes to 2 parentless roots

Neighborhood in Abstraction Space

Cadet branch sits in a moderately populated region (55th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Inheritance, Lineage & Development (17 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08