Reuleaux polygon¶

A convex constant-width curve assembled from an odd number of equal-radius circular arcs, with each arc centered at an opposite vertex of its generating polygon.

Version: v1 · 2026-09-08 · History
Domain-specific #: 6508
Origin domain: convex geometry
Subdomain: curves of constant width

Core Idea¶

A Reuleaux polygon is a curve of constant width composed of circular arcs of one radius, constructed so each arc is centered at the vertex opposite the replaced side interval.^[1] As parallel support lines rotate, one touches an arc and the opposite one touches that arc's center vertex. Equal radii keep support-line separation constant despite changing contact points. 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 convex geometry. It is piecewise-circular constant width generated by opposite vertex centers, including approximation of arbitrary constant-width curves. That residual remains recognizable when examples, notation, scale, or implementation change, but it disappears if the carrier is mistyped, the condition that the closed convex boundary uses an odd number of equal-radius arcs and every pair of parallel support lines has the same separation 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 closed convex boundary uses an odd number of equal-radius arcs and every pair of parallel support lines has the same separation. 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 closed convex boundary uses an odd number of equal-radius arcs and every pair of parallel support lines has the same separation, 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 Reuleaux polygon, 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.

Structural Signature¶

Carrier: an odd-sided convex generating polygon satisfying opposite-distance conditions and a closed boundary formed from equal-radius circular arcs
Inputs or antecedent state: the exact convex geometry carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate Reuleaux polygon
Constitutive operation: As parallel support lines rotate, one touches an arc and the opposite one touches that arc's center vertex. Equal radii keep support-line separation constant despite changing contact points.
Invariant: the closed convex boundary uses an odd number of equal-radius arcs and every pair of parallel support lines has the same separation
Recognition test: type the carrier, state every parameter and convention in the definition, test that the closed convex boundary uses an odd number of equal-radius arcs and every pair of parallel support lines has the same separation, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases
Output or consequence: recognizing and comparing instances of Reuleaux polygon, 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 closed convex boundary uses an odd number of equal-radius arcs and every pair of parallel support lines has the same separation 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 convex geometry. The field contains many questions and methods that do not instantiate Reuleaux polygon.
It is not its most familiar example. Replacing the three sides of an equilateral triangle by arcs centered at the opposite vertices produces the Reuleaux triangle. exhibits the structure, but the example is evidence for the abstraction rather than its definition.
It is not the neighboring catalog concept Curve of constant width. Curves of constant width may be smooth or use arcs of unequal radii; a Reuleaux polygon is the equal-radius, odd-arc subclass generated from a qualifying polygon.
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 Reuleaux polygon must control the decision
It is not an unrestricted metaphor for any process that seems similar. Outside convex geometry, the vocabulary and validity conditions do not transfer literally.

Scope of Application¶

Reuleaux polygon belongs to convex geometry and is useful where the analyst can specify an odd-sided convex generating polygon satisfying opposite-distance conditions and a closed boundary formed from equal-radius circular arcs, then evaluate the closed convex boundary uses an odd number of equal-radius arcs and every pair of parallel support lines has the same separation. The scope is broad within that domain but bounded by the need for the closed convex boundary uses an odd number of equal-radius arcs and every pair of parallel support lines has the same separation. 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 convex geometry carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate Reuleaux polygon are converted, constrained, or organized by As parallel support lines rotate, one touches an arc and the opposite one touches that arc's center vertex. Equal radii keep support-line separation constant despite changing contact points..
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 Reuleaux polygon 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 Reuleaux polygon, 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 closed convex boundary uses an odd number of equal-radius arcs and every pair of parallel support lines has the same separation 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 Reuleaux polygon 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 convex geometry carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate Reuleaux polygon, the structure counts as Reuleaux polygon exactly when the closed convex boundary uses an odd number of equal-radius arcs and every pair of parallel support lines has the same separation.

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 Reuleaux polygon. Reuleaux polygon 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 Reuleaux polygon. 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: an odd-sided convex generating polygon satisfying opposite-distance conditions and a closed boundary formed from equal-radius circular arcs. Reject examples whose alleged carrier belongs to a different problem.
Lock the constitutive rule. Express the closed convex boundary uses an odd number of equal-radius arcs and every pair of parallel support lines has the same separation independently of one notation or implementation. This step prevents the canonical example from becoming the definition.
Derive consequences. From the closed convex boundary uses an odd number of equal-radius arcs and every pair of parallel support lines has the same separation, infer recognizing and comparing instances of Reuleaux polygon, 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 Reuleaux polygon must control the decision and an object that resembles Reuleaux polygon 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 convex geometry because they reuse an odd-sided convex generating polygon satisfying opposite-distance conditions and a closed boundary formed from equal-radius circular arcs, As parallel support lines rotate, one touches an arc and the opposite one touches that arc's center vertex. Equal radii keep support-line separation constant despite changing contact points., and type the carrier, state every parameter and convention in the definition, test that the closed convex boundary uses an odd number of equal-radius arcs and every pair of parallel support lines has the same separation, 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 Replacing the three sides of an equilateral triangle by arcs centered at the opposite vertices produces the Reuleaux triangle. to A many-arc Reuleaux polygon approximates a smooth constant-width profile for coin or rotor design while preserving caliper diameter in every orientation..^[3]

