Architecture consolidation is ready to become runtime enforcement.

Evidence

Consolidation reports classify duplicate surfaces as primary, supporting, archive, legacy, or hidden internal.

Risk

Legacy pages still exist physically and require continued quarantine discipline.

Next Step

Keep supporting routes visible only through secondary navigation and future archive policies.

Evidence

docs/EEOS_PRIMARY_MODULE_MAP.md defines 24 official primary modules with purpose, owner, dependencies, route, status, audience, and integration requirement.

Risk

The map is authoritative documentation but not yet a runtime registry.

Next Step

Convert the Primary Module Map into Kernel registry enforcement during Phase 2B.

Evidence

Simulation Engine is the official primary module; Scenario Simulator, Decision Simulator, Executive Simulation Lab, and Intelligence Simulator are supporting views.

Risk

Supporting simulation pages can drift if future work updates them independently.

Next Step

Route future simulation logic through the official Simulation Engine data contract.

Evidence

Opportunity Engine is the official primary module; Opportunity Radar, Opportunity Graph, Opportunity Intelligence, and Executive Opportunity Engine are supporting views.

Risk

Opportunity Graph still overlaps with Knowledge Graph and must remain a view, not a separate canonical graph.

Next Step

Keep opportunity discovery downstream of Knowledge Graph and Executive Intelligence Core.

Evidence

Mission Control remains the executive home screen; CEO Daily Briefing, Executive Briefing Center, Executive Command Center, CEO Command Center, and Executive Consciousness are supporting systems.

Risk

Briefing pages may continue to feel like competing home screens if navigation expands again.

Next Step

Keep Mission Control as the only primary executive home surface.

Evidence

Executive Intelligence Core is the primary reasoning layer; Reasoning, Wisdom, Consciousness, Advisory Board, Trust, Explainability, and Confidence feed the Core.

Risk

Supporting reasoning engines need runtime prevention against independent recommendations.

Next Step

Enforce Recommendation Contract routing through Executive Intelligence Core.

Evidence

Knowledge Graph is the primary graph; Executive Knowledge Graph, Opportunity Graph, and Executive Decision Graph are supporting graph views.

Risk

A shared graph data contract is documented but not enforced at write time.

Next Step

Create Phase 2B graph write gates through Kernel and Event Contract validation.

Evidence

Business Memory stores lessons, Executive Decision Ledger stores decisions, and Executive Timeline displays chronology.

Risk

Memory and ledger persistence is not immutable in production yet.

Next Step

Make Decision Ledger append-only and route memory writes through the Event Contract.

Evidence

docs/LEGACY_QUARANTINE_REPORT.md marks legacy CRM and direct integration artifacts as quarantined and blocked from external connection paths.

Risk

Legacy route and files remain present for reference, so enforcement must prevent direct use.

Next Step

Add runtime guards so legacy integration artifacts cannot bypass Plugin Gateway.

Evidence

Primary navigation groups were reduced to Mission Control, Intelligence, Business Apps, Strategy, Security, Platform, Vault, and Founder.

Risk

New internal pages can gradually re-clutter the experience if not assigned to existing groups.

Next Step

Require every new page to declare primary/supporting/internal navigation status.

Evidence

src/core/contracts/recommendation-contract.ts and docs/RECOMMENDATION_CONTRACT.md define the official recommendation structure.

Risk

Existing mock recommendation data is only partially migrated.

Next Step

Use Phase 2B enforcement to validate every recommendation packet at runtime.

Evidence

src/core/contracts/event-contract.ts and docs/EVENT_CONTRACT.md define the official event structure and supported event types.

Risk

Future signal producers must be prevented from emitting non-contract events.

Next Step

Add Kernel event validation before any event reaches Business DNA or Executive Intelligence Core.

Evidence

docs/RUNTIME_ENFORCEMENT_PLAN.md defines production gates for Kernel, Firewalls, Sentinel, permissions, tenant boundaries, plugins, audit, action approval, ledger immutability, secrets, and environments.

Risk

The plan is not implementation; enforcement still must be built.

Next Step

Use the plan as the Phase 2B engineering backlog.

Evidence

/integration-readiness-matrix and docs/INTEGRATION_READINESS_MATRIX.md score planned integrations against required gates and keep every integration Not Live.

Risk

Readiness scores are mock-only and not connected to automated checks.

Next Step

Connect future scores to runtime gate results before controlled integration pilots.