Statement

A user-centric system inverts the point resolution starts from. Not 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.

Definitions

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.

Structural Basis

What makes this a structural claim, not only a preference, is already verified:

The Graph, Not the Menu

me
 ├─ family.photos
 ├─ family.messages
 ├─ work.neurons_me
 ├─ work.github
 ├─ music.playlists
 └─ ai.claude

Each 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.

Two Architectures

Platform-centric.me-centric
Containing contextthe platformthe user's graph
Addressingassigned by the appdeclared by the user, free-form
Optimized forretention — time inside a boundaryresolution — completing a request
What a platform isa destinationa reachable node

Scope — What's Not Yet Resolved

NRP resolves an already-formed 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.