Registry Mediated Discovery

Put a maintained discovery registry between agents and changing counterparts so stable names resolve to current locations, interfaces, or contact records instead of hard-coded references.

Gap-fill disposition

discoverability warranted a full archetype because the accepted catalog and earlier queue outputs did not own the complete registry-mediated discovery pattern: stable discovery key, current locator binding, resolver contract, freshness/liveness policy, visibility rule, lifecycle state, and stale-reference fallback.

Practical frame

A durable identifier is useful only if someone can later find the current reachable thing it denotes. In small systems, direct references and local memory often work. In changing systems, they become hidden coupling. Registry-Mediated Discovery introduces a maintained indirection surface so callers can ask a governed registry for the current contact point, endpoint, location, role-holder, successor, or unavailable state.

Use checklist

1. Name the discovery key callers will use.
2. Decide who may publish, update, retire, or contest entries.
3. Separate stable identity fields from current locator fields.
4. Add freshness, liveness, and cache rules.
5. Return explicit lifecycle states rather than silent failures.
6. Apply visibility and access controls to discovery metadata.
7. Monitor stale-reference incidents and lookup success.

Boundary cautions

Do not collapse this draft into generic search or retrieval. Search helps users find unknown things. Registry-mediated discovery helps users resolve a known key, role, identifier, or category into a current reachable counterpart. Also do not collapse it into Durable Identifier Binding without preserving the difference between assigning a durable referent handle and maintaining the current locator/resolution layer that makes the handle operational over time.

Common Mechanisms

• Catalog or Broker Directory
• Directory Service
• Federated Registry Synchronization
• Human Referral Directory
• Lease or Heartbeat Registration
• Name Resolution Service
• Registry Query API
• Resolver Cache with TTL
• Service Registry
• Successor Forwarding Record

Compression statement

When participants, services, records, assets, or resources must be findable despite changes in location, ownership, endpoint, name, version, health, or availability, create a registry-mediated discovery surface: define discovery keys and referent scope, collect current locator records under stewardship, expose a resolver/query contract, enforce visibility and trust rules, maintain freshness/liveness signals, and provide fallbacks for stale, ambiguous, retired, or superseded bindings.

Canonical formula: Discover(key, context) -> current_locator_record | successor | unavailable | ambiguous, governed by registry_authority, freshness_policy, visibility_rule, and lifecycle_state

Related Abstractions

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (8)

• Discoverability: Measure the degree to which a system's actions and features can be located through perception and exploration alone — a property of the artifact, not the user — separating capability from findable capability and locating unfound features as a design defect.
• Identifier Assignment: Mint a durable handle for an entity and bind it to that entity in a public, queryable record, so future reference can route through the handle without re-describing the entity.
• Index: An auxiliary key-to-location table that makes lookup fast at the cost of maintenance.
• Indirection: Introduces intermediary references.
• Persistent Identifier: A designed token committed to keep resolving to its entity across changes in the entity's location, representation, custodian, or version, via a separately maintained resolver.
• Reification: An abstraction designed to summarise a substrate is treated as the substrate itself, with the audit trail back to the original allowed to atrophy.
• Search and Retrieval: Locate and extract information.
• Site: A persistent, addressable position whose identity is given by its capacity to host or contain entities, surviving the turnover of whatever occupies it.

Also references 22 related abstractions

• Access Control: Restrict system access.
• Appellation: A stable opaque token is bound by an authoritative act to an entity and thereafter used to refer to it across contexts, decoupling reference from description.
• Authentication: Binding an asserted identity or origin to admissible evidence through a procedure that yields a verdict, before trust, access, or weight is granted.
• Boundary: Defines system limits.
• Consistency: A set of commitments cannot jointly derive a contradiction.
• Context: Surrounding state that selects which content a fixed focal signal carries.
• Coupling: Interdependence among subsystems.
• Data Integrity: Accuracy and consistency preserved.
• Hashing: Deterministically reducing any object to a short fixed-size token used as its handle.
• Hierarchical Address: A single string whose substring structure encodes a path through a tree, so the identifier simultaneously names an entity and locates it within a containment hierarchy.

▸ Show 12 more

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Service Discovery Registry · domain variant · recognized

A distributed-systems variant that maps stable service names to current running instances, endpoints, versions, and health state.

• Distinct from parent: The parent is cross-domain; this variant is the software service-resolution form.
• Use when: Services scale, migrate, deploy, or fail over while callers need stable discovery; Health and freshness data materially affect routing decisions.
• Typical domains: software architecture, cloud platforms, microservices
• Common mechanisms: service registry, lease or heartbeat registration, registry query api

Directory-Mediated Referral · communication variant · recognized

A human or institutional variant that maps roles, needs, or stable entities to current responsible people, offices, contacts, or referral channels.

• Distinct from parent: The parent includes machine and record discovery; this variant emphasizes social and institutional handoff.
• Use when: A caller knows a role, need, or organization but not the current responsible contact; Personnel or duty assignments change faster than external references.
• Typical domains: healthcare, emergency management, organizations
• Common mechanisms: human referral directory, catalog or broker directory

Persistent Identifier Resolution · temporal variant · merge review

A variant where a persistent identifier resolves to current metadata, locations, successors, or archival states across platform and custody changes.

• Distinct from parent: The parent includes any registry-mediated discovery; this variant overlaps strongly with Durable Identifier Binding.
• Use when: Long-lived citations must survive storage migrations; Resolution should expose current landing pages, successor records, or unavailable states.
• Typical domains: publishing, archives, data repositories
• Common mechanisms: name resolution service, successor forwarding record, resolver cache with ttl

Near names: Service Discovery, Discovery Registry, Directory Service Discovery, Identifier-to-Location Resolution.