KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesIrredundant Bases and the Irredundant Basis TheoremEngineering · Engineering MathematicsLesson 74/883← PrevNext →
GuidePublished 12 Aug 2026Updated 13 Aug 20268 min readBy Kevin Jogin
On this page

Ask about this page

KEVOS AIIrredundant Bases and the Irredundant Basis Theorem

KEVOS knowledge first · trusted web sources when needed

Core Structure Theory

Irredundant Bases and the Irredundant Basis Theorem

Minimal generating sets that admit no proper generating subset, and the theorem constraining the possible sizes of such bases in an algebra with an algebraic closure operator.

Category Engineering / MathematicsSource II.4Pages 35-37Reading 2 minReviewed 2026-08-07

Learning objectives

  • Define irredundant basis and distinguish it from minimal generating set
  • State the irredundant basis theorem
  • Recognise when the theorem's conclusion is informative
On this page
  1. Irredundant bases
  2. The theorem
  3. When bases are well behaved
  4. A concrete failure

Irredundant bases

Definition — Irredundant basis

A subset X of an algebra A is an irredundant basis if Sg(X) = A and no proper subset of X generates A.

Equivalently, X generates and for each x ∈ X, the element x does not lie in Sg(X − {x}).

Irredundant is weaker than minimum-size

An irredundant basis need not have the smallest possible size. An algebra can have irredundant bases of several different cardinalities — a phenomenon impossible for vector spaces, where all bases have the same size, and the reason the theorem is needed at all.

The theorem

Irredundant basis theorem

Let C be an algebraic closure operator on a set A, and let IrB(A) denote the set of cardinalities of irredundant bases of A. If IrB(A) contains arbitrarily large finite numbers, then it contains all sufficiently large finite numbers — that is, the set of finite basis sizes has no arbitrarily large gaps.

Informally: irredundant basis sizes cannot be scattered arbitrarily. Once they become unbounded, they fill in a final segment of the natural numbers.

A specialised result

This section is one the source itself marks as omissible from the short course. It is not used in the main development; it is included because the question — how badly can generating sets behave? — is natural, and the answer is a genuine constraint rather than a triviality.

When bases are well behaved

Basis behaviour across settings
SettingAll irredundant bases the same size?
Vector space over a fieldYes — dimension is an invariant
Free module over a commutative ringYes — rank is an invariant
Free algebra in a varietyYes — the free generating set is determined
Matroid / pregeometryYes — this is essentially the definition
General groupNo
General algebraNo
The exchange property

Bases have constant size exactly when the closure operator satisfies the exchange property: if a ∈ C(X ∪ {b}) − C(X), then b ∈ C(X ∪ {a}). Closure operators with this property are exactly the matroids, and linear span is the motivating instance.

A concrete failure

Groups with bases of different sizes

The symmetric group S3 is generated irredundantly by two transpositions — a basis of size 2. It is also generated by a transposition together with a 3-cycle, again size 2. But many finite simple groups admit irredundant generating sets of several distinct sizes, and the phenomenon is common rather than exceptional.

The exchange property fails for group generation: knowing that a is in the subgroup generated by X and b tells one nothing about whether b lies in the subgroup generated by X and a.

The irredundant basis theorem is the residual regularity that survives this failure. It does not restore constancy, but it rules out pathological gaps in the spectrum of basis sizes.

Frequently asked questions

Is this theorem used later in the book?

No. The source flags §4 as omissible from the introductory course, and nothing in the later chapters depends on it. It is included for completeness of the treatment of generation.

What is the relationship to matroid theory?

Direct. Closure operators satisfying the exchange property are matroids, where all bases have equal size. The irredundant basis theorem describes what can be salvaged when exchange fails, so it sits just outside matroid theory.

Related pages

  • The Subalgebra Lattice Sub(A) is Algebraic
  • Congruences and the Substitution Property

Source. S. Burris and H. P. Sankappanavar, A Course in Universal Algebra, The Millennium Edition — a corrected re-typesetting of Springer-Verlag Graduate Texts in Mathematics 78 (1981). Section II.4, book pages 35-37.

This page is an original exposition prepared for the KEVOS® knowledge library. It restates and reorganises mathematical results; it is not a reproduction of the source text.

Handbook application: from concept to controlled practice

Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Irredundant Bases and the Irredundant Basis Theorem. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.

The operating aim is to turn a compact mathematical statement into a usable chain of definitions, claims, examples and checks. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.

Treat Irredundant Bases and the Irredundant Basis Theorem as a network of definitions and implications, not as a list of formulas. The working vocabulary on this page—bases, irredundant, theorem, generating, basis—should be made explicit before any proof or computation begins. Record the ambient set or structure, the permitted operations and the equality or equivalence relation in use. A compact theorem often changes meaning when the base field, finiteness condition, commutativity assumption or direction of an action changes.

