.me — addressing
Namespace
jabellae.cleaker.me
jabellae.local.cleaker
me://jabellae.cleaker.me/profile.nameA namespace names WHICH tree of meaning you're addressing. Path (me.whatever(what)) names WHERE in it. Two different questions, answered two different ways — see O(k) Semantic Kernel Architecture for the tree the namespace points at.
Grammar
| handle | the claimed identity within a root — jabellae |
| root | the namespace's own anchor — cleaker.me, local.cleaker, any <root> |
| handle.root | the composed namespace — jabellae.cleaker.me |
| path | local state within that tree — bookmarkable, shareable, survives a refresh |
import me from "this.me";
import cleaker from "cleaker";
const identity = me("jabellae", "my-secret"); // who: offline identity
const node = cleaker(identity, "cleaker.me"); // where: jabellae.cleaker.me
cleaker(identity); // no namespace given → defaults to cleaker.meTwo ways to be addressed
| Mounted natively | the page IS a door of the namespace — window.location.origin and the namespace are the same thing. |
| Referenced from outside | any page can point INTO a namespace — a link, a QR, an NRP expression — without being its door. The namespace is resolved from identity, never guessed from wherever the page happens to be served. |
The second case is the normal one, not the exception — a namespace is not the URL bar. It is whatever the identity resolves to, wherever you're standing when you ask.
What you see in each
| Natively | you open cleaker.me at cleaker.me: the namespace's own interface, its QR in the center, ready to connect. Its links are routes — you browse the namespace itself, and each route opens in the content area. |
| From outside, a site with .GUI | the app draws its own bars; the namespace's links appear in them, after the app's. Choosing one opens it over the app, in the content area's place. |
| From outside, a site without .GUI | any page: Cleaker brings the bars and lays them over the page. The namespace's links open the same way, over the page, in the content area's place. |
From outside, the namespace never takes the page over: it opens on top of whatever route of that domain you are on, and closing it leaves the page exactly as it was. Only where the page is the namespace does its content area belong to it.