Skip to content

FDC3 Sail Project Meeting - 2026 October 12th #384

Closed
Closed
FDC3 Sail Project Meeting - 2026 October 12th#384
Labels
meetingProject meeting agenda / notes

Description

@SeeWhatsOn
SeeWhatsOn
opened on Oct 12, 2026

Date & Time

2026 October 12th — 14:00 UTC

Zoom Details:

Register for the meeting and get an invite sent to your calendar here:
https://zoom-lfx.platform.linuxfoundation.org/meeting/95252800112?password=90638454-991c-4ab0-8aed-791fc372623c&invite=true

Join Zoom Meeting:
https://zoom-lfx.platform.linuxfoundation.org/meeting/95252800112?password=90638454-991c-4ab0-8aed-791fc372623c

Meeting ID: 95252800112
Meeting Passcode: 001816
Join via Phone: https://zoom.us/u/alwnPIaVT

Meeting Notices

  • FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

  • All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

  • FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact legal@finos.org with any questions.

  • FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Tracking Attendance

Those logged in using the LF Meetings will be automatically tracked.

Purpose

The Sail call is where people see what's new, try it, and shape what comes next. Maintainer housekeeping happens async on GitHub.

Agenda

Target: 40 minutes total.

Discussion question (comment before the meeting)

Before the call, please comment on this issue: what would stop you using Sail V3, and what should we test first? Even a couple of lines helps shape the discussion.

Async — please comment on the issue/PR, not discussed in the call

Action Items

Meeting Minutes

Attendees: Chris Watson (@SeeWhatsOn), Rob Moffat (@robmoffat), Kris West (@kriswest), Kryspin Ziemski (@kziemski), Patrick O'Neill (@patrickboneill), Youssef Qteishat, Jamil Ahmad (SavaNet), Kallal Mukherjee

Recap

