Mappa Core / Experience

Vista sintetica delle relazioni tra repository Experience, servizi Core e moduli trasversali del workspace.

Principio di integrazione

I frontend delle experience parlano sempre con il proprio backend same-origin. I backend orchestrano i servizi Core e riusano package e contratti condivisi dove serve.

Vista per Experience

Experience	Moduli principali	Core coinvolti	Shared e trasversale
funnel-ia-engine	backend, worker, frontend	platform-auth-service, platform-ai-service, platform-payments-service, platform-agent-service, platform-mcp-service	platform-local-stack, @platform/contracts-auth, @platform/contracts-ai, @platform/contracts-payments, @platform/contracts-agent, @platform/observability, @platform/ui
sfdc-external	backend, frontend, shared	platform-auth-service, platform-connectors-service	platform-local-stack, @platform/contracts-auth, @platform/contracts-connectors, @platform/auth-client, @platform/http-client
cs-portal	backend, frontend	platform-auth-service, platform-connectors-service	platform-local-stack, platform-status-service
cs-chat	api, web, shared	platform-auth-service, platform-ai-service, platform-agent-service, platform-mcp-service	platform-local-stack, platform-status-service, @platform/contracts-agent, cs-chat/packages/shared
cs-transacion-manage	api, web, shared	platform-auth-service, platform-payments-service	platform-local-stack, platform-status-service, cs-transacion-manage/packages/shared

Vista per Core

Core	Experience che lo consumano	Ruolo principale
platform-auth-service	funnel-ia-engine, sfdc-external, cs-portal, cs-chat, cs-transacion-manage	Sessione condivisa, provider auth, credenziali locali, risoluzione identita e membership.
platform-ai-service	platform-mcp-service, platform-agent-service, funnel-ia-engine, cs-chat	Boundary AI condiviso con registry provider persistito in Postgres.
platform-payments-service	funnel-ia-engine, cs-transacion-manage, platform-status-service	Boundary pagamenti provider-agnostic per catalogo pricing, checkout, webhook Stripe, record purchase/subscription, stato piano ed eventi normalizzati ai consumer.
platform-connectors-service	sfdc-external, cs-portal, platform-mcp-service	Boundary datasource verso Salesforce con source-based endpoints, raw read-only query, SOSL e operazioni batch.
platform-mcp-service	platform-agent-service, cs-chat, client MCP	Tool MCP controllati per status, auth, AI, connectors e scraper.
platform-agent-service	funnel-ia-engine, cs-chat	Runtime asincrono per agent execution, tool orchestration MCP, validazione output e callback ai prodotti.
platform-scraper-service	Backend/BFF e client MCP interni	Runtime asincrono per crawling web sicuro con callback service-to-service.

Vista operativa trasversale

Modulo	Ruolo
platform-local-stack	Bootstrap locale unico, profili YAML, proxy host-based, infra Docker e log collection.
platform-status-service	Dashboard e API aggregate per stato runtime, viste operations e catalogo prodotti status persistito.
platform-shared-packages	Contratti, client, osservabilita e primitive UI condivise tra repo.

Lettura rapida

• Core espone boundary tecnici riusabili e non deve essere chiamato direttamente dai frontend.
• Experience possiede UI, flussi di dominio e orchestrazione applicativa.
• Trasversale raccoglie stack locale, package shared e contratti riutilizzati tra piu repository.
• Per il dettaglio completo dei moduli resta canonico il catalogo moduli.