Affiliation
Morgan Stanley
Qualifications for candidacy
Both an employee of a FINOS member organisation (Morgan Stanley) and an active contributor / maintainer. I am also an incumbent TOC member standing for re-election.
- Lead maintainer of FINOS CALM (Architecture as Code) - founded the Architecture as Code Working Group within the DevOps Automation SIG in August 2023 and helped take it through to a top-level FINOS project. CALM operates as a monorepo housing the CALM JSON Schema (Common Architecture Language Model) and the tooling built on top of it: CALM Hub, the CLI, the VSCode plugin, CALM Guard and CALM Studio.
- Active, hands-on contribution history across the
finos/architecture-as-code repo - recent work spans the CALM Hub UI, CLI test coverage, the VSCode extension, documentation/search, dependency and security hygiene, plus AI-powered tooling for CALM authoring (#1628) and seeding community participation such as the DTCC AI-Powered Hackathon (#2050).
- Project governance - led CALM's governance restructure, including the schema/governance repository split and the onboarding of external contributors from multiple member firms.
- Co-lead of the FINOS DevOps Automation SIG and contributor to the TraderX trading simulator.
- Incumbent TOC member - served a full term on the committee, including project onboarding reviews and lifecycle work.
GitHub: @rocketstack-matt
LinkedIn: https://www.linkedin.com/in/matthewbain/
Blog: Accidental Architect
Bio
Matthew Bain is a Distinguished Engineer at Morgan Stanley, where he works on AI, Data, Architecture and Modernization across Prime Brokerage & Securities Finance Technology. He joined Morgan Stanley in 2013 and has held a range of roles across the Institutional Securities Technology division, including leading Cash Management Technology and Securities Lending Trading Technology, and sits on a number of firmwide governance and oversight committees.
Matthew studied Computer Science at Durham University and has worked in technology across the finance industry for around 25 years. Over that time he has built trading systems, data platforms and a fair number of overly adventurous spreadsheets, at several of the world's largest investment banks across asset classes spanning Asset & Wealth Management, Equities Program Trading, and Client & Regulatory Reporting.
His current focus is on how we capture and evolve system architectures as code - making architecture machine-readable and version-controlled so that it can drive automation and provide evidence that what we said we would build is what we actually built. That question matters everywhere, but it is especially important in highly regulated industries. More recently this has extended into data architecture for AI use cases and the governance of AI systems, where machine-readable architecture and controls have a natural role to play. He is the founder and a lead maintainer of FINOS CALM, and is passionate about improving software development practices and driving speed, agility and resilience through a relentless focus on process automation.
What impact do you hope to have on the ecosystem during your tenure as TOC member?
Having served a term on the TOC and helped grow a project from working group to top-level status, I want to use a second term to deepen the work on governance maturity, AI, and the contributor experience. Concretely:
-
Bring architecture-as-code thinking to FINOS technical governance. CALM exists to make architecture and the controls that sit on it machine-readable and verifiable. I would like to help other FINOS projects express their architecture, dependencies and control mappings in a consistent, declarative way - turning architecture into connective tissue between projects rather than prose that drifts from reality.
-
Push the AI governance agenda where it intersects with verifiable controls. The supervisory landscape is shifting (the move from SR 11-7 toward refreshed model-risk guidance, and the way GenAI sits awkwardly outside classic model-risk regimes) and the industry needs open, technically enforceable answers. I would advocate for FINOS work that translates AI governance principles into controls a firm can actually run and evidence, and connect that to the architecture-as-code and AI-readiness efforts already underway.
-
Strengthen project lifecycle and governance rigor. I led CALM's own governance restructure proposal - splitting schema and governance concerns, clarifying maintainer responsibilities, and managing the politics of onboarding contributors from multiple firms. I want to apply that experience when reviewing incoming projects: pre-screening for maintainer diversity, single-vendor concentration, licensing resilience, and a credible path through the project lifecycle.
-
Lower the on-ramp for new FSI contributors. Many engineers inside member firms want to contribute upstream but are blocked by IP-clearance friction, governance unfamiliarity, or unclear pathways. As a maintainer who has walked several first-time contributors through that process, I would like to help shape and document the harmonized contribution and Labs/lifecycle pathways, and mentor incoming maintainers.
Are there any FINOS Strategic Initiatives you would be interested in working on?
- AI Governance Framework (AIGF) - particularly the operational side: turning AIGF risk categories into machine-readable, verifiable controls rather than documentation, and the relationship between AI governance and model-risk supervisory expectations.
- AI Readiness / common controls for AI services - where the inheritance and mapping of controls is a live, practical question for member firms.
- CALM (Architecture as Code) - I will continue as a maintainer.
Confirmation & Commitment
Affiliation
Morgan Stanley
Qualifications for candidacy
Both an employee of a FINOS member organisation (Morgan Stanley) and an active contributor / maintainer. I am also an incumbent TOC member standing for re-election.
finos/architecture-as-coderepo - recent work spans the CALM Hub UI, CLI test coverage, the VSCode extension, documentation/search, dependency and security hygiene, plus AI-powered tooling for CALM authoring (#1628) and seeding community participation such as the DTCC AI-Powered Hackathon (#2050).GitHub: @rocketstack-matt
LinkedIn: https://www.linkedin.com/in/matthewbain/
Blog: Accidental Architect
Bio
Matthew Bain is a Distinguished Engineer at Morgan Stanley, where he works on AI, Data, Architecture and Modernization across Prime Brokerage & Securities Finance Technology. He joined Morgan Stanley in 2013 and has held a range of roles across the Institutional Securities Technology division, including leading Cash Management Technology and Securities Lending Trading Technology, and sits on a number of firmwide governance and oversight committees.
Matthew studied Computer Science at Durham University and has worked in technology across the finance industry for around 25 years. Over that time he has built trading systems, data platforms and a fair number of overly adventurous spreadsheets, at several of the world's largest investment banks across asset classes spanning Asset & Wealth Management, Equities Program Trading, and Client & Regulatory Reporting.
His current focus is on how we capture and evolve system architectures as code - making architecture machine-readable and version-controlled so that it can drive automation and provide evidence that what we said we would build is what we actually built. That question matters everywhere, but it is especially important in highly regulated industries. More recently this has extended into data architecture for AI use cases and the governance of AI systems, where machine-readable architecture and controls have a natural role to play. He is the founder and a lead maintainer of FINOS CALM, and is passionate about improving software development practices and driving speed, agility and resilience through a relentless focus on process automation.
What impact do you hope to have on the ecosystem during your tenure as TOC member?
Having served a term on the TOC and helped grow a project from working group to top-level status, I want to use a second term to deepen the work on governance maturity, AI, and the contributor experience. Concretely:
Bring architecture-as-code thinking to FINOS technical governance. CALM exists to make architecture and the controls that sit on it machine-readable and verifiable. I would like to help other FINOS projects express their architecture, dependencies and control mappings in a consistent, declarative way - turning architecture into connective tissue between projects rather than prose that drifts from reality.
Push the AI governance agenda where it intersects with verifiable controls. The supervisory landscape is shifting (the move from SR 11-7 toward refreshed model-risk guidance, and the way GenAI sits awkwardly outside classic model-risk regimes) and the industry needs open, technically enforceable answers. I would advocate for FINOS work that translates AI governance principles into controls a firm can actually run and evidence, and connect that to the architecture-as-code and AI-readiness efforts already underway.
Strengthen project lifecycle and governance rigor. I led CALM's own governance restructure proposal - splitting schema and governance concerns, clarifying maintainer responsibilities, and managing the politics of onboarding contributors from multiple firms. I want to apply that experience when reviewing incoming projects: pre-screening for maintainer diversity, single-vendor concentration, licensing resilience, and a credible path through the project lifecycle.
Lower the on-ramp for new FSI contributors. Many engineers inside member firms want to contribute upstream but are blocked by IP-clearance friction, governance unfamiliarity, or unclear pathways. As a maintainer who has walked several first-time contributors through that process, I would like to help shape and document the harmonized contribution and Labs/lifecycle pathways, and mentor incoming maintainers.
Are there any FINOS Strategic Initiatives you would be interested in working on?
Confirmation & Commitment