Unclassified

Microfrontends (Three Invokable Surfaces)


Microfrontends (Three Invokable Surfaces)

The Platform Control Board is implemented as a microfrontend — one of three invokable surfaces:

#PackageRole
1@integratewise/auth-connectors-mfeUniversal identity, grants, discovery, connector tray
2@integratewise/auth-onboarding-mfeLogin / signup / onboarding flow
3@integratewise/platform-mfePlatform Control Board — all kernel features

Host detection architecture

The host is identified during onboarding, not selected at runtime:

  1. User arrives from Host X (ChatGPT, Claude, Web, Platform, MCP Client, etc.)
  2. One Auth establishes identity + host context
  3. Discovery Engine runs against Host X
  4. Connector tray = projections from Host X
  5. User sees only what Host X provides

Platform Kernel views (implemented in platform-mfe)

ViewComponentDescription
Spine FabricSpineFabricViewOperational DB fabric: cache ↔ canonical ↔ KV ↔ R2 ↔ Redis ↔ AI Search ↔ Omni Router
Spine NetworkSpineNetworkViewVisual graph of Spine nodes and edges
OODA PipelineOODAPipelineViewObserve → Orient → Decide → Act pipeline
Agent StatusAgentStatusView5 bounded agents + Co-worker status
Memory QueuesMemoryQueuesViewMemory Queue + Approval Queue + Promotion Queue + 10 memory categories
Tool CapabilityToolCapabilityMatrixViewHost-connected tools → capabilities → workspace projection
ConfigurationConfigurationManagerViewTenant, schema, connector, projection configuration
ActivationActivationManagerViewActivation status, blockers, go-live checklist

Design tokens

All MFEs use packages/*/src/lib/design-tokens.ts as the single source of truth. Derived from apps/web/src/integratewise-figma-tokens.json.

See docs/architecture/MICROFRONTENDS.md for complete specification.