Namespaces and Addresses

Why addresses matter

Addresses can answer who is being reached, what role is being invoked, what route is being used, what context may be included, and what boundary governs the exchange.

Personal namespaces

A personal namespace might someday look like <username>@yihaw.net. No public namespace system is available yet. This page defines the questions before the system exists.

Service namespaces

Future surfaces might include shapes such as app.yihaw.net/<username>, blog.yihaw.net/<username>, or media routes. These examples are not promises.

Example shapes

• A person address should protect identity and consent.
• A service route should protect ownership and access.
• An agent route should name delegation and limits.
• A temporary route should expire clearly.

Questions before launch

Before any namespace becomes real, yihaw.net needs clear answers for identity verification, ownership transfer, delegation, retention, export, deletion, abuse prevention, observability, and recovery.