Discoverability¶
Core Idea¶
Agents find each other through a shared registry rather than by direct reference: providers register under stable logical names, consumers resolve those names to a current location at use-time, and the registry is the only address either side must know in advance — so the coupling survives turnover.
How would you explain it like I'm…
The Magic Phone Book
Imagine you want to find your friend, but instead of memorizing where she lives, you ask the front desk and they tell you her room right now. If she moves to a new room, the front desk just updates it, and you can still find her by name. You only have to remember the front desk, not every friend's room.
Look It Up by Name
Discoverability is when things find each other through a shared directory instead of by knowing each other's exact address. Each helper signs up in the directory under a name. When someone needs a helper, they look up the name and the directory tells them where that helper is right now. The clever part is that if a helper moves, the directory updates, and the people looking still find them without changing anything. So the only address you must memorize is the directory itself.
Registry Indirection
Discoverability is a structural pattern where providers and consumers connect through a shared registry rather than by hardcoding each other's locations. A provider registers under a stable name; a consumer looks up that name and gets the provider's current location. The name stays fixed even when the location changes, so providers can come, go, or relocate without breaking anyone. This is different from simply naming things (which only gives them labels) and from the interface (how two parties talk once connected). The registry is a single point of indirection that replaces the impossible job of everyone tracking everyone.
Discoverability names the structural pattern in which agents locate each other through a shared registry that sits as a named indirection between consumers and providers, rather than through direct reference. It rests on four load-bearing commitments. First, a three-party structure: provider, consumer, and registry are distinct roles, and the registry is its own addressable entity rather than a property of either party. Second, indirection over direct reference: consumers hold provider names, not locations, and resolve them at use-time. Third, a mutable mapping under a stable name: the logical identifier stays constant while the location it resolves to may change without the consumer ever knowing. Fourth, turnover survival: providers can join, leave, and relocate while consumers keep connecting to currently-correct providers with no code or address change, so the coupling outlives party turnover. This is not naming (which only requires identifiers), nor interface (how parties interact after finding each other), nor networking (the substrate lookup runs on). The decisive test is whether a provider can change location without consumer code changing — and the same test applies socially, where it becomes whether a professional can move offices without each client losing them.
Broad Use¶
- DNS: domain names resolve to current IP addresses; servers change IPs without client reconfiguration.
- Microservices: services register endpoints under logical names; consumers query and receive an up-to-date endpoint.
- Civic life: phone directories and library catalogs map stable names or call numbers to current numbers and shelf locations.
- Scholarship: DOIs and bibliographic keys map to current canonical locations.
- Platforms: drivers and hosts register availability; the matchmaking platform mediates discovery.
- Microbiology: in quorum sensing, a chemical-concentration field acts as a passive registry of population density.
Clarity¶
Naming the pattern surfaces the registry as a separate object of design — who runs it, how it fails, who governs registration — instead of folding it into one of the parties it mediates.
Manages Complexity¶
It collapses N×M pairwise coupling to N+M+1: each side knows only the registry, so providers and consumers change independently through one indirection point.
Abstract Reasoning¶
When N parties must reach M, factor the stable-name/mutable-location mapping into a registry — and treat its three pathologies (bottleneck, trust-anchor, staleness) as the inherent price, to be bounded rather than wished away.
Knowledge Transfer¶
- Distributed systems → healthcare: the registry refactor that rescues a tangled microservice config also rescues a referral network when personal address books break on staff turnover.
- Engineering → any substrate: a practitioner who has managed DNS staleness asks, everywhere, what the staleness window is and who controls registration.
- Architecture → microbiology: recognizing a passive concentration field as an implicit registry ports the coupling analysis to diffusion-mediated systems no one designed.
Example¶
A web operator renumbers from one IP to another and every browser worldwide reaches the new address without a single client change — the turnover-survival test that defines discoverability.
Relationships to Other Primes¶
Parents (1) — more general patterns this builds on
- Discoverability is a kind of Indirection — The SPECIFIC three-party form of indirection — provider, consumer, and a registry that is its own addressable entity — whose payoff is turnover survival (a provider can relocate without consumer change). The file calls indirection 'the prime's structural parent'; discoverability USES indirection but adds the registry, the stable-name/mutable-location split, and turnover survival.
Path to root: Discoverability → Indirection → Layering
Not to Be Confused With¶
- Discoverability is not Indirection because discoverability is the specific three-party registry form whose payoff is turnover survival, whereas indirection is the general move of resolving a reference through a pointer.
- Discoverability is not Traceability because discoverability is forward-looking resolution of a name to a current location, whereas traceability links artefacts backward to their origins for accountability.
- Discoverability is not Interface because discoverability governs how parties find each other, whereas an interface governs how they interact once found.