AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
frontendcritical PriorityID: module-federation-2-strict-singleton-reconciliation-barrier

Strict Singleton Version Reconciliation and Split-Brain Prevention Barrier in Module Federation 2.0

Enforces strict singleton version reconciliation, explicit shared scope initialization barriers, and fail-fast failover strategies across Module Federation 2.0 micro-frontends. Prevents split-brain state mutations, duplicate event bus instances, and runtime React/Zustand context degradation caused by loose semver fallbacks or uncoordinated remotes. Mandates runtime assertions and deterministic host-driven container registration.

Prohibited Anti-Pattern: Uncoordinated Eager Imports and Loose Semver Sharing Permitting Multi-Instance Context Partitioning

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Strict Singleton Version Reconciliation and Split-Brain Prevention Barrier in Module Federation 2.0 - Enforces strict singleton version reconciliation, explicit shared scope initialization barriers, and fail-fast failover strategies across Module Federation 2.0 micro-frontends. Prevents split-brain state mutations, duplicate event bus instances, and runtime React/Zustand context degradation caused by loose semver fallbacks or uncoordinated remotes. Mandates runtime assertions and deterministic host-driven container registration.
globs: **/*module-federation.config.{ts,js}, **/rspack.config.{ts,js}, **/webpack.config.{ts,js}, src/bootstrap.{ts,tsx}, src/init-federation.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/module-federation-2-strict-singleton-reconciliation-barrier"
---

# Strict Singleton Version Reconciliation and Split-Brain Prevention Barrier in Module Federation 2.0

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Uncoordinated Eager Imports and Loose Semver Sharing Permitting Multi-Instance Context Partitioning

## System Constraints
You are a Principal Software Architect enforcing Module Federation 2.0 strict singleton reconciliation. Mandate explicit singleton definitions, strictVersion barriers, runtime initialization gates, and fail-fast assertions to eliminate split-brain micro-frontend runtime contexts.

## Strict Guidelines
- Engineers MUST ALWAYS configure reactive cores (e.g., react, react-dom), state singletons (e.g., Zustand stores, Redux orchestrators), and telemetry clients with 'singleton: true', 'strictVersion: true', and a deterministic 'requiredVersion' constraint.
- Engineers MUST NOT permit 'singleton: true' without setting 'strictVersion: true' on shared packages that maintain shared memory or global context references, avoiding silent multi-instance fallback forks.
- Hosts MUST enforce an asynchronous initialization barrier (Dynamic Remote Loading with shared scope validation via initSharing) prior to bootstrapping the host UI tree.
- Remotes MUST NEVER declare different major/minor versions of stateful singleton primitives without an explicit compatibility adapter or container-level version gate.
- Engineers MUST implement a runtime singleton assertion barrier using Symbol-keyed global markers or Object.freeze barriers to fail-fast during local bootstrap if a duplicated module instance is detected.

## Bad vs Good Implementations
### Module Federation Shared Config - Permissive Fallback vs. Strict Singleton Barrier

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Without 'strictVersion: true' and an explicit 'requiredVersion', Module Federation silently falls back to spawning an isolated bundle instance when version ranges deviate. This instantiates duplicate React runtime and Zustand state stores across remotes, breaking reactive dispatch.
```typescript
import { ModuleFederationPlugin } from '@module-federation/enhanced/rspack';

export default {
  plugins: [
    new ModuleFederationPlugin({
      name: 'remote_catalog',
      filename: 'remoteEntry.js',
      // Anti-pattern: Loose sharing without strictVersion causes duplicated instances
      // when versions mismatch slightly, leading to split-brain Zustand/React context.
      shared: {
        react: { singleton: true },
        'react-dom': { singleton: true },
        zustand: { singleton: true }
      }
    })
  ]
};
```

