Site Registry¶
Registry — instantiates Persistent Site Framing
The authoritative catalog of sites — binding each host position's identity and steward to a durable entry that persists through every occupant.
A Site Registry is the single authoritative list of the host positions a system agrees exist, where each entry answers two questions no occupant is allowed to answer for it: what makes this site the same site over time, and who is responsible for it. Everything else in the archetype — labels, maps, ledgers, dashboards — hangs off registry entries, but the registry's own job is narrow and foundational: it is the object of record for site identity and stewardship, the place where "rack B-14" or "the corner office" is defined once, independently of whatever is currently sitting in it. Its defining move is that a registry entry survives an empty site: delete the occupant and the entry stays; retire the site and the entry is marked retired rather than erased.
Example¶
A data center operations team has drifted into naming rack units after the servers in them — "the Postgres box," "the old billing node." When a server is swapped, the name lies, and nobody can say which physical position lost redundancy. They stand up a Site Registry. Each rack unit gets one entry: an identity frame that fixes it to a physical coordinate (row, cabinet, U-height range) and a named steward — the facilities engineer accountable for that cabinet. The entry declares what the site is, not what hardware occupies it.
The payoff shows up the first time a server dies. Before, the ticket said "replace the Postgres box." Now it says "U22–U23 in cabinet B-14 is vacant; steward is Priya." The position is addressable while empty, the person to call is unambiguous, and when new hardware lands, only the occupancy relation changes — the registry entry, its identity, and its steward hold still. The registry didn't schedule the swap or draw the floor; it just guaranteed there was a stable site for all of that to refer to.
How it works¶
The registry is a curated table with exactly one row per site and a discipline about what may change it. Two rules do the heavy lifting. First, identity is stated, not inferred: each entry carries an explicit identity frame (a coordinate, legal description, namespace path, or authority grant) so the site cannot be silently redefined by whoever occupies it. Second, every site has a steward — a named owner accountable for the entry's accuracy and for lifecycle decisions (create, split, merge, retire). New sites enter through the steward, not through a side door; a site with no steward is a registry defect, not a valid state.
The registry deliberately does not store occupancy, capacity checks, or spatial layout. It references the token that addresses each entry and hands the rest to specialized mechanisms, keeping itself thin enough to stay trustworthy.
Tuning parameters¶
- Granularity — one entry per building, per room, per rack unit, per shelf. Finer entries give precision and localize accountability but multiply maintenance; coarser entries are cheap but hide meaningful distinctions.
- Identity basis — physical coordinate, legal parcel, logical namespace, or organizational authority. The basis you pick determines what kinds of change count as "the same site" versus "a new site."
- Stewardship model — a single owner per site, a role-based steward, or a team. Tighter ownership sharpens accountability but bottlenecks change; shared stewardship scales but risks the tragedy of the unowned entry.
- Entry lifecycle strictness — how ceremonious creation and retirement are. Heavy gates keep the registry clean but slow; light gates keep it current but invite ghost entries.
When it helps, and when it misleads¶
The registry earns its keep by being the system of record[n1] everything else can trust: with identity and stewardship pinned down, occupancy can turn over freely without the underlying position becoming ambiguous. It is the antidote to occupant-site conflation — the failure where a position quietly inherits the name of its current tenant.
Its classic failure is the opposite of drift: treating the identifier as sacred. A registry that never retires entries accumulates ghost sites — rows that are still assignable long after the physical position is gone — and a registry whose identity frame is too rigid resists legitimate redesign, so teams route around it and it silently goes stale. The tolerable misuse is the well-meaning "just add a column" that turns the registry into a dumping ground for occupancy state and capacity notes it was never meant to own, at which point it stops being authoritative because it is now everywhere and nowhere. The guarding discipline is to keep the registry to identity and stewardship, let the steward — not the crowd — mutate entries, and mark retirement explicitly rather than deleting.
How it implements the components¶
Site Registry fills the identity-and-ownership core of the archetype, and only that:
site_identity_frame— each entry states, explicitly and durably, what makes the site itself across time, so no occupant can redefine it.site_lifecycle_steward— every entry names the owner accountable for its accuracy and for create/split/merge/retire decisions.
It does not render the handle those entries reference — addressable_site_token and its context_anchor_metadata are the Physical or Virtual Labeling System's (the registry's nearest twin: the registry owns the site, the labeling system makes its token findable) — and it stores no occupancy_relation_record; that belongs to the Occupancy Ledger.
Related¶
- Instantiates: Persistent Site Framing — the registry is the object of record that gives every other mechanism a stable site to point at.
- Consumes: Physical or Virtual Labeling System — supplies the addressable token each entry hangs on.
- Sibling mechanisms: Physical or Virtual Labeling System · Site Map or Plan · Capacity-Fit Matrix · Assignment and Release Workflow · Occupancy Ledger · Site Lineage Tombstone · Vacancy Status Dashboard · Site Audit Walkthrough
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Site Registry operates as a persistent ledger, log, register, or case record that preserves history and traceability because it the authoritative catalog of sites — binding each host position's identity and steward to a durable entry that persists through every occupant.
Independent corroboration: The frozen evidence defines Site Registry as 'The authoritative catalog of sites — binding each host position's identity and steward to a durable entry that persists through every occupant', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Library & Information Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: An authoritative durable catalog binding site identity to steward is a metadata-registry mechanism. NARA defines a registry as the managed home of precise identifiers, meanings, values, and authoritative metadata; architecture supplies spatial attributes.
Related originating lineages:
- Architecture & Urban Planning — Site identity and position support spatial planning across changing occupants.
- Computer Science & Software Engineering — Stable identifiers and records preserve continuity through lifecycle changes.
- Law & Governance — Land and facility registers establish accountable custodianship.
- Organizational & Management Science — organizational_management contributes organizational design, management, and operational governance to this mechanism's defining operation—The authoritative catalog of sites — binding each host position's identity and steward to a durable entry that persists through every occupant—without displacing the selected primary historical lineage.
- Public Administration & Policy — public_administration_policy contributes public administration, policy implementation, and program oversight to this mechanism's defining operation—The authoritative catalog of sites — binding each host position's identity and steward to a durable entry that persists through every occupant—without displacing the selected primary historical lineage.
Review resolution: The blind reviewers disagree on primary lineage (library_information_science versus architecture_urban_planning). Authoritative or primary research supports library_information_science as the best historical origin: An authoritative durable catalog binding site identity to steward is a metadata-registry mechanism. NARA defines a registry as the managed home of precise identifiers, meanings, values, and authoritative metadata; architecture supplies spatial attributes. The cited National Archives, Federal Enterprise Architecture Records Management Profile directly supports the mechanism's defining operation. All independently supported contributing domains are retained without an arbitrary cap. origin_mode=cross_disciplinary_synthesis records lineage, while domain_reach=multi_domain records later applicability separately from provenance.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
[n1] A system of record is the authoritative source for a given data element — the one place other systems defer to when copies disagree. A site registry is the system of record for site identity and stewardship, which is exactly why it must resist absorbing data it isn't authoritative for. ↩