The namespace algebra behind .me — and why it matters

#webdev #opensource #programming #ai

Most systems start with data while .me started with a question:

What is a namespace, really?

Not "what does it do" — but what is it, structurally. The answer I arrived at is simple but it changes everything:

A namespace is a region. And regions have a natural algebra.

The core rule

More specific ⇒ subset. Always.

cleaker.me ⊇ jabellae.cleaker.me
jabellae.cleaker.me ⊇ jabellae.cleaker.me/profile
jabellae.cleaker.me ⊇ jabellae.cleaker.me:8161

This isn't a convention. It's a consequence of what namespaces are. Adding a coordinate (subdomain, port, path) shrinks the region. B adds coordinates to A → B ⊆ A. Always.

Why this matters for routing

Traditional routing is host-first: you pick a server, then navigate a path. The namespace algebra inverts this. You name the thing first — semantically, precisely — and resolution figures out where it lives.

me://jabellae.cleaker.me[surface:iphone]/profile

That's not a URL. It's a semantic address. The namespace tells you who. The selector tells you which surface. The path tells you what. Resolution happens after naming, not before.

The six axioms (A0–A5)

I formalized this into six axioms:

A0 — namespace as region (coordinates define a set)
A1 — relation as function (viewer → target)
A2 — relation refinement (more specific overrides)
A3 — relation composition (chains resolve transitively)
A4 — identity relation (you resolve to yourself)
A5 — existence relation (any viewer maps to a base namespace)

These aren't arbitrary design choices. They fall out of what a namespace structurally is. I didn't invent them — I found them.

What this enables

When your addressing system has a real algebra underneath, you get things for free that other systems have to hack in:

conflict resolution (more specific wins, always)
composable routes (A3 handles chains)
local-first resolution (A4 before any network call)
semantic multi-device addressing without DNS hacks

This algebra is the foundation of .me — a semantic reactive kernel for sovereign personal computing. The full spec, the npm packages, and the URI scheme are open source and public domain.

npm: this.me · cleaker · neurons.me