File System is the wrong Source of Truth.
Most systems still bind data to location:
/projects/app/config.json
Here, meaning is inferred from structure.
Move the file → break assumptions.
TRADITIONAL: Navigating the "Where"
If the server changes or the file moves, this breaks.
const response = await fetch('https://v1.host');
SEMANTIC: Resolving the "What"
Location is abstracted. Cleaker finds the truth regardless of the host.
const theme = await me.jabellae.settings.theme;
A semantic system flips this:
Data is addressed by identity + context + intent, not path.
<namespace>:<operation>/<attribute>
Example (abstract):
user:read/profile.displayName
Core idea
• Paths are positional
• Semantics are referential
You don’t navigate a tree — you resolve a meaning.
What changes technically?
1. Decoupled storage
• Data can live anywhere (FS, DB, distributed)
• Addressing layer resolves meaning → location
2. Stable references
• Refactors don’t break access
• No tight coupling to directory structure
3. First-class relationships
• Data modeled as graphs, not trees
• Composition over nesting
4. Intent-based access
• Queries express what, not where
Minimal model
neurons-me.github.io
Instead of:
/path/to/resource.json
You operate on:
<subject>.<property>
Resolved via:
• namespace
• operation (read/write)
• semantic key
From:
filesystem as source of truth
To:
semantic layer as source of truth
This is not abstraction for convenience — it’s a shift from data organization to data meaning resolution.
:::
Semantic Addressing - suiGn
Top comments (0)