Degree of a field extension¶

The vector-space dimension of an extension field over its base field.

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

Core Idea¶

For a field extension E over F, the degree [E:F] is the cardinal dimension of E as an F-vector space; finite towers satisfy multiplication of degrees.^[1] Choosing an F-basis expresses every extension element uniquely in base-field coordinates, and composing bases through a tower multiplies the coordinate dimensions. 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 field theory. It is the domain-specific identity determined by the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree. That residual remains recognizable when examples, notation, scale, or implementation change, but it disappears if the carrier is mistyped, the condition that the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree fails, a neighboring object is substituted, or notation and topical resemblance replace the constitutive test. This gives the entry an operational identity rather than merely a historical label.

A useful analysis keeps three layers separate. The constitutive layer says what must be true: the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree. The evidential layer asks what observation or proof warrants the claim: type the carrier, state every parameter and convention in the definition, test that the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases. The use layer asks what reasoning becomes available once the identity is established: recognizing and comparing instances of Degree of a field extension, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions. Conflating the layers is the most common source of scope inflation.

How would you explain it like I'm…

How Many Building Blocks

Imagine you have a big box of ordinary fractions, and you add one new number that fractions can't make, like the number that times itself makes 2. Now every number in your bigger box can be built from just two ingredients: a fraction, plus a fraction times the new number. The degree counts how many ingredients you need, so here it is 2.

Building-Block Count

Start with the fractions. Add a new number, the square root of 2, and allow adding, subtracting, multiplying and dividing. Every number you can now make can be written as a + b times the square root of 2, where a and b are fractions, and in only one way. You need two building blocks, 1 and the square root of 2, so the degree of this bigger number system over the fractions is 2. If you build up in two steps, the degrees multiply: a step of 2 followed by a step of 3 gives a total degree of 6.

Dimension Over the Base Field

If a field E contains a smaller field F, then E can be treated as a vector space over F: you can add elements of E and scale them by elements of F. The degree [E:F] is the dimension of that vector space, the size of a basis. For instance, every element of ℚ(√2) is uniquely a + b√2 with a, b rational, so [ℚ(√2):ℚ] = 2. Degrees multiply through towers: if F ⊆ K ⊆ E, then [E:F] = [E:K]·[K:F]. The degree always depends on which base field you fix, and it is different from transcendence degree, which counts algebraically independent elements rather than vector-space dimension.

For a field extension E/F, the degree [E:F] is the dimension of E regarded as a vector space over F, where the base-field inclusion F ⊆ E is fixed. It may be finite or an infinite cardinal. Choosing an F-basis of E lets every element of E be written uniquely as an F-linear combination of basis elements, so elements acquire base-field coordinates. For a finite tower F ⊆ K ⊆ E, the tower law [E:F] = [E:K][K:F] holds: if {kᵢ} is a basis of K over F and {eⱼ} a basis of E over K, then the products {kᵢeⱼ} form a basis of E over F, so the dimensions multiply. For a simple algebraic extension F(α)/F, the degree equals the degree of α's minimal polynomial. The degree depends on the chosen base field, and it must be distinguished from transcendence degree, which measures the size of a transcendence basis, not linear dimension.

Structural Signature¶

Carrier: the typed field theory carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets
Inputs or antecedent state: the exact field theory carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate Degree of a field extension
Constitutive operation: Choosing an F-basis expresses every extension element uniquely in base-field coordinates, and composing bases through a tower multiplies the coordinate dimensions.
Invariant: the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree
Recognition test: type the carrier, state every parameter and convention in the definition, test that the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases
Output or consequence: recognizing and comparing instances of Degree of a field extension, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions
Failure boundary: the carrier is mistyped, the condition that the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree fails, a neighboring object is substituted, or notation and topical resemblance replace the constitutive test

What It Is Not¶

It is not the whole field of field theory. The field contains many questions and methods that do not instantiate Degree of a field extension.
It is not its most familiar example. A canonical instance directly demonstrates that the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree. exhibits the structure, but the example is evidence for the abstraction rather than its definition.
It is not the neighboring catalog concept Transcendence degree. Field-extension degree counts vector-space basis size and may be infinite even at finite transcendence degree; transcendence degree counts an algebraically independent basis.
It is not a claim that every boundary case has one uncontested classification. a generalized or degenerate case may change existence, uniqueness, measurement, or naming conventions, so the exact definition of Degree of a field extension must control the decision
It is not an unrestricted metaphor for any process that seems similar. Outside field theory, the vocabulary and validity conditions do not transfer literally.

Scope of Application¶

Degree of a field extension belongs to field theory and is useful where the analyst can specify the typed field theory carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, then evaluate the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree. The scope is broad within that domain but bounded by the need for the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree. The entry records a descriptive analytical identity; practical use requires the governing domain's evidence, standards, and safety obligations.^[2]

