Skip to main content

FDC3 Intent Interoperability on C3

State 014 layers FDC3 context and intent interoperability onto the C3 TraderX runtime and adds a local Sail sidecar demo environment.

  • Inherits architectural baseline from: 012-platform-convergence-c3
  • Generated from: system/architecture.model.json
  • Canonical flows: ../001-baseline-uncontainerized-parity/system/end-to-end-flows.md

Entry Points​

  • traderx-ui: http://localhost:8080
  • mini-traderx: http://localhost:8080/mini-traderx
  • sail-ui: http://localhost:8090

Architecture Diagram​

Node Catalog​

NodeKindLabelNotes
traderactorTraderUser interacting with TraderX blotters and tickets.
traderxUiserviceTraderX Angular UITrade/order/position views plus FDC3 integration adapter.
traderxIngressgatewayTraderX IngressNGINX ingress for TraderX UI/API traffic.
traderxDirectorycomponentTraderX App DirectoryTraderX-owned FDC3 App Directory source for core TraderX, Mini TraderX, and TraderX Intent Launcher.
sailSidecarserviceSail SidecarLocal Sail desktop-agent runtime hosted outside TraderX ingress.
sailDirectorycomponentAggregated App DirectoriesSail-consumed directory sources for TraderX-owned apps, TradingView/Pricer demos, and FINOS conformance apps.
demoAppsserviceDemo FDC3 AppsMini TraderX, local TraderX Intent Launcher, frameable TradingView/Pricer apps, and FINOS conformance apps participating in ticker/account workflows.
orderApiserviceOrder Matcher APIOrder listing and lifecycle endpoints used by order flows.
tradeApiserviceTrade Service APITrade creation/query endpoints used by trade ticket flows.
positionApiservicePosition Service APIPosition/blotter data source for symbol-selected rows.
natsserviceNATS BrokerRealtime ticker and lifecycle updates via websocket gateway.

State Notes​

  • FDC3 integration is additive and frontend-scoped.
  • No backend API or schema changes are required for core interoperability behavior.
  • Sail sidecar is intentionally outside TraderX ingress to keep concerns separated.
  • TraderX-hosted App Directory metadata is intentionally behind TraderX ingress because it describes TraderX-owned apps and routes.
  • Sail should aggregate app-directory sources rather than owning every app record locally.
  • Degraded mode preserves baseline workflows when DesktopAgent is unavailable.