# AI Catalog Governance

The AI Catalog project is governed by the Technical Steering Committee. The initial Committee has four seats, each held by the following individuals:

| Company | Representative | Contact |
| :--- | :--- | :--- |
| Google | Junjie Bu | https://github.com/mindpower |
| Microsoft | Darrel Miller | https://github.com/darrelmiller |
| Anthropic | David Soria Parra | https://github.com/dsp-ant |
| PulseMCP | Tadas Antanavicius | https://github.com/tadasant |
## Mission and Scope of the Project

1. The mission of the Project is to enable discovery of AI services and related artifacts. The Project includes collaborative development of the following components:

   1. AI Catalog specification;

   2. Tooling related to validation of AI Catalogs, and transformation to and from the AI Catalog format; and

   3. documentation and other artifacts related to the Project.

2. The scope of the Project includes collaborative development under the Project License (as defined herein) supporting the mission, including documentation, testing, integration and the creation of other artifacts that aid the development, deployment, operation or adoption of the open source project.

## Technical Steering Committee

1. The Technical Steering Committee (the "TSC") will be responsible for all technical oversight of the open source Project.
2. **TSC Composition**

    a. **"Startup Phase."** At the inception of the Project, four TSC members will be nominated. Two will be nominated by MCP Core Maintainers (https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/MAINTAINERS.md) and two will be nominated by the the Linux Foundation A2A Technical Steering Committee (https://github.com/a2aproject/A2A/blob/main/GOVERNANCE.md).

    b. **"Steady State."** The TSC will decide upon a "steady state" composition of the TSC (whether by election, subproject technical leads, or other method as determined by the TSC).

    c. The TSC may choose an alternative approach for determining the voting members of the TSC, and any such alternative approach will be documented in the GOVERNANCE file. Any meetings of the Technical Steering Committee are intended to be open to the public, and can be conducted electronically, via teleconference, or in person.

3. **Responsibilities:** The TSC will be responsible for all aspects of oversight relating to the Project, which may include:
    1. coordinating the technical direction of the Project;
    2. approving project or system proposals;
    3. appointing representatives to work with other open source or open standards communities;
    4. establishing community norms, workflows, issuing releases, and security issue reporting policies;
    5. approving and implementing policies and processes for contributing (to be published in the [`CONTRIBUTING`](CONTRIBUTING.md) file - to follow);
    6. discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects; and
    7. coordinating any marketing, events, or communications regarding the Project.

### TSC Voting

While the Project aims to operate as a consensus-based community, if any TSC decision requires a vote to move the Project forward, the voting members of the TSC will vote on a one vote per voting member basis.

Quorum for TSC meetings requires a majority of all voting members of the TSC to be present. The TSC may continue to meet if quorum is not met but will be prevented from making any decisions at the meeting. Decisions by vote require a majority vote of all TSC members.

### TSC Meetings
TSC Meetings are held on the Linux Foundation's meeting platform. [https://zoom-lfx.platform.linuxfoundation.org/meetings/aicatalog](https://zoom-lfx.platform.linuxfoundation.org/meeting/91656063701?password=946db53a-d3d4-4dd2-a8d5-5ed46ae035d3) has meeting details and recordings of past meetings.
Agenda and meeting notes are posted in the [TSC Meeting Notes](https://docs.google.com/document/d/1RriqwfC6fcL5NbpGrFFHXfvonQiIsXrutGuwpnBlAwM/edit?tab=t.ub1ywahpk09y) document.

## Project Communications

The AI Catalog project utilizes GitHub for conversations about the project. All are welcome and encouraged to participate on the [AI Catalog](http://github.com/Agent-Card/ai-card) repository.

Any discussions about feature proposals, significant changes to the project architecture or governance, etc. should be held in GitHub with adequate notice and time for comment. Our goal is that GitHub is the source of truth for significant project decisions.