Definition and recognition. Determine whether a proposed instance satisfies the constitutive conditions rather than merely sharing terminology.
Construction or evolution. Track how the exact field theory carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate Degree of a field extension are converted, constrained, or organized by Choosing an F-basis expresses every extension element uniquely in base-field coordinates, and composing bases through a tower multiplies the coordinate dimensions..
Comparison. Compare instances using carrier, parameters, convention, domain, scale, boundary conditions, evidence, exact versus approximate form, and limiting behavior, without treating convenience measures as the definition.
Boundary analysis. Diagnose cases where a generalized or degenerate case may change existence, uniqueness, measurement, or naming conventions, so the exact definition of Degree of a field extension must control the decision and state which convention or theorem controls the decision.
Downstream reasoning. Use the established identity to support recognizing and comparing instances of Degree of a field extension, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions while preserving the assumptions under which the inference is valid.

Clarity¶

The abstraction clarifies a crowded vocabulary by making the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree 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 Degree of a field extension can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated. The disciplined statement is: given the exact field theory carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate Degree of a field extension, the structure counts as Degree of a field extension exactly when the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree.

This format also separates identity from measurement. Empirical, computational, or documentary proxies support recognition only under declared validity and uncertainty assumptions; formal cases require proof rather than measurement. Measurements can be noisy, implementations can approximate, and proofs can use equivalent characterizations; none of those facts licenses changing the object being measured. When reports disagree, first check scope and convention, then data or proof, and only then interpret the disagreement as substantive.

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 Degree of a field extension. Degree of a field extension 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.

The compression has a price. A single label can hide canonical, generalized, restricted, approximate, computational, empirical, and historically variant formulations of Degree of a field extension. Good use therefore carries a small declaration of assumptions alongside the name. The abstraction manages complexity when it reduces the state space of the question while keeping the failure boundary visible; it mismanages complexity when the label substitutes for that boundary analysis.

Abstract Reasoning¶

Identify the carrier. State what the elements, states, objects, or observations are: the typed field theory carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets. Reject examples whose alleged carrier belongs to a different problem.
Lock the constitutive rule. Express the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree independently of one notation or implementation. This step prevents the canonical example from becoming the definition.
Derive consequences. From the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree, infer recognizing and comparing instances of Degree of a field extension, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions. Record each assumption used so that a later change of setting does not silently preserve an invalid conclusion.
Test adversarial cases. Examine a generalized or degenerate case may change existence, uniqueness, measurement, or naming conventions, so the exact definition of Degree of a field extension must control the decision and an object that resembles Degree of a field extension in purpose or vocabulary but does not satisfy its invariant is outside the class. A robust identity explains why the first is convention-sensitive and why the second is outside the class.
Compare and refine. Use carrier, parameters, convention, domain, scale, boundary conditions, evidence, exact versus approximate form, and limiting behavior to compare legitimate instances, and refine the model when discrepancies reflect hidden variation rather than failure of the abstraction itself.

Knowledge Transfer¶

Knowledge transfers strongly among subfields of field theory because they reuse the typed field theory carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, Choosing an F-basis expresses every extension element uniquely in base-field coordinates, and composing bases through a tower multiplies the coordinate dimensions., and type the carrier, state every parameter and convention in the definition, test that the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases. A theorem, diagnostic, or modeling warning can travel when those roles remain literal. For example, the distinction between constitutive identity and a convenient observable transfers from A canonical instance directly demonstrates that the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree. to An applied instance preserves the same invariant under a changed notation, scale, implementation, or empirical setting..^[3]

Transfer outside the home domain is weaker. The skeletal pattern—type the carrier, apply the defining mechanism of Degree of a field extension, preserve its invariant, and derive only consequences licensed by the stated boundary—may suggest an analogy, but the domain-specific mechanisms, admissible evidence, and consequences do not come along automatically. The safe transfer procedure maps each role explicitly, checks the invariant again, and refuses the name when only a superficial resemblance remains.

Examples¶

Canonical¶

A canonical instance directly demonstrates that the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree. The example exposes the carrier and directly tests that the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree; changing incidental notation preserves the identity, while removing that condition destroys it. This example is canonical because every role can be inspected: the carrier is the typed field theory carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets; the operative rule is Choosing an F-basis expresses every extension element uniquely in base-field coordinates, and composing bases through a tower multiplies the coordinate dimensions.; the invariant is the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree; and the result supports recognizing and comparing instances of Degree of a field extension, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions.^[1] Changing incidental notation or scale leaves the structure intact, while removing the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree destroys the classification.

Mapped back: the typed field theory carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets → Choosing an F-basis expresses every extension element uniquely in base-field coordinates, and composing bases through a tower multiplies the coordinate dimensions. → the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree → recognizing and comparing instances of Degree of a field extension, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions

Applied / In Practice¶

An applied instance preserves the same invariant under a changed notation, scale, implementation, or empirical setting. The applied case qualifies only because the same invariant and boundary test remain literal under changed parameters or implementation. The applied case is not licensed merely by vocabulary. It qualifies because the same recognition test—type the carrier, state every parameter and convention in the definition, test that the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases—can be run and because the same failure boundary—the carrier is mistyped, the condition that the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree fails, a neighboring object is substituted, or notation and topical resemblance replace the constitutive test—remains meaningful.^[2] The case also shows why practical outputs should report assumptions, resolution, and uncertainty instead of a naked label.

