FDC3 Use Cases and Workflows Discussion Group

Group overview

Newly rebranded "Use Cases and Workflows" discussion group for FDC3, replacing "Context Data and Intents".

The remit of this discussion group is:

talking about existing or potential financial use-cases
unlocking the power of standardisation
discussing new ways to collaborate either inside the organisation or firm-to-firm
sharing expert insights about how to make the most out of FDC3
and collaborating to shaping the future of financial workflows.

Relevant issue tags

Current open issues that relate to the discussion group:

Specific issues will also be tagged with the labels:

Meeting Date

Thursday 6th November 2025 - 10am (US eastern timezone EST) / 3pm (London, GMT)

Zoom info

Join Zoom Meeting
Meeting ID: 969 4029 4948
Passcode: 636931

Dial-in:

Country	International Dial-in	Toll-free Dial-in
US	+1 929 205 6099 (New York)	877 853 5247
UK	+44 330 088 5830	0800 031 5717
France	+33 1 8699 5831	0 800 940 415
Find your local number	https://zoom.us/u/ad2WVnBzb8

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 [email protected] 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.
A Discussion Group has no direct decision-making power regarding the FDC3 standard - rather it is intended that anything they propose or work on will result in proposals (via Github issues and PRs) for the Standards Working Group participants to consider and vote on for inclusion in the standard.

Participation Requirements

Note: Meeting participants are expected to accept the terms of the FDC3 license (Community Specification License), understand the governance process and have a CLA in place.

Please click the following links at the start of the meeting if you have not done so previously.

View the CSL
View the GOVERNANCE of the Project
Click here to start a PR.
- Edit the page to add your details.
- Hit the save button.
- Click "Create Pull Request".
- Click "Accept" on the EasyCLA dialog in the PR's discussion section.
Click here to send email to become a voting participant on the FDC3 Project

Tracking Attendance

Note: Meeting participants are expected to add a comment to this GitHub issue in order that we can track attendance of FDC3 project meetings. Please do this at the start of the meeting.

Agenda

[x] Convene & roll call, review meeting notices (5mins)
[ ] Review action items from previous meeting (5mins)
- [x] #1679
[x] Exploring MCP-UI and Ai across FDC3 | @novavi (30 mins)
- [x] #1669
[ ] What Role Could FIX Messages Play in FDC3 Data Exchange? (10 mins)
- [ ] Continuation from discussions at #1626 with Jim Kaye
[x] Open floor discussion around FDC3 topics (5 mins)
[x] AOB & Adjourn (5mins)

Minutes

Convene & roll call, notices
- New participants introduced: Meghan (Fidelity), Dmitri (Vexa), Ryan (@rmcneely-interopio), Ash Forgar (Citibank).
Review action items from previous meeting
- No outstanding actions carried over; @mistryvinay noted he still owes prior minutes. Issue #1679 considered complete/closed in practice.
Exploring MCP-UI and AI across FDC3 (owner: @novavi; ref: #1669)
- @novavi opened with context on rapid developments around MCP, Web-MCP, and OpenAI’s SDK for embedding UIs and tool calls within AI chat interfaces. Highlighted potential for dual-direction integration between AI tools and FDC3 intents.
- @kriswest emphasized two tangible workstreams:
  - Add structured LLM/AI metadata fields to the App Directory for describing input/output semantics and natural-language summaries of intents.
  - Publish an “FDC3 + AI examples” reference guide to show patterns for rendering UIs in chat vs. launching full apps from chat contexts.
- @lspiro-Tick42 shared Interop.io’s practical experience integrating AI assistants with FDC3:
  - Their App Directory already includes method and tool descriptors to make apps callable by AI systems in a controlled way.
  - Proposed extending the App Directory schema with clearly defined fields (e.g., toolDescription, inputDescription, outputDescription) that align with MCP-style “tool” declarations.
  - Suggested documenting best practices so vendors can easily adopt a consistent “AI-ready” App Directory entry format.
  - Noted that Interop.io limits exposed intents to those explicitly marked as LLM-safe, ensuring sandbox integrity while still enabling discovery.
- Security & discovery:
  - @SeeWhatsOn raised concerns about avoiding over-exposure of app metadata to external LLMs and emphasized adding “opt-in” flags for LLM discovery.
  - Discussion aligned around a secure-by-default approach: only explicitly marked tools would appear to external AI systems.
- Broader considerations:
  - Discussion touched on Anthropic “skills”, OpenAI “tools”, BPM process flows (Flux Nova), and generic “AI assistant to FDC3 desktop” patterns.
  - @kriswest suggested using GitHub Discussions to continue threads and potentially target demo examples for OSSF London.
- Volunteers:
  - @rmcneely-interopio to collaborate with Juliana (Interop.io) on documenting AI/FDC3 integration learnings.
  - @kriswest offered to help shepherd related spec PRs once issues are opened.
Open floor discussion (FDC3 topics)
- @robmoffat suggested leveraging the growing MCP ecosystem via an adapter layer to bootstrap a public FDC3 example directory.
- @SeeWhatsOn proposed cataloguing current pain points and limitations encountered when combining AI agents with FDC3 to guide prioritization.
- Agreement to document and publish these findings as part of new issues or discussion threads.
AOB & Adjourn
- Slack access via [email protected]; open channel #fdc3.
- Next month’s focus: “What Role Could FIX Messages Play in FDC3 Data Exchange?” (pending Jim Kaye’s availability).

Action Items

[ ] @rmcneely-interopio - Raise an umbrella issue to extend the App Directory with LLM/tool metadata (intent descriptions, I/O semantics, AI-safe discovery flags) and link to #1669.
[ ] @novavi Draft proposal for additions to the FDC3 specification and API overview, outlining how FDC3 should describe AI/LLM integrations and metadata; collaborate with @kriswest for alignment.
[ ] @kriswest - Draft proposal text for new descriptive fields adjacent to intents raised/listened to, plus outline for best-practice guidance.
[ ] @SeeWhatsOn - Draft security/discovery guidance (default opt-in for LLM exposure, scoping, examples of whitelisting) for inclusion in the spec site.
[ ] @lspiro-Tick42 - Contribute an example Interop.io App Directory JSON schema extension illustrating AI/LLM metadata fields and sandbox discovery controls.
[ ] @novavi - Work with Juliana to produce a “top 10 lessons” write-up on bringing FDC3 methods/tools into AI workflows; open an issue to track.
[ ] @robmoffat - Explore an MCP↔FDC3 adapter concept note to leverage the MCP app ecosystem on FDC3 desktops; report back with pros/cons.
[ ] All - Convert specific ideas from this meeting into individual GitHub issues or Discussions (skills analysis, gap analysis, BPM/task-list use case, Web-MCP considerations).
[x] @mistryvinay - Publish these minutes to issue #1698 and coordinate next month’s FIX topic with Jim Kaye.