A developer has published a comprehensive framework called "Semantic Taxonomy – Official Path Rules" designed to organize routes within applications using a ".me" namespace system. The framework establishes clear boundaries between canonical user data, operational state, and visual interface elements to prevent what the author calls "contamination" between different types of application data.
The framework, published by developer Sui Gn on DEV Community, introduces a structured approach to organizing application routes that separates concerns into distinct categories. At its core, the system uses namespace ownership to define meaning and establishes strict rules about where different types of data can be stored and accessed.
The taxonomy divides routes into two primary categories: canonical and local. Canonical routes, including profile.* and auth.*, contain user data that must be publishable and resolvable by external systems like cleaker.me. Local routes, such as ui.* and runtime.*, exist only within the current device or session and handle temporary operational and visual state.
Writing and Reading Restrictions
The framework implements strict access controls to maintain data integrity. GUI components are forbidden from writing to canonical paths like profile.* or auth.* unless an explicit allowCanonicalWrite: true flag is used. This prevents user interface elements from inadvertently modifying persistent user data.
Meanwhile, local paths like ui.cleaker.* and runtime.cleaker.* allow unrestricted writes for managing application state. Identity session data should only be modified during authentication events like login and logout.
For reading operations, the framework mandates that identity components must read from canonical paths (profile.* and auth.*), while view state components should read from ui.cleaker.* and operational state from runtime.cleaker.*.
Preventing Data Contamination
The documentation emphasizes preventing "contamination" between different data types. Correct implementation would store a username as me.profile.username = "jabellae" and authentication timestamps as me.auth.claimed_at = 1744300000000.
Incorrect implementations that the framework aims to prevent include storing visual state like modalOpen within profile data or mixing device-specific information with user identity data.
The author describes this document as "the bible for the Cleaker refactor and all future components," suggesting it will guide ongoing development of what appears to be a larger application or platform project.
Analysis
Why This Matters
- Demonstrates growing awareness among developers about the importance of data architecture and separation of concerns in application design
- Provides a concrete framework that other developers could adapt for their own projects to improve code organization
- Reflects broader industry trends toward more structured approaches to managing application state and user data
Background
Software architecture has long struggled with the challenge of organizing different types of data within applications. Traditional approaches often led to "spaghetti code" where user interface elements, business logic, and data storage became intertwined, making applications difficult to maintain and debug.
The concept of "separation of concerns" has been a fundamental principle in software engineering for decades, dating back to early structured programming methodologies. Modern frameworks like React, Vue, and Angular have incorporated these principles through component-based architectures and state management patterns.
Recent years have seen increased focus on data sovereignty and user control over personal information, particularly following privacy regulations like GDPR. This has pushed developers to think more carefully about how user data is stored, accessed, and transmitted between systems.
Key Perspectives
Software Architects: View this type of framework as essential for maintaining clean, scalable codebases and preventing technical debt that can accumulate when data boundaries are unclear.
Frontend Developers: May appreciate the clear guidelines for where different types of data should be accessed, though some might find the restrictions limiting for rapid prototyping or simple applications.
Privacy Advocates: Could see value in the clear separation between canonical user data and local application state, as it makes user data boundaries more explicit and potentially easier to audit.
What to Watch
- Whether this framework gains adoption beyond the author's own "Cleaker" project
- How the developer community responds to the specific rules and restrictions proposed
- Whether similar taxonomies emerge from other development teams facing similar architectural challenges