#### Production Standard (Correct)
> **Standard**: Declaring 'strictVersion: true' alongside strict 'requiredVersion' parameters forces the container to throw a deterministic compile-time and runtime error if incompatible versions collide, preventing silent state isolation.
```typescript
import { ModuleFederationPlugin } from '@module-federation/enhanced/rspack';
import deps from './package.json' with { type: 'json' };

export default {
  plugins: [
    new ModuleFederationPlugin({
      name: 'remote_catalog',
      filename: 'remoteEntry.js',
      shared: {
        react: {
          singleton: true,
          strictVersion: true,
          requiredVersion: deps.dependencies.react
        },
        'react-dom': {
          singleton: true,
          strictVersion: true,
          requiredVersion: deps.dependencies['react-dom']
        },
        zustand: {
          singleton: true,
          strictVersion: true,
          requiredVersion: deps.dependencies.zustand
        }
      }
    })
  ]
};
```

### Runtime Singleton Guard and Scope Reification Barrier

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Eagerly rendering without initializing shared federation scope and asserting single-instance identity leads to race conditions where the remote evaluates before the host sets up the global scope, partitioning runtime memory.
```typescript
// Anti-pattern: Eagerly mounting and assuming global state singletons are unified
import React from 'react';
import ReactDOM from 'react-dom/client';
import App from './App';
import { useSharedSessionStore } from './sharedSession';

// Mounts directly without verifying shared container initialization
ReactDOM.createRoot(document.getElementById('root')!).render(<App />);
```

