Open for comment

Anyone may comment. No membership or GitHub account is needed. Every comment gets a public answer.

How a proposal becomes a specification

The process borrows from the IETF, W3C community groups, the FinOps Foundation’s FOCUS and MCP’s enhancement proposals.

  1. 1

    Draft Draft

    Editors write the text in the open, numbered and versioned below 1.0. It can change in any way.
  2. 2

    Public comment Public comment

    A stated period of at least 30 days. Each comment is answered in public: accepted, accepted in part, declined with a reason, or deferred.
  3. 3

    Accepted Accepted

    A stable version, 1.0 or later, after at least one full comment period on that text. Later changes follow semantic versioning and are commented on again.
  4. 4

    Handed off Handed off

    The Institute hands mature proposals to established standards bodies rather than competing with them.

Read the full process →

Where the text lives

The text will be published in a public GitHub repository, github.com/agentrelations/specs, where its history and every comment can be read. Until then, comment here. The site shows the same text the repository holds.

Specification text
Creative Commons Attribution 4.0 (CC BY 4.0): copy, adapt and build on it, including commercially, with credit.
Schemas and code
Apache License 2.0, which adds a patent grant.
Contributions
Issues and pull requests on GitHub, each commit signed off under the Developer Certificate of Origin; or the comment form on each proposal’s page.

Help shape a proposal

Practitioners from any organization can comment on drafts and join a working group.