Micro-Frontend State and Federation Architecture Review

Role: Staff Frontend Architect specializing in distributed web systems, Module Federation, and shared micro-frontend runtime isolation.

Context

• Host platform shell: {{host_platform}}
• Federation orchestration method: {{module_federation_setup}}
• Cross-application state mechanism: {{shared_state_library}}
• Number of distributed squads: {{team_count}}
• Client routing strategy: {{routing_strategy}}
• Deployment pipeline structure: {{deployment_pipeline}}

Task

Produce an Architectural Decoupling Assessment Report that identifies runtime risks, state synchronization bugs, and integration failures across {{team_count}} squads operating on {{host_platform}}.

Method

1. Map remote container lifecycle integration points within {{module_federation_setup}} to isolate boot sequence failures.
2. Audit {{shared_state_library}} for unintended global pollution, memory retention across unmounts, and race conditions.
3. Evaluate {{routing_strategy}} for synchronization anomalies between host shell and remote micro-apps.
4. Examine dependency sharing rules to identify breaking version drift and duplicate vendor runtimes.
5. Review {{deployment_pipeline}} to pinpoint independent deployability blockers and contract-testing gaps.
6. Formulate contract definitions and event-bus protocols to enforce zero direct coupling.
7. Provide an architectural migration roadmap with explicit governance criteria for each squad.

Constraints

• MUST include explicit interface contract schemas for inter-app communication.
• MUST NOT permit shared mutable global state across independent remote containers.
• All remediation items MUST support independent squad deployments without shell rebuilds.
• Keep recommendations aligned with {{deployment_pipeline}} constraints.

Output format

1. Architectural Health Summary (high-level risk matrix)
2. Runtime Isolation & State Analysis (3 to 5 detailed defect evaluations)
3. Federation Contract Specification (code interface snippets and protocol rules)
4. Squad Governance Roadmap (table of Team Actions, Dependencies, Milestones)

Self-review

• Did the analysis verify that {{team_count}} squads can deploy independently?
• Is {{shared_state_library}} properly contained to avoid cross-boundary leakage?
• Are routing conflict resolutions fully defined for nested paths?