Complex polytope¶

A regular incidence geometry modeled in complex unitary space that generalizes real regular polytopes through complex reflections and phase-valued incidence.

Version: v2 · 2026-09-19 · History
Domain-specific #: 3804
Domain group: Formal Sciences
Origin domain: Mathematics
Subdomain: Complex Geometry → Mathematics

Core Idea¶

General definitions outside the regular case are not fully uniform, complex dimension is not simply doubled real polytope dimension and faces and incidence are projective or unitary configurations rather than ordinary convex hulls.^[1] Finite unitary reflection groups generate flags of incident complex subspaces; regularity makes the automorphism group transitive on flags and symbolic diagrams encode reflection orders and incidence. 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 complex geometry. It is the domain-specific identity fixed by the complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes are explicit. That residual remains recognizable when examples, notation, scale, or implementation change, but it disappears if the carrier is mistyped, the condition that the complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes are explicit 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 complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes are explicit. 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 complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes are explicit, 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 Complex polytope, 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…

No faithful explanation at this level. All three generators agree the only child-level picture is a solid shape with flat faces, which is exactly the convex real polytope complex polytopes are distinguished from; their faces are incident complex subspaces, not filled regions.

Pieces-and-Touching Pattern

Normal shapes like triangles and cubes have corners, edges, and faces, and you can think of them as solid chunks of space. Mathematicians made a version of this in a space that uses complex numbers instead of ordinary ones. There, a complex polytope isn't a solid chunk at all: it's a pattern of points, complex lines, and bigger flat pieces that fit together in a particular way. The nicest ones, called regular complex polytopes, have so much symmetry that every 'corner-edge-face' chain looks exactly like every other. Their symmetries are made from special reflection-like moves in complex space.

Complex Incidence Polytope

A real polytope, like a cube, is built from vertices, edges, and faces and fills in a convex region. A complex polytope is an analogue in a complex space, but its faces are not convex pieces: they are points, complex lines, and higher complex subspaces arranged by an incidence relation (which ones lie in which). A flag is a chain of faces, one of each rank, each inside the next. A complex polytope is regular if its symmetry group can move any flag to any other. These symmetries come from finite unitary reflection groups — complex versions of reflections, which can have orders other than 2 — and a diagram or symbol records the reflection orders and how faces are connected. Complex dimension isn't simply twice the dimension of a real polytope, and general definitions outside the regular case aren't fully standardized.

Complex polytopes are analogues of polytopes in complex Hermitian or projective space, whose faces — points, complex lines, and higher complex subspaces — and incidence relations are projective or unitary configurations rather than convex hulls. General definitions outside the regular case are not fully uniform, and complex dimension is not simply double the real polytope dimension. In the regular case, finite unitary reflection groups generate flags of incident complex subspaces; regularity means the automorphism group acts transitively on maximal flags. Coxeter-like symbols and diagrams encode the orders of the generating reflections, which need not be 2, and the incidence structure. Rigorous treatment must state the ambient space, rank and face types, incidence relation, flags, automorphism or unitary reflection group and its generators, the finite versus infinite case, and any real section or realization. The concept must be distinguished from convex real polytopes and from purely combinatorial abstract polytopes.

Structural Signature¶

Carrier: the typed complex geometry carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets
Inputs or antecedent state: the exact complex geometry carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate Complex polytope
Constitutive operation: Finite unitary reflection groups generate flags of incident complex subspaces; regularity makes the automorphism group transitive on flags and symbolic diagrams encode reflection orders and incidence.
Invariant: the complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes are explicit
Recognition test: type the carrier, state every parameter and convention in the definition, test that the complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases
Output or consequence: recognizing and comparing instances of Complex polytope, 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 complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes are explicit 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 complex geometry. The field contains many questions and methods that do not instantiate Complex polytope.
It is not its most familiar example. A canonical instance directly demonstrates that the complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes are explicit. exhibits the structure, but the example is evidence for the abstraction rather than its definition.
It is not the neighboring catalog concept Abstract polytope. An abstract polytope is an incidence poset satisfying combinatorial axioms; a regular complex polytope adds realization in complex unitary geometry and reflection structure.
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 Complex polytope must control the decision
It is not an unrestricted metaphor for any process that seems similar. Outside complex geometry, the vocabulary and validity conditions do not transfer literally.

Scope of Application¶