Transfer outside the home domain is weaker. The skeletal pattern—type the carrier, apply the defining mechanism of Reuleaux polygon, 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¶

Replacing the three sides of an equilateral triangle by arcs centered at the opposite vertices produces the Reuleaux triangle. The example exposes the carrier and directly tests that the closed convex boundary uses an odd number of equal-radius arcs and every pair of parallel support lines has the same separation; 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 an odd-sided convex generating polygon satisfying opposite-distance conditions and a closed boundary formed from equal-radius circular arcs; the operative rule is As parallel support lines rotate, one touches an arc and the opposite one touches that arc's center vertex. Equal radii keep support-line separation constant despite changing contact points.; the invariant is the closed convex boundary uses an odd number of equal-radius arcs and every pair of parallel support lines has the same separation; and the result supports recognizing and comparing instances of Reuleaux polygon, 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 closed convex boundary uses an odd number of equal-radius arcs and every pair of parallel support lines has the same separation destroys the classification.

Mapped back: an odd-sided convex generating polygon satisfying opposite-distance conditions and a closed boundary formed from equal-radius circular arcs → As parallel support lines rotate, one touches an arc and the opposite one touches that arc's center vertex. Equal radii keep support-line separation constant despite changing contact points. → the closed convex boundary uses an odd number of equal-radius arcs and every pair of parallel support lines has the same separation → recognizing and comparing instances of Reuleaux polygon, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions

Applied / In Practice¶

A many-arc Reuleaux polygon approximates a smooth constant-width profile for coin or rotor design while preserving caliper diameter in every orientation. 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 closed convex boundary uses an odd number of equal-radius arcs and every pair of parallel support lines has the same separation, 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 closed convex boundary uses an odd number of equal-radius arcs and every pair of parallel support lines has the same separation 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 Reuleaux polygon, preserve its invariant, and derive only consequences licensed by the stated boundary. Its identity-bearing terms—Reuleaux polygon, carrier, parameter, invariant, boundary, evidence, model, transformation, and application—derive their meaning from convex geometry 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, As parallel support lines rotate, one touches an arc and the opposite one touches that arc's center vertex. Equal radii keep support-line separation constant despite changing contact points., a recognition invariant, and a consequence. That skeleton may resemble patterns elsewhere, especially type the carrier, apply the defining mechanism of Reuleaux polygon, preserve its invariant, and derive only consequences licensed by the stated boundary. The domain accent is not decorative: Reuleaux polygon, 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 convex geometry.

The proposed strict upward parent is prime:invariance. The defining property is invariant width under rotation of the support direction; piecewise-circular construction supplies the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Reuleaux polygon adds domain-specific constraints.

The entry does not collapse into that parent because piecewise-circular constant width generated by opposite vertex centers, including approximation of arbitrary constant-width curves It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Reuleaux polygon. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge.

The prospective workspace queue contains one strict upward edge to prime:invariance. No live DAG mutation is authorized.

Relationships to Other Abstractions¶

Current abstraction Reuleaux polygon Domain-specific

Parents (1) — more general patterns this builds on

Reuleaux polygon is a kind of Invariance Prime

The proposed strict upward parent is prime:invariance.

Hierarchy path (1) — routes to 1 parentless root

Reuleaux polygon → Invariance

Neighborhood in Abstraction Space¶

Reuleaux polygon sits in a moderately populated region (43^rd percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Convex Geometry & Spatial Partition (35 abstractions)

Nearest neighbors

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

Not to Be Confused With¶

Curve of constant width. Curves of constant width may be smooth or use arcs of unequal radii; a Reuleaux polygon is the equal-radius, odd-arc subclass generated from a qualifying polygon.
One canonical example. An instance demonstrates the structure but does not define the whole abstraction.
Measurement or implementation of Reuleaux polygon. A proxy or realization is evidence for the abstraction, not the abstraction itself.
Generalized Reuleaux polygon. An extension qualifies only when its changed axioms and retained invariant are stated.

References¶

[1] Tommy Bonnesen and Werner Fenchel, Theorie der konvexen Körper, Springer, 1934; English translation Theory of Convex Bodies, BCS Associates, 1987. registry ↩a ↩b

[2] Martin Gardner, The Colossal Book of Mathematics, W. W. Norton, 2001/2006, curves of constant width. registry ↩a ↩b

[3] Peter M. Gruber, Convex and Discrete Geometry, Springer, 2007, DOI 10.1007/978-3-540-71133-9. registry ↩