Semantic Addressing - Semantic Data Resolution.

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" (Brittle) // If the server changes or the file moves, this breaks. const response = await fetch(' https://v1.host' ); // SEMANTIC: Resolving the "What" (Resilient) // 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 •