For a proof, write the hypotheses as a checklist and mark the line at which each one is used. For a computation, state the representation of the input, the arithmetic model, the termination condition and the output invariant. For a classification problem, distinguish existence from uniqueness and distinguish an object from its representation. These separations prevent a correct local calculation from being mistaken for the general result.

A useful worked example should be small enough to inspect completely but rich enough to exercise the main mechanism. Compute the result in two ways where practical: symbolically and by substitution, structurally and numerically, or directly and through a normal form. Then include one near-miss example in which a hypothesis fails. The contrast explains why the theorem is shaped as it is and gives the reader a diagnostic pattern for later problems.

Verification is part of the mathematics. Check domains and codomains, substitute proposed solutions, test identity and zero cases, compare dimensions or cardinalities, and confirm that maps respect the required operations. In numerical work, report precision, conditioning and a residual rather than digits alone. In algorithmic work, separate mathematical correctness from implementation complexity and resource limits.

Step-by-step operating method

  1. Fix the setting. State the objects, ambient structure, notation and assumptions before manipulating symbols.
  2. Separate claims. Distinguish definitions, hypotheses, conclusions, equivalent conditions and consequences.
  3. Choose a method. Select proof, construction, calculation or algorithm according to the question actually asked.
  4. Work a small case. Use the smallest non-trivial example to expose the mechanism and test edge behaviour.
  5. Verify independently. Substitute back, check invariants, test boundary cases or use an alternative derivation.

Worked-example protocol

Illustrative method—not a source theorem. Start with a small admissible input and list the definitions it must satisfy. Carry out each transformation on a separate line, citing the property that permits it. Preserve exact values until approximation is necessary. At the end, verify the output against the original definition and one invariant such as dimension, degree, determinant, order, norm or residual. Then alter one hypothesis and observe which step ceases to be valid. This protocol creates a reusable example without inventing a theorem-specific numerical answer.

StageRecordQuality check
InputObjects, domain, notation, assumptionsEvery symbol is defined
MethodPermitted operation or cited result at each stepAll hypotheses hold
OutputExact result and representationCorrect type, domain and form
VerificationSubstitution, invariant or alternative derivationIndependent agreement
Boundary testZero, identity, degenerate or failed hypothesisScope is understood

Common failure modes and recovery actions

1. Watch for

Using a theorem without checking every hypothesis.

Recovery: Return to the governing definition or requirement and restate the decision in one sentence.

2. Watch for

Treating a suggestive example as a proof of the general case.

Recovery: Separate evidence from assumption, assign an owner and set a date for validation.

3. Watch for

Changing notation or conventions part-way through an argument.

Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.

4. Watch for

Hiding a division-by-zero, convergence, finiteness or commutativity assumption.

Recovery: Record the consequence, decision and rationale, then update the controlled baseline.

5. Watch for

Reporting a computed result without a residual, substitution or structural check.

Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.

Review checklist

  • Can every symbol be traced to a definition or prior result?
  • Which hypothesis does each major step use?
  • Does the method cover zero, identity, degenerate and boundary cases?
  • Can the conclusion be checked by a second representation or calculation?
  • Are mandatory requirements distinguished from recommendations and illustrative values?
  • Are sources, assumptions, units, dates and versions recorded closely enough to reproduce the decision?
  • Have safety, legal, ethical, stakeholder and operational consequences been considered at the appropriate level?
  • Is there a named owner and a trigger for review, escalation, change or retirement?

Questions for deeper application

What is the most important distinction a practitioner must preserve when applying Irredundant Bases and the Irredundant Basis Theorem?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

Which assumption about bases would change the result most if it proved false?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

What evidence would allow an independent reviewer to reproduce or challenge the conclusion?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

Which boundary, exception or failure case has not yet been tested?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

What must be handed over, monitored or reviewed after the immediate work is complete?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

Authoritative references and use notes

The sources below were selected as institutional or primary guidance for the broader practice. They support the handbook method; they do not imply that every statement or clause in a source applies to every project. Confirm the current edition, jurisdiction, contract and application before treating any requirement as mandatory.

  • MIT OpenCourseWare — Linear Algebra — Massachusetts Institute of Technology. Used for systems, vector spaces, determinants, eigenvalues and matrices. Accessed 2026-08-13.
  • MIT OpenCourseWare — Algebra I — Massachusetts Institute of Technology. Used for groups, vector spaces, linear transformations and linear groups. Accessed 2026-08-13.

Continue learning

Needs AssessmentGuide · Engineering MathematicsThe M5 and N5 Forbidden-Sublattice TheoremsGuide · Engineering MathematicsNEXT LESSON →Term Operations and Polynomial OperationsGuide · Engineering MathematicsApplied Universal Algebra: a SynthesisGuide · Engineering Mathematics
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®