Astronym Registry
Status RDAP

Architecture

Built as a system, not a stack.

A registry has to accept precise transactions, protect authoritative state, publish the right data, and make important outcomes understandable. Astronym is organized around those enduring responsibilities.

Systems view · From interface to evidence

Conceptual model

Clear boundaries from request to result.

The clearest way to understand Astronym is by responsibility. Standards define the edges. Registry rules govern change. Authoritative state anchors the result. Publication and evidence make that result useful and accountable.

Public, responsibility-level view of the registry platform
Provisioning Registrar systems
Direction Registry policy
Discovery Public Internet
Standards boundary EPP provisioning
Decision boundary Policy & lifecycle rules
Publication boundary RDAP & DNS data
The system of record Authoritative registry state One coherent account of names, relationships, and lifecycle
Required outputs Reporting & escrow
Accountability Operational evidence
Stewardship Abuse & compliance workflows
Security Observability Continuity Human operations

A responsibility-level view of how standards, state, publication, and assurance work together as one registry system.

Design principles

Architecture that can explain itself.

Complex systems earn trust when responsibilities, state changes, and evidence are clear enough to reason about. Astronym is designed to make that clarity a property of the system.

  • 01

    Standards at the boundaries

    Stable, well-understood protocols make interoperability a design constraint instead of a later integration exercise.

  • 02

    Authoritative state at the center

    Every registry action should resolve to one durable, explainable account of what changed and why.

  • 03

    Policy is explicit

    Lifecycle decisions belong in deliberate rules and reviewable workflows, with each important change clear and accountable.

  • 04

    Evidence follows the work

    Important outcomes should leave useful proof for operations, compliance, learning, and review.

  • 05

    Failure is a design input

    Boundaries, recovery paths, and safe behavior matter most when the easy path is unavailable.

  • 06

    Humans remain in the system

    Clear ownership, understandable controls, and useful diagnostics are part of the architecture.

Three lenses

Transact. Publish. Assure.

01

Transaction

Accept intended changes through precise interfaces, apply registry policy, and preserve a clear lifecycle.

02

Publication

Turn authoritative state into the appropriate standards-based data for the systems and people that rely on it.

03

Assurance

Observe behavior, retain meaningful evidence, and make operating decisions from facts rather than assumptions.

The long view

Good architecture is measured by the quality of the boundaries between components.

Astronym applies lessons from more than three decades of Internet engineering to a registry platform intended to remain comprehensible as it grows.

Next layer

An overview designed for deeper dives.

Future notes will take individual ideas from this map—protocol boundaries, registry state, lifecycle policy, publication, operational evidence, and continuity—and examine the engineering behind each one in greater depth.

Protocol boundaries Registry state Lifecycle policy Data publication Operational evidence Continuity engineering
Our engineering approach Intended services