The meeting focused on the development and deployment strategy for FDC3 Sail. Kryspin proposed a draft PR to make agent skills distributable as npm packages, a technique used by Vercel, to separate consumable skills from development skills. Patrick shared feedback from road testing the V3 branch: it looked great, with minor UX issues and room for a simple search box on the App Directory page. The group discussed how different organisations want to consume Sail, with Chris highlighting the need for both a friendly UI for beginners and a composable npm package for integrating into existing infrastructure. Youssef asked whether Sail was primarily for enterprise use, and Jamil shared his organisation's needs around onboarding, App Directory hosting and deployment within their existing web infrastructure. Rob and Chris presented their work on Sail V3: a componentised architecture with a headless desktop agent and multiple UI options (#341), plus Rob's PR on top of it (#396) adding FDC3 2.2 and 3.0 conformance. The conversation also covered the value of a server-side agent for multi-device sessions, and a plugin or middleware system for telemetry, access control and permissions. Kris confirmed the FDC3 conformance framework version 3.0 has been published.

Discussion

Agent skills as npm packages

  • Kryspin will open a draft PR that separates consumable skills from development skills, distributing them as npm packages (similar to Vercel's approach).
  • A deployment skill would scan node_modules for versioned skills meant for consumption.
  • Rob approved the plan. The PR stays in draft until V3 is released.

App Directory and V3 feedback

  • Patrick road tested the V3 branch. Minor UX issues found; a simple search box on the App Directory page would help.
  • Chris noted there are two UIs in play (Sail One and FDC3 Finance), and Kris is exploring how to embed a desktop agent into existing UIs.
  • Sail has moved from an Electron app to a web-based one, with an npm package as a likely next step.

How people want to consume Sail

  • Chris: an introductory UI for people new to FDC3, plus the ability to plug Sail into existing systems for specialist projects.
  • Patrick: a wizard for generating App Directories to cut onboarding friction.
  • Youssef: confirmed the focus is enterprise use, not personal use.
  • Kryspin: proposed a Tauri back end for wider distribution than Electron, including possible mobile support, while keeping React and other UI frameworks.
  • Kris: Electron deployment is being deprecated in V3 in favour of the web, due to maintenance cost. Componentisation means different UIs can sit over the same back end, including a new Dockview-based UI that could be contributed back.
  • Jamil: evaluating application experience, App Directory set-up and deployment. Their Angular product runs on a subdomain; asked whether Sail needs a subdomain or subdirectory.
  • Rob: a hosted Sail would give easy access to FDC3 learning materials and a place to demonstrate AI governance.

Sail V3 structure (#341 and #396)

  • Chris presented the V3 monorepo: independent components, including a desktop agent that runs in the browser and works with different UIs.
  • Rob's Pluggable Sail Prototype #396 builds on Rewrite Sail as the v3 browser Desktop Agent. #341: FDC3 2.2 and 3.0 conformance, published example apps, and a test matrix across Sail versions and UIs.
  • The 637 touched files are mostly package renames and refactoring, adding packages such as Sail Conformance Harness and Sail Headless Agent.
  • Chris and Rob will go through the files in detail, covering dependency management, duplication between UIs, the server-side implementation and scalability.

Deployment options

  • Tension between a flexible toolbox of components and keeping it simple.
  • The Sail Browser Agent holds the browser-dependent parts. The core FDC3 routing runs in the headless agent, which can run anywhere.
  • The server-side version runs in Node.js on the FINOS cloud and supports multi-tenancy. Future uses include connecting Java apps and letting multiple devices join the same session.

Bridging and plugins

  • Youssef suggested a Slack bot rather than a mobile client. Kris explained the WebSocket-based bridging and Symphony's earlier FDC3 actions in chat messages.
  • Plugin use cases: telemetry, translation, access control, permissions. Rob asked for these to be documented and noted permission requests may need to be core rather than a plugin.

Activity

  1. SeeWhatsOn
    added
    meetingProject meeting agenda / notes
    on Oct 12, 2026
  2. github-project-automation
    added this to FDC3-Sailon Oct 12, 2026

  3. robmoffat commented on Oct 12, 2026

    @robmoffat
    robmoffat
    on Oct 12, 2026
    Member

    Round-the-Room Uses

    @SeeWhatsOn - Some introductory UI for people who've never used FDC3 before. Has seen customers wanting to embed this into their existing apps. Posits that another firm is a good example of this. Intent Resolver, Channel Management - this should all be hook-able.

    Patrick - Wizard for generating the app directory? His firm are quite advanced in FDC3, but wants to make it easier. Would like ti to be easier for people to get up and running with Sail. Gets called in to help when asked to get it running - where are the files located etc.

    Youssef - agrees with Patrick & Chris - features for beginners to help speed up onboarding within an enterprise setting.

    Kryspin - having FDC3 as a component architecture and then using it as the hosting layer for a reference architecture. Has been considering a Tauri back-end, which would allow a wider distribution than having the electron hosting approach. Needs a common layer for a personal suite of financial services deployments. Interested in Native deployment.

    Kris - Componentisation of Sail, different front-ends. Call Centre use case. Prescribed layouts, rather than user-customisable ones.

    Jamil - No FDC3 experience, so a fresh start - how easy is it to get started. Hosting. Deployment. their angular product has a subdomain - do they need it to work somewhere else?

    Kallal - permanently muted.

    Rob - 1. Learning materials. AI Governance.

  4. robmoffat commented on Oct 12, 2026

    @robmoffat
    robmoffat
    on Oct 12, 2026
    Member

    Pluggable

    • Permissions / User Requests
    • Middleware
    • Telemetry
    • Extra Browser Chrome
    • Auditing
    • MCP Apps ??
    • Extensions
  5. SeeWhatsOn
    closed this as completedon Oct 25, 2026
  6. github-project-automation
    moved this from Backlog to Done in FDC3-Sailon Oct 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    meetingProject meeting agenda / notes

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions