.me - A semantic reactive kernel using natural paths and…
0 reactions
.me - A semantic reactive kernel using natural paths and automatic derivations.
# Core Idea
Instead of traditional key-value stores or complex object graphs, .me treats all data as **natural semantic paths**:
* profile.name http://profile.name
* wallet.balance
* runtime.mesh.surfaces.iphone.battery
* me://jabellae.cleaker.me\[surface:iphone\]/chat/general
The kernel is built around three core principles:
* **Identity is canonical** — There's one source of truth for who you are.
* **Session is volatile** — Login/logout doesn't touch your core identity.
* **Surfaces are plural** — Your Mac, phone, server, etc., are all just "surfaces" of the same .me.
# What makes it different
* **Reactive by default**: Any change to a path automatically notifies subscribers (very fast O(k) resolution).
* **Semantic paths**: You don't get("user.profile.name"), you just ask for profile.name . The kernel understands context, surfaces, and selectors (\[current\], \[\], \[surface:iphone\]).
* **Built-in Mesh awareness**: It knows you're not just running on one device. It can resolve paths across multiple surfaces.
* **.me URI scheme**: You can encode any operation into a scannable QR code (me://jabellae.cleaker.me\[claim:xyz123\]/new-surface).
#technology
# Core Idea
Instead of traditional key-value stores or complex object graphs, .me treats all data as **natural semantic paths**:
* profile.name http://profile.name
* wallet.balance
* runtime.mesh.surfaces.iphone.battery
* me://jabellae.cleaker.me\[surface:iphone\]/chat/general
The kernel is built around three core principles:
* **Identity is canonical** — There's one source of truth for who you are.
* **Session is volatile** — Login/logout doesn't touch your core identity.
* **Surfaces are plural** — Your Mac, phone, server, etc., are all just "surfaces" of the same .me.
# What makes it different
* **Reactive by default**: Any change to a path automatically notifies subscribers (very fast O(k) resolution).
* **Semantic paths**: You don't get("user.profile.name"), you just ask for profile.name . The kernel understands context, surfaces, and selectors (\[current\], \[\], \[surface:iphone\]).
* **Built-in Mesh awareness**: It knows you're not just running on one device. It can resolve paths across multiple surfaces.
* **.me URI scheme**: You can encode any operation into a scannable QR code (me://jabellae.cleaker.me\[claim:xyz123\]/new-surface).
#technology
| 1,000 mlx | |
| 2 | |
| 0 |