🗺️ Core Architecture Specifications & Research Tracks
The Native Web Federation oversees the multi-phase standardization, conformance test engineering, and architectural hardening of the following critical base infrastructures:
Phase 1: Remote Module Definition (RMD) Foundational Pattern
-
Status: Active Standardization
-
Scope: Establishing the formal structural mechanics of how modern browser runtimes natively isolate, fetch, and project decoupled layout components. This specification provides a standardized, zero-compilation architectural pattern for native browser includes and partials without third-party frameworks.
Phase 2: The Native Microfrontend (MFE) Protocol
-
Status: Architectural Scoping
-
Scope: Divided into two foundational infrastructure execution tracks:
-
Same-Domain Orchestration: Utilizing the baseline RMD pattern in tandem with native Web Components and Custom Elements to achieve a low-overhead MFE architecture completely devoid of heavy vendor frameworks.
-
Cross-Domain Orchestration: Evaluating structural Cross-Origin Resource Sharing (CORS) behavior under a decoupled routing research bed to benchmark native multi-domain MFE limitations and establish the baseline security profiles required for future Phase 7 hardening.
-
Phase 3: Native Data Sovereignty
-
Status: Protocol Design
-
Scope: Leveraging cross-domain routing mechanics paired with an additional pattern using Import Attributes of type JSON on a standardized
index.jsonfile at a conventional location. This composable system allows external users to securely project and render their own content onto a consumer site natively. -
Application: This model opens up low-friction adoption vectors without any servers involved. Existing major social media platforms and web services can leverage this to seamlessly allow users to supply a personal repository link or REST endpoint. The consumer site can then write content directly back to that user's personal host via a simplified user interface, bypassing the need for end-users to possess manual programming knowledge.
Phase 4: Cross-Domain Federated Sites
-
Status: Research and Validation
-
Scope: Realizing Ward Cunningham’s vision for the Smallest Federated Wiki across general application environments. This protocol defines how independent websites can point back to one another, mirror code layers, and selectively swap components or preferred edits across distinct domain lines, laying the foundation for entirely new web infrastructure industries.
Phase 5: The Content Domain Name Server (CDNS)
-
Status: Conceptual Modeling
-
Scope: Blueprinting a structural hybrid infrastructure sitting between traditional Content Delivery Networks (CDNs) and Domain Name Servers (DNS) specifically for modular components. The CDNS specification defines patterns for stable, immutable URLs that inspect request parameters to dynamically serve localized text, internationalization directives, and geographically optimized assets natively.
Phase 6: The Open WebSDK Framework
-
Status: Drafting & Extensibility Layering
-
Scope: Engineering the world's most extensible, fully browser-standard Software Development Kit. Built entirely on vanilla browser primitives, this framework facilitates rapid consumer adoption while maintaining strict flexibility, allowing legacy proprietary setups to incrementally migrate to native performance baselines.
Phase 7: W3C Specification & Native Browser Engineering
-
Status: Visionary & Standards Body Integration
-
Scope: Transitioning the verified specification pipeline into formal international web standards tracking. The operational goal for this phase involves forking the Chromium engine to implement and compile a custom, native Blink rendering element inside the browser core, establishing a permanent, hardcoded runtime baseline for the pattern.