22 April 2026 - AI Governance Framework Meeting Agenda

[lucaborella89]

Overview

Click on the image and then on the item to view the related repo

Date

20260422 - 3pm GMT

Zoom details

https://zoom-lfx.platform.linuxfoundation.org/meeting/97158459687?password=62a83d0b-7b19-416d-8250-e5bcf9f7640b

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.

Agenda and minutes

• PR and project review
• OSFF Toronto Training Dry-run debrief (use cases are needed but difficult to get FSIs public on this) @d1gital-f
• Adoption paths (1-pager) Documentation Improvements - Update 1-pagers to help FSIs adopt AIGF and drive buy-in #251 @lucaborella89
• Go to market / Getting ready for FINOS AI Community Call / MRM Demo material with AIGF MCP + CALMSuite / 1) Why in open source is valuable 2) Why we cannot just use existing framework @chamindra
• Skills governance: how people onboard skills, how this function sit? Does the governance need to be on central teams? Discuss governance of "skills"? #258 @alvin-c-shih
• Use Cases Catalogue enriches the industry flavour of the AIGF. Use case and reg layers add value statement internally. We don't want to re-invent the wheel, shall we use Evident AI public data vs. setting up a mechanism legally proven whereby the data can be shared. Anonymised survey to get the data. Here the 3 top threats vs. cross industries @lucaborella89
• Add meeting KPIs after each working session ends

[lucaborella89]

From Prashant George:

https://www.occ.treas.gov/news-issuances/bulletins/2026/bulletin-2026-13.html

The link also mentions a RFI coming up soon @pmerrison

[lucaborella89]

Quick recap:

The meeting focused on reviewing the AI Governance Framework (AIGF) and discussing its
implementation and adoption strategies.

@lucaborella89 presented feedback from the recent OSFF Toronto training session, which highlighted the need for
more use cases and case studies to help organizations understand how to adopt the framework.

The group discussed go-to-market strategies, with @chamindra suggesting the need for more targeted
materials for different organizational roles and clearer value propositions for open-source peerreviewed frameworks.
#251

Jerome offered to share DTCC's inventory of over 200 use cases to help populate the framework with
real-world examples.

The conversation also covered potential partnerships with vendors and risk management firms, as well
as the development of a vendor onboarding questionnaire led by @MKQuantum #294

@alvin-c-shih presented a reference architecture for skills management within the framework #272 and a number new risks and mitigations discovered while building the architecture #273

@Tanishq1030 shared a tool for scanning codebases against regulatory rules and policies.
#259

The conversation ended with discussions about integrating these various components into the broader
AIGF ecosystem.

Stats:

• 15 participants

Full meeting minutes attached LFX Meetings - AIGF working session - 22 April .pdf

[Tanishq1030]

hey, @lucaborella89
I just wanted to add a quick point of clarification to the minutes regarding the Anchor presentation so the full scope is captured for the AIGF integration discussions.

While the summary correctly highlights Layer 1 (the static analysis and codebase parsing for regulatory compliance), Anchor actually operates as a two-engine system. Layer 2 is the dynamic enforcement engine: a WebAssembly (WASM) sandbox (the Diamond Cage) that intercepts live autonomous agent tool-calls, evaluates them against the ruleset in under 5ms, and hashes the decisions into the cryptographic ledger.

I completely agree with Alvin’s suggestion to explore how the static engine can consume definitions from architecture-as-code frameworks. Moving forward, I would also love to discuss how the AIGF approaches real-time execution boundaries for agentic workflows using that Layer 2 dynamic sandbox.

Looking forward to picking this up in issue #259!