Skip to main content

Packages

How the Sail workspaces relate. The same diagram appears in the repository README; this page is the docs entry point for per-package guides.

PackageRole
@finos/sail-headless-agentFDC3 engine — 2.2 / 3.0 DACP handlers (FDC3ServerInstance)
@finos/sail-browser-agentBrowser host for that engine — WCP, MessagePorts, host contracts
@finos/sail-platformWorkspaces, layouts, pluggable storage (no FDC3 dependency)
@finos/sail-themeShared brand tokens and assets
@finos/sail-envShared host URL/env helpers (appId, directory, auto-resolve, max FDC3 version)
@finos/sail-financeExample shell — finance-specific workspace
@finos/sail-oneExample shell — domain-neutral tab-and-grid canvas
@finos/fdc3-sail-webPrevious Socket.IO Sail UI (still runnable; shares the headless engine)
@finos/sail-conformance-harnessPlaywright runner for the FINOS FDC3 conformance toolbox against product hosts

Two different test signals​

Do not conflate these:

SignalWhat it testsWhere it lives
Cucumber BDDEngine / DACP messaging (MockTransport) for wire 2.2 and 3.0sail-headless-agent BDD inventory
FINOS conformance toolboxLive browser / WCP behaviour of product hostssail-conformance-harness — matrix over sail-one, sail-finance, and sail-v2-web (@finos/fdc3-sail-web)