Working Groups
Working groups
Focused working groups developing specification extensions, tooling standards, and ecosystem interoperability.
Proposed working groups
-
Proposed
MCP Change Events WG
Develops a Specification Extension Proposal (SEP) to the AAIF (AI Agentic Internet Forum) proposing ChangeSpec-format change events as the reference model for MCP change feeds. If the SEP is accepted, this working group transitions to an AAIF WG, with ChangeSpec maintaining authorship of the reference implementation.
-
Proposed
Compliance Extension WG
Formalizes the
ext:compliance.*namespace for DORA, OSFI B-10, FCA, and OCC third-party risk extension fields. Produces a published extension schema and mapping documentation that can be cited in regulatory comment submissions. -
Proposed
Key Transparency WG
Designs the key transparency log mechanism planned for ChangeSpec v1.1 (Section 12.20 of the 1.0 spec identifies this as a known limitation). Produces a SEP for the transparency log architecture, trust bootstrap protocol, and consumer verification requirements.
Proposing a working group
A Working Group may be proposed when a body of work is too large for a single SEP and requires sustained collaboration across multiple organizations. To propose a WG:
- Open an issue in github.com/changespec/spec with the label
working-group-proposal. - Include: proposed charter (problem statement, scope, non-goals, deliverables, success criteria), proposed chair(s), expected participant organizations, timeline.
- 30-day comment period before maintainers vote on chartering.
- Chartered WGs are listed here with a link to their charter and discussion channel.
WG chairs are not required to be existing ChangeSpec maintainers, but must be nominated by an existing maintainer.