#### Production Standard (Correct)
> **Standard**: Enforces a Symbol-based global initialization gate to ensure that only a single instance of critical stores can execute. Any secondary remote trying to load an out-of-spec store triggers an instant, traceable runtime panic instead of corrupting user state.
```typescript
import React from 'react';
import ReactDOM from 'react-dom/client';

const SINGLETON_KEY = Symbol.for('enterprise.shared.session_store.barrier');

interface GlobalMemoryBarrier {
  [SINGLETON_KEY]?: string;
}

export function assertSingletonIntegrity(instanceId: string): void {
  const globalRef = globalThis as unknown as GlobalMemoryBarrier;
  if (globalRef[SINGLETON_KEY] && globalRef[SINGLETON_KEY] !== instanceId) {
    throw new Error(
      `[ModuleFederation:CollisionDetected] Split-brain singleton collision detected: ` +
      `existing=${globalRef[SINGLETON_KEY]}, incoming=${instanceId}`
    );
  }
  globalRef[SINGLETON_KEY] = instanceId;
}

async function bootstrap(): Promise<void> {
  // Invariant: Verify singleton contract before UI initialization
  assertSingletonIntegrity('v2.4.1-core');
  
  const { default: App } = await import('./App');
  const rootElement = document.getElementById('root');
  if (!rootElement) throw new Error('Root container missing');
  
  ReactDOM.createRoot(rootElement).render(<App />);
}

void bootstrap();
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

Webpack & Rspack AST Inspector MCP
Inspects and audits dynamic federation configuration files and package dependencies across monorepo boundaries.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Module Federation Dependency Matrix Auditor
CLI tool that statically audits semver compatibility for all shared singletons across all host and remote configuration manifests.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Strict Singleton Version Reconciliation and Split-Brain Prevention Barrier in Module Federation 2.0

Strict Singleton Version Reconciliation and Split-Brain Prevention Barrier in Module Federation 2.0 defines an industrial-grade behavioral standard for frontend engineering. Enforces strict singleton version reconciliation, explicit shared scope initialization barriers, and fail-fast failover strategies across Module Federation 2.0 micro-frontends. Prevents split-brain state mutations, duplicate event bus instances, and runtime React/Zustand context degradation caused by loose semver fallbacks or uncoordinated remotes. Mandates runtime assertions and deterministic host-driven container registration. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Uncoordinated Eager Imports and Loose Semver Sharing Permitting Multi-Instance Context Partitioning Without an explicit system instruction file, developers spend hours debugging silent failures.
Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftUncoordinated Eager Imports and Loose Semver Sharing Permitting Multi-Instance Context PartitioningCritical
Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production.
Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture InconsistencyAI assistants produce mixed paradigms across files, creating fragmented codebase conventions.Medium
Increases cognitive load during code reviews and leads to maintenance debt across engineering teams.
Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.
Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Engineers MUST ALWAYS configure reactive cores (e.g., react, react-dom), state singletons (e.g., Zustand stores, Redux orchestrators), and telemetry clients with 'singleton

Engineers MUST ALWAYS configure reactive cores (e.g., react, react-dom), state singletons (e.g., Zustand stores, Redux orchestrators), and telemetry clients with 'singleton: true', 'strictVersion: true', and a deterministic 'requiredVersion' constraint.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Engineers MUST NOT permit 'singleton

Engineers MUST NOT permit 'singleton: true' without setting 'strictVersion: true' on shared packages that maintain shared memory or global context references, avoiding silent multi-instance fallback forks.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Hosts MUST enforce an asynchronous initialization barrier (Dynamic Remote Loading with shared scope validation via initSharing) prior to bootstrapping the host UI tree.

Hosts MUST enforce an asynchronous initialization barrier (Dynamic Remote Loading with shared scope validation via initSharing) prior to bootstrapping the host UI tree.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Remotes MUST NEVER declare different major/minor versions of stateful singleton primitives without an explicit compatibility adapter or container-level version gate.

Remotes MUST NEVER declare different major/minor versions of stateful singleton primitives without an explicit compatibility adapter or container-level version gate.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
5

Engineers MUST implement a runtime singleton assertion barrier using Symbol-keyed global markers or Object.freeze barriers to fail-fast during local bootstrap if a duplicated module instance is detected.

Engineers MUST implement a runtime singleton assertion barrier using Symbol-keyed global markers or Object.freeze barriers to fail-fast during local bootstrap if a duplicated module instance is detected.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Strict Singleton Version Reconciliation and Split-Brain Prevention Barrier in Module Federation 2.0 critical for AI coding assistants?

Enforces strict singleton version reconciliation, explicit shared scope initialization barriers, and fail-fast failover strategies across Module Federation 2.0 micro-frontends. Prevents split-brain state mutations, duplicate event bus instances, and runtime React/Zustand context degradation caused by loose semver fallbacks or uncoordinated remotes. Mandates runtime assertions and deterministic host-driven container registration. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Uncoordinated Eager Imports and Loose Semver Sharing Permitting Multi-Instance Context Partitioning) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related FRONTEND Rules

View all rules →
frontend
119

SolidStart 1.0 Server Functions & Async Boundaries Production Standard

SolidStart 1.0 relies on the Vinxi bundler to split `server$` closures into independent HTTP POST RPC endpoints. Direct lexical closure over client signals within `server$` scopes or failure to demarcate async boundaries with `<Suspense>` causes silent serialization failures, client-bundle secret leaks, and SSR hydration mismatches. Enforcing strict parameter passing, runtime input validation, and Solid async primitives maintains security and fine-grained reactivity across network boundaries.

frontend
119

Astro 5 Actions & Content Layer Production Standard

Enforces strict type safety and architectural correctness for Astro 5 Server Actions and the zero-waterfall Content Layer API. Prevents runtime contract mismatches, hydration mismatches, and unhandled mutation exceptions across dynamic and prerendered boundaries. Failure to follow these patterns leads to silent data fetching waterfalls, build-time cache corruptions, and unhandled server action exceptions.

frontend
51

Nuxt 4 Nitro Server Engine & Shared Directory Production Standard

Nuxt 4 enforces strict boundary segregation between client UI in the app/ directory, backend endpoints in server/, and universal contracts in shared/. Violating cross-boundary isolation or maintaining module-scoped state in Nitro server handlers causes catastrophic cross-request data corruption and hydration mismatches under concurrent production traffic. Architects must enforce request-isolated H3 event contexts, universal serialization schemas, and strict path-alias boundaries.

1 Rule in Stack

Strict