Mapped back: declared instance → recognition test → boundary check → qualified use

Structural Tensions¶

T1: Axiomatic identity vs. operational recognition. The defining conditions may be exact while empirical or computational recognition is approximate. Neither pole can be removed without changing the analytical task. Diagnostic: Can the reviewer state both the exact condition and the evidence used to infer it?
T2: Local roles vs. global consequence. The mechanism is enacted through local relations, but the abstraction is usually valued for a global classification or prediction. Neither pole can be removed without changing the analytical task. Diagnostic: Does the claimed global result actually follow from the declared local conditions?
T3: Ideal form vs. finite representation. Theory states a clean invariant while data structures, measurements, or proofs expose only finite representations. Neither pole can be removed without changing the analytical task. Diagnostic: Would increasing resolution converge toward the same classification?
T4: Canonical convention vs. legitimate variants. A standard formulation supports communication, while variants may preserve the same core under changed assumptions. Neither pole can be removed without changing the analytical task. Diagnostic: Which role is invariant across variants, and which convention-specific conclusion changes?
T5: Compression vs. hidden assumptions. The name compresses a complex argument but can conceal prerequisites. Neither pole can be removed without changing the analytical task. Diagnostic: Can each downstream inference be traced to an explicit assumption?
T6: Autonomous residual vs. reduction to catalog neighbors. The candidate uses broader structures but adds an identity-bearing residual. Neither pole can be removed without changing the analytical task. Diagnostic: After subtracting the proposed parent and named neighbors, does the constitutive residual still support independent diagnostics?

Structural–Framed Character¶

The entry is structurally mixed but domain-framed. Its portable skeleton is type the carrier, apply the defining mechanism of Degree of a field extension, preserve its invariant, and derive only consequences licensed by the stated boundary. Its identity-bearing terms—Degree of a field extension, carrier, parameter, invariant, boundary, evidence, model, transformation, and application—derive their meaning from field theory and cannot be replaced by generic systems language without losing the tests that distinguish valid from invalid instances.

This mixed character explains why the abstraction is reusable inside the domain yet does not meet the Prime bar. The structure organizes reasoning, but its claims still depend on domain-specific objects, evidence, and intervention semantics.

Structural Core vs. Domain Accent¶

The structural core consists of a carrier, Choosing an F-basis expresses every extension element uniquely in base-field coordinates, and composing bases through a tower multiplies the coordinate dimensions., a recognition invariant, and a consequence. That skeleton may resemble patterns elsewhere, especially type the carrier, apply the defining mechanism of Degree of a field extension, preserve its invariant, and derive only consequences licensed by the stated boundary. The domain accent is not decorative: Degree of a field extension, carrier, parameter, invariant, boundary, evidence, model, transformation, and application determine what counts as an admissible carrier, a valid transition, and successful evidence.

The abstraction therefore remains domain-specific. A cross-domain reuse that preserves only words such as 'balance,' 'cut,' 'sequence,' 'loss,' or 'simulation' is metaphor. Literal transfer requires the original role structure and diagnostics, which in this case remain anchored in field theory.

This entry is a kind of Dimension.

It remains its own entry because the base-field inclusion is fixed and the degree is the dimension of the extension as a vector space over that base, distinct from transcendence degree.

Relationships to Other Abstractions¶

Current abstraction Degree of a field extension Domain-specific

Parents (1) — outgoing typed relations

Degree of a field extension is a kind of Dimension Prime

What makes it its own entry: the domain-specific identity determined by the base-field inclusion is fixed and degree is the dimension of the extension as a vector space over that base, distinguished from transcendence degree.

Hierarchy path (1) — routes to 1 parentless root

Degree of a field extension → is a kind of Dimension

Neighborhood in Abstraction Space¶

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

Family — Field Theory & Polynomial Structures (26 abstractions)

Nearest neighbors

Rupture field — 0.93
Minimal polynomial (field theory) — 0.91
Separable polynomial — 0.91
Algebraically closed field — 0.91
Algebraic number field — 0.90

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

Not to Be Confused With¶

Transcendence degree. Field-extension degree counts vector-space basis size and may be infinite even at finite transcendence degree; transcendence degree counts an algebraically independent basis.
One canonical example. An instance demonstrates the structure but does not define the whole abstraction.
Measurement or implementation of Degree of a field extension. A proxy or realization is evidence for the abstraction, not the abstraction itself.
Generalized Degree of a field extension. An extension qualifies only when its changed axioms and retained invariant are stated.

References¶

[1] Jacobson, N, 'Basic Algebra I', W. H. Freeman and Company, 1985.not authoritative registry ↩a ↩b

[2] Jacobson, N, 'Basic Algebra II', W. H. Freeman and Company, 1989. openlibrary.orgnot authoritative registry ↩a ↩b

[3] Serge Lang, Algebra, revised 3^rd edition, Springer, 2002. registry ↩