Well-Known URIs gave every website one discovery shelf

Many web protocols need to learn something about a site before using it: policy, configuration, certificates, app links or account metadata. Without a convention, each protocol would invent a root-level URL and risk colliding with the site's own content.

Well-Known URIs solved that with one intentionally dull prefix: /.well-known/. Protocols register a suffix, and clients know where to look without scanning or guessing.

The genius is restraint. The standard does not centralize hosting or dictate the metadata format. It only reserves a tiny part of URI space and adds an IANA registry so discovery remains predictable.

Reserve one discovery shelf

A fixed prefix reduces client-side guessing and extra round trips.

Registration prevents protocol names from trampling one another.

Sites keep the rest of their URI space under their own control.

Discovery works when the namespace is boring and governed. One small reserved shelf beats a hundred protocols grabbing random front-door URLs.

The pattern became a quiet dependency for modern web infrastructure, including security, identity and automation protocols. ACME, WebFinger, OpenID-related discovery and security.txt-style conventions all benefit from having one recognized place to put origin-level facts.