Proposed working groups

No working groups have been formally chartered yet. The first WG will be announced following the May 2026 specification launch. Proposals below are under development.
  • 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.

    Chair: To be appointed AAIF SEP target: Q3 2026 Scope: MCP 2026 change event extensions
  • 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.

    Chair: To be appointed Target: Q4 2026 Scope: Regulatory compliance extension fields
  • 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.

    Chair: To be appointed Target: v1.1 (2027) Scope: Cryptographic key transparency and signer authorization

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:

  1. Open an issue in github.com/changespec/spec with the label working-group-proposal.
  2. Include: proposed charter (problem statement, scope, non-goals, deliverables, success criteria), proposed chair(s), expected participant organizations, timeline.
  3. 30-day comment period before maintainers vote on chartering.
  4. 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.