KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesSemigroups, Monoids and Quasigroups as AlgebrasEngineering · Engineering MathematicsLesson 28/883← PrevNext →
GuidePublished 12 Aug 2026Updated 13 Aug 20268 min readBy Kevin Jogin
On this page

Ask about this page

KEVOS AISemigroups, Monoids and Quasigroups as Algebras

KEVOS knowledge first · trusted web sources when needed

Core Structure Theory

Semigroups, Monoids and Quasigroups as Algebras

The one-operation structures and the divisibility structures, presented as algebras. Quasigroups in particular require a careful choice of type, and that choice illustrates a general principle.

Category Engineering / MathematicsSource II.1Pages 26-30Reading 2 minReviewed 2026-08-07

Learning objectives

  • Present semigroups and monoids as algebras and identify the varieties
  • Explain why quasigroups need three binary operations rather than one
  • Connect quasigroups to Latin squares
On this page
  1. Semigroups and monoids
  2. Quasigroups: the type problem
  3. Loops and the connection to Latin squares
  4. Why the type choice is a general lesson

Semigroups and monoids

Definition — Semigroup

An algebra ⟨S, ·⟩ of type ⟨2⟩ in which multiplication is associative.

Adding a nullary operation for the identity gives a monoid, of type ⟨2, 0⟩. Both classes are varieties.

Monoid is not the same as 'semigroup with identity'

A semigroup may happen to possess an identity element without that element being part of its type. The distinction matters for subalgebras: a subsemigroup of a monoid need not contain the identity, whereas a submonoid must. Changing the type changes the subalgebra lattice.

Commutative semigroups, bands (idempotent semigroups) and semilattices (commutative bands) are all subvarieties obtained by adding identities.

Quasigroups: the type problem

Definition — Quasigroup (first attempt)

A set with a binary operation such that for all a, b the equations a · x = b and y · a = b have unique solutions.

This definition is not equational — it asserts existence and uniqueness of solutions rather than stating identities. With this type, quasigroups are not a variety: a subalgebra of a quasigroup under multiplication alone need not be a quasigroup.

The repair: three operations

Introduce the solutions as operations. A quasigroup is an algebra ⟨Q, ·, /, \⟩ of type ⟨2, 2, 2⟩ satisfying:

  • x \ (x · y) ≈ y  and  x · (x \ y) ≈ y
  • (y · x) / x ≈ y  and  (y / x) · x ≈ y

With this type the class of quasigroups is a variety. This is a recurring move in the subject: an existential condition is converted into an operational one by naming the witness, which brings the class inside the equational framework.

Loops and the connection to Latin squares

Definition — Loop

A quasigroup with a two-sided identity element, included in the type as a nullary operation.

Groups are exactly the associative loops. The chain of specialisation is:

  • Quasigroup — unique solvability
    • Loop — plus identity
      • Group — plus associativity
        • Abelian group — plus commutativity
The combinatorial identity

The multiplication table of a finite quasigroup is precisely a Latin square: an n × n array in which every symbol occurs exactly once in each row and each column. Unique solvability of a · x = b is exactly the row condition; the column condition comes from the other equation.

This identification is what allows the refutation of Euler's conjecture on orthogonal Latin squares to be carried out algebraically, which is the subject of Chapter III §3.

Why the type choice is a general lesson

Three examples of the same phenomenon have now appeared:

Adding operations to obtain a variety
StructureNaive typeRepaired typeGained
Group⟨2⟩⟨2, 1, 0⟩Closure under subalgebras
Monoid⟨2⟩⟨2, 0⟩Identity preserved by subalgebras and homomorphisms
Quasigroup⟨2⟩⟨2, 2, 2⟩Equational definability
The general principle

If a class is closed under H, S and P but its natural axioms are not identities, the remedy is usually to enlarge the type by naming witnesses. If the class is not closed under all three, no enlargement of the type will make it a variety — the obstruction is structural.

Frequently asked questions

Are quasigroups congruence-permutable?

Yes. The term p(x,y,z) = (x / (y \ y)) · (y \ z) can be used to build a Mal'cev term, so quasigroups — and hence groups and loops — are congruence-permutable.

Is every Latin square the table of a group?

No, far from it. Every group of order n gives a Latin square, but the number of Latin squares of order n grows far faster than the number of groups. Most Latin squares correspond to quasigroups that are not associative.

Related pages

  • A Catalogue of Algebras: Groups, Rings, Lattices
  • Modules and R-Modules as Algebras
  • Quasigroups, Loops and Latin Squares

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.1, book pages 26-30.

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 Semigroups, Monoids and Quasigroups as Algebras. 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 Semigroups, Monoids and Quasigroups as Algebras as a network of definitions and implications, not as a list of formulas. The working vocabulary on this page—quasigroups, choice, type, semigroups, monoids—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 Semigroups, Monoids and Quasigroups as Algebras?

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 quasigroups 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 — Algebra I — Massachusetts Institute of Technology. Used for groups, vector spaces, linear transformations and linear groups. Accessed 2026-08-13.
  • The Stacks Project — table of contents — The Stacks Project. Used for commutative algebra, homological algebra, modules and derived categories. Accessed 2026-08-13.

Continue learning

Domain Deep-Dive — Development Approach & Life CycleGuide · Engineering MathematicsPMBOK 7 — The 8 Performance DomainsGuide · Engineering MathematicsThe 8 Performance DomainsGuide · Engineering MathematicsThe Prerequisite Dependency GraphGuide · Engineering Mathematics
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®