Concept
Update TraderX's FDC3 implementation to exercise FDC3 v3 ahead of GA, using the FDC3 3.0.0-alpha.2 client package and the Sail sail-v3-beta branch as the demo/runtime target.
This can run as a hack day track even while FDC3 v3 is still pre-release: the goal is to validate the migration early, identify Sail/Web Agent gaps, and make TraderX a useful reference/demo app for v3 interoperability.
Prototype Direction
- Move TraderX frontend integration to official
@finos/fdc3@3.0.0-alpha.2 and getAgent() semantics.
- Stand up a local Sail v3 beta sidecar for a repeatable demo workspace.
- Seed AppD records for TraderX, Mini TraderX, TraderX Intent Launcher, TradingView-style demo apps, Pricer, and FINOS conformance apps.
- Use canonical
fdc3.instrument broadcasts for security selection.
- Add TraderX-specific
traderx.account context for account selection between TraderX windows.
- Add a standalone
/mini-traderx companion window that listens for global account/instrument context, shows current price, and displays a live position blotter filtered to the selected instrument.
- Keep Mini TraderX scoped to account, instrument, price, and positions only; trade/order ticket launching remains in main TraderX and the separate Intent Launcher.
- Verify real Sail delivery of broadcasts across TraderX, Mini TraderX, launcher, TradingView, and Pricer.
Demo Ideas
- Open a Sail v3 workspace with main TraderX, Mini TraderX, TradingView Chart/Market Data, Pricer, and Intent Launcher already laid out.
- Select a position/security in main TraderX and watch Mini TraderX plus external apps pivot through
fdc3.instrument.
- Change selected account in main TraderX and watch Mini TraderX pivot through
traderx.account.
- Use Intent Launcher to raise
TraderX.CreateTradeTicket / TraderX.CreateOrderTicket for the current instrument.
- Show fallback/local-only behavior when no FDC3 agent is present.
- Capture conformance/regression gaps for Sail v3 beta and FDC3 alpha.
Current Prototype Notes
- State 014 is the target state for this work.
- FDC3 package target:
@finos/fdc3@3.0.0-alpha.2.
- Sail target:
sail-v3-beta branch.
- Keep TraderX payloads canonical for
fdc3.instrument.id.ticker; isolate Sail/demo compatibility shims in state generation/bootstrap code.
- Account context should only carry account identity/display name, not balances, positions, or P&L.
Acceptance Criteria
Concept
Update TraderX's FDC3 implementation to exercise FDC3 v3 ahead of GA, using the FDC3
3.0.0-alpha.2client package and the Sailsail-v3-betabranch as the demo/runtime target.This can run as a hack day track even while FDC3 v3 is still pre-release: the goal is to validate the migration early, identify Sail/Web Agent gaps, and make TraderX a useful reference/demo app for v3 interoperability.
Prototype Direction
@finos/fdc3@3.0.0-alpha.2andgetAgent()semantics.fdc3.instrumentbroadcasts for security selection.traderx.accountcontext for account selection between TraderX windows./mini-traderxcompanion window that listens for global account/instrument context, shows current price, and displays a live position blotter filtered to the selected instrument.Demo Ideas
fdc3.instrument.traderx.account.TraderX.CreateTradeTicket/TraderX.CreateOrderTicketfor the current instrument.Current Prototype Notes
@finos/fdc3@3.0.0-alpha.2.sail-v3-betabranch.fdc3.instrument.id.ticker; isolate Sail/demo compatibility shims in state generation/bootstrap code.Acceptance Criteria
fdc3.instrument.traderx.account./mini-traderxand renders live account/instrument-scoped positions.