Community

Community-driven governance

MCPF is intended to outlive any single vendor. The community decides the standard, the repo structure, and the release cadence.

How to participate

Contribute like infrastructure projects do

Prefer small, reviewable changes; preserve backward compatibility; document everything; and keep releases predictable.

Open issues first

Start with a problem statement: what breaks without trust? what policy must an enterprise enforce? what should be revocable?

Share real-world use cases

Registries only matter when used in production. Share patterns: internal allowlists, regulated industries, partner federation, audits.

Start here

Note: MCPF is separate from Veritrust as a stand-alone framework. Veritrust can support deployments, but it does not own the standard.