Resolution begins at identity. Platforms are nodes, not destinations.
user → platform → world, where each platform unilaterally
defines what exists and what it means. Instead
world → .me → meaning, where identity is the fixed root and
platforms are nodes resolved into it.
Platform-centric: resolve(request) = platform.scope(request)
.me-centric: resolve(request) = me.graph(request)
In the platform-centric case, platform.scope bounds what
the request can even mean — the platform is the containing context. In
the .me-centric case, the graph is the containing context;
a platform is a reachable node inside it, not the boundary around it.
What makes this a structural claim, not only a preference, is already verified:
me.whatever.you.want("x"). No fixed schema owned by a platform; a person's graph shape is not assigned in advance. See Inverted Dependency Indexing.q ≤ p ⟺ q is a descendant of p. Meaning is addressed by position in a personal graph, not by which app's database row holds it. See SpaceStructure.me:// URI resolves across a mesh of surfaces without a central registry, per the Namespace Resolution Protocol.me
├─ family.photos
├─ family.messages
├─ work.neurons_me
├─ work.github
├─ music.playlists
└─ ai.claudeEach branch is addressable because it was declared, not because a platform shipped a menu item for it. A platform integrating with this graph occupies a node; it does not define the graph's shape.
The same relation holds for what a node means, not just where it
sits — worked out at multi-agent scale in
Robots
That Understand Context: four different agents point into the same
graph from four different context branches and resolve
canProceed to four different answers, without four copies of
the underlying object existing anywhere. The graph doesn't hand out one
fixed menu; it resolves differently depending on where the request enters
it — which is the same property a user-centric system needs from
platforms resolving into a person's own graph, not the other way around.
| Platform-centric | .me-centric | |
|---|---|---|
| Containing context | the platform | the user's graph |
| Addressing | assigned by the app | declared by the user, free-form |
| Optimized for | retention — time inside a boundary | resolution — completing a request |
| What a platform is | a destination | a reachable node |
me:// URI across a mesh —
that part is real, specified, hop-by-hop. Turning a natural-language
request ("show me what Ana posted") into that resolved URI is not
something NRP or the kernel does today; no natural-language resolution
layer is shipped. The addressable, meaning-first graph such a layer
would sit on top of is real now. The layer itself is direction, not a
current mechanism — stated plainly rather than implied.