Complex polytope belongs to complex geometry and is useful where the analyst can specify the typed complex geometry carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets, then evaluate the complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes are explicit. The scope is broad within that domain but bounded by the need for the complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes are explicit. 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 complex geometry carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate Complex polytope are converted, constrained, or organized by Finite unitary reflection groups generate flags of incident complex subspaces; regularity makes the automorphism group transitive on flags and symbolic diagrams encode reflection orders and incidence..
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 Complex polytope 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 Complex polytope, 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 complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes 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 Complex polytope 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 complex geometry carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate Complex polytope, the structure counts as Complex polytope exactly when the complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes are explicit.

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 Complex polytope. Complex polytope 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 Complex polytope. 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 complex geometry carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets. Reject examples whose alleged carrier belongs to a different problem.
Lock the constitutive rule. Express the complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes are explicit independently of one notation or implementation. This step prevents the canonical example from becoming the definition.
Derive consequences. From the complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes are explicit, infer recognizing and comparing instances of Complex polytope, 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 Complex polytope must control the decision and an object that resembles Complex polytope 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 complex geometry because they reuse the typed complex geometry carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets, Finite unitary reflection groups generate flags of incident complex subspaces; regularity makes the automorphism group transitive on flags and symbolic diagrams encode reflection orders and incidence., and type the carrier, state every parameter and convention in the definition, test that the complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes are explicit, 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 complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes are explicit. to An applied instance preserves the invariant under changed notation, scale, dataset, jurisdiction, or implementation..^[3]

Transfer outside the home domain is weaker. The skeletal pattern—type the carrier, apply the defining mechanism of Complex polytope, 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 complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes are explicit. The example exposes the carrier and directly tests that the complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes are explicit; 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 complex geometry carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets; the operative rule is Finite unitary reflection groups generate flags of incident complex subspaces; regularity makes the automorphism group transitive on flags and symbolic diagrams encode reflection orders and incidence.; the invariant is the complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes are explicit; and the result supports recognizing and comparing instances of Complex polytope, 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 complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes are explicit destroys the classification.

Mapped back: the typed complex geometry carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets → Finite unitary reflection groups generate flags of incident complex subspaces; regularity makes the automorphism group transitive on flags and symbolic diagrams encode reflection orders and incidence. → the complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes are explicit → recognizing and comparing instances of Complex polytope, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions

Applied / In Practice¶

An applied instance preserves the invariant under changed notation, scale, dataset, jurisdiction, or implementation. 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 complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes are explicit, 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 complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes are explicit 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 Complex polytope, preserve its invariant, and derive only consequences licensed by the stated boundary. Its identity-bearing terms—Complex polytope, carrier, parameter, invariant, boundary, evidence, model, transformation, and application—derive their meaning from complex 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, Finite unitary reflection groups generate flags of incident complex subspaces; regularity makes the automorphism group transitive on flags and symbolic diagrams encode reflection orders and incidence., a recognition invariant, and a consequence. That skeleton may resemble patterns elsewhere, especially type the carrier, apply the defining mechanism of Complex polytope, preserve its invariant, and derive only consequences licensed by the stated boundary. The domain accent is not decorative: Complex polytope, 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 complex geometry.

This entry is a kind of Representation.

It remains its own entry because its identity is fixed by the complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes.

Relationships to Other Abstractions¶

Current abstraction Complex polytope Domain-specific

Parents (1) — outgoing typed relations

Complex polytope is a kind of Representation Prime

It remains its own entry because its identity is fixed by the complex Hermitian or projective space, rank and face types, points complex lines and higher subspaces, incidence relation, flags and maximal flags, automorphism or unitary reflection group, regular flag-transitivity, generators and Coxeter-like diagram or symbol, finite and infinite cases, real section or realization and distinction from convex real and abstract polytopes.

Hierarchy path (1) — routes to 1 parentless root

Complex polytope → is a kind of Representation → presupposes Abstraction

Neighborhood in Abstraction Space¶

Complex polytope 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 — Schemes, Varieties & Moduli Spaces (41 abstractions)

Nearest neighbors

Representation on coordinate rings — 0.91
Holomorphic tangent bundle — 0.90
Positive form — 0.90
Ran space — 0.90
Degeneration (algebraic geometry) — 0.90

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

Not to Be Confused With¶

Abstract polytope. An abstract polytope is an incidence poset satisfying combinatorial axioms; a regular complex polytope adds realization in complex unitary geometry and reflection structure.
One canonical example. An instance demonstrates the structure but does not define the whole abstraction.
Measurement or implementation of Complex polytope. A proxy or realization is evidence for the abstraction, not the abstraction itself.
Generalized Complex polytope. An extension qualifies only when its changed axioms and retained invariant are stated.

References¶

[1] H.S.M Coxeter, 'Regular Complex Polytopes', Cambridge University Press, 1991.not authoritative registry ↩a ↩b

[2] Peter McMullen, Egon Schulte, 'Abstract Regular Polytopes', Cambridge University Press, December 2002. registry ↩a ↩b

[3] Peter Orlik, Victor Reiner, Anne V. Shepler. The sign representation for Shephard groups. Mathematische Annalen. March 2002, Volume 322, Issue 3, pp. 477–492. DOI:10.1007/s002080200001.not authoritative registry ↩