This repository is the governance home for the FINOS Architecture as Code project, also known as CALM.
It contains no code. Its purpose is to hold the project-wide governance documentation in a neutral location, so that no single code repository implies it is the "home" of the project. Every repository in the project defers to the documents here as the authoritative source.
| Document | Purpose |
|---|---|
| GOVERNANCE.md | Project governance policies — roles, contribution rules, Maintainer voting, and how Maintainers are added and removed. Applies to all repositories in the project. |
| CONTRIBUTING.md | Project-wide contribution guidelines — how to raise issues, submit pull requests, and the responsible use of AI coding assistants. |
| CODE_OF_CONDUCT.md | The Code of Conduct all participants are subject to. |
| MAINTAINERS.md | The current Maintainer roster for the project. |
| SECURITY.md | How to report a security vulnerability. |
The FINOS Technical Charter for the project will be published as a PDF at the root of this repository once FINOS has issued it. It defines mission, scope, IP and licensing, and takes precedence over the documents here.
The project is organised across the following repositories:
| Repository | Contents |
|---|---|
| calm-governance | This repository. Project-wide governance, contribution guidelines, and Code of Conduct. |
| architecture-as-code | The main repository — CLI, server, shared libraries, data models, widgets, CALM Hub and its UI, the VS Code extension, and the documentation site. |
| calm-schema | Proposed. The CALM Meta Schema, its documentation, and validation test suite. |
The restructure that introduces calm-schema, together with a proposed rename of the main repository to calm and of the FINOS project itself to CALM, is described in architecture-as-code#2354. Those are proposals under discussion — until FINOS approves the rename, the official project name remains "Architecture as Code".
Governance changes are made in the open:
- Open an issue describing the change you are proposing and the problem it addresses.
- Discuss it with the Maintainers and the wider community. Governance topics are also raised at the monthly community meetup and weekly Office Hours.
- Raise a pull request against the relevant document.
Minutes of governance meetings are recorded as issues in this repository using the Meeting Minutes issue template, giving governance decisions a public record alongside the policies they change.
Amendments to GOVERNANCE.md require a vote of the Maintainers, following the Maintainer Voting process set out in that document. Changes to the Maintainer roster follow the process in MAINTAINERS.md.
Security vulnerabilities must be reported privately rather than raised as issues — see SECURITY.md.
NOTE: Pull requests must follow this repository’s contribution policy. FINOS projects typically use DCO (signed commits) and/or CLA via EasyCLA, depending on configuration. Read FINOS Contribution Requirements before contributing.
Questions about CLA, DCO, or EasyCLA? Email help@finos.org
Copyright 2026 FINOS
Distributed under the Apache License, Version 2.0.
SPDX-License-Identifier: Apache-2.0