Skip to content

Root (chord)

The pitch class that names and structurally organizes a chord as the origin of its interval stack, regardless of which chord tone sounds lowest.

Version
v1 · 2026-09-08 · History
Domain-specific #
6542
Origin domain
music theory
Subdomain
music theory

Core Idea

Root identification depends on harmonic theory and can be ambiguous for symmetric, added-note or nontertian sonorities; inversion changes bass but not root under standard tonal analysis. Chord tones are interpreted as intervals above an organizing pitch, and harmonic function, spelling and voice leading support that pitch as the generative reference. 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

Root (chord) belongs to music theory and is useful where the analyst can specify the typed music theory carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, then evaluate the tuning and notation, chord tones and spellings, bass and inversion, proposed root, interval-generation rule, harmonic context and function, competing analyses and ambiguity are explicit. The scope is broad within that domain but bounded by the need for the tuning and notation, chord tones and spellings, bass and inversion, proposed root, interval-generation rule, harmonic context and function, competing analyses and ambiguity are explicit. 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 the tuning and notation, chord tones and spellings, bass and inversion, proposed root, interval-generation rule, harmonic context and function, competing analyses and ambiguity 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. A bare label is insufficient because the name Root (chord) 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 Root (chord). Root (chord) 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 music theory carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets. Reject examples whose alleged carrier belongs to a different problem. 2. Lock the constitutive rule. Express the tuning and notation, chord tones and spellings, bass and inversion, proposed root, interval-generation rule, harmonic context and function, competing analyses and ambiguity are explicit independently of one notation or implementation.

Knowledge Transfer

Knowledge transfers strongly among subfields of music theory because they reuse the typed music theory carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, Chord tones are interpreted as intervals above an organizing pitch, and harmonic function, spelling and voice leading support that pitch as the generative reference., and type the carrier, state every parameter and convention in the definition, test that the tuning and notation, chord tones and spellings, bass and inversion, proposed root, interval-generation rule, harmonic context and function, competing analyses and ambiguity are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions

Local relationship map for Root (chord)Parents 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.Root (chord)DOMAINPrime abstraction: Reference-Point Dependence — is a kind ofReference-PointDependencePRIME

Current abstraction Root (chord) Domain-specific

Parents (1) — more general patterns this builds on

  • Root (chord) is a kind of Reference-Point Dependence Prime

    The proposed strict upward parent is prime:reference_point_dependence.

Hierarchy path (1) — routes to 1 parentless root

Neighborhood in Abstraction Space

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

Family — Harmony, Tuning & Musical Form (24 abstractions)

Nearest neighbors

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