# Namespaced Registries Let Extensions Share Assets Without Sharing Ownership ## Claim A shared registry with provider namespaces lets independent extensions reuse one asset interface without colliding over common names. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Applies to WordPress icon collections registered for PHP, REST, and editor use. - Namespaces prevent identifier collision; they don't guarantee visual consistency or accessibility. - Registry consumers should depend on the public interface rather than a provider's storage details. ## Evidence [[3. Resources/Readwise/Books/Atomic ideas — Registering and rendering SVG icons in WordPress 7.1]] describes a common icon registry whose namespaced collections can expose the same icon names across independent providers. ## Links - [[A Rule-Based DSL Over Object Metadata Is the Control Plane]] — parallels: shared metadata becomes the coordination surface across implementations. - [[Portability Is Proven by a Second Implementer Not by Design Intent]] — applies-in: independent icon providers test whether the registry is truly shared. - [[Structured AI Edits Need Platform-Native Validation]] — supports: common platform interfaces preserve invariants better than direct storage assumptions. - [[3. Resources/MOCs/Open Source Governance MOC]] — applies-in: the MOC lists this note under Synthesis additions (2026-08-11 — shared extension registries).