# How a proposal becomes a specification

> Stages, comment periods, versions and who decides. The same text as PROCESS.md in the specifications repository.

Source: https://agentrelations.org/standards/proposals/process

The Institute drafts in the open, asks for public comment, answers every comment in public and only then accepts a version. The process borrows from the IETF (numbered drafts, last call), W3C community groups (open drafts on GitHub, anyone may comment), the FinOps Foundation's FOCUS (a versioned Markdown specification with releases) and MCP's Specification Enhancement Proposals (a status in every document, a named sponsor).

### Stages

| Stage | What it means | How it moves on |
| --- | --- | --- |
| **Idea** | A problem worth solving, raised as a GitHub Discussion or by the Institute. Not yet in `proposals/`. | An editor agrees to write it and opens a pull request with a first draft. |
| **Draft** | In `proposals/` with a number, editors and a version below 1.0. It can change in any way. | The editors judge it complete enough to comment on and set a comment period. |
| **Public comment** | Open for comment for a stated period, at least 30 days. The dates are in the front matter and on the site. | The period closes and every comment has a public answer. Then the editors publish a revised draft (back to Draft), or propose acceptance. |
| **Accepted** | A stable version, 1.0.0 or later. Implementations can rely on it. | Changes go through the same stages as a new version. |
| **Withdrawn** | Stopped, with the reason stated. The text stays for the record. | None. |
| **Superseded** | Replaced by a later proposal, named in the front matter. | None. |
| **Handed off** | Transferred to an established standards body (IETF, W3C, schema.org, the Agentic AI Foundation or another). The Institute's version points to the new home. | None. |

A proposal may go round Draft and Public comment several times. Acceptance needs at least one full comment period on the version being accepted.

### Who does what

- **Editors** write the text, run the comment period and answer comments. Each proposal names its editors in its front matter. Anyone may volunteer to edit; the Institute appoints them.
- **Contributors** comment, open issues and send pull requests. Anyone may contribute; no membership is needed.
- **The Institute** decides when a proposal moves to Accepted, Withdrawn or Handed off, on the editors' recommendation, and publishes its reasons in the pull request that makes the change.

### Comment periods

1. The editors set the opening and closing dates in the proposal's front matter (`comment_opens`, `comment_closes`) and the site shows them.
1. Comments arrive as GitHub issues (template: *Comment on a proposal*) or through the form on the site, which the editors copy here as issues. A comment sent after the close is still read and answered, and may wait for the next version.
1. Each comment gets one of four answers, recorded on its issue: **accepted** (and the version that carries the change), **accepted in part**, **declined** (with the reason), or **deferred** (to a named later version).
1. When the period closes, the editors list the comments and their answers in the proposal's *Changes* section for the next version.

### Versions

Each proposal is versioned on its own, with [semantic versioning](https://semver.org/):

- **Patch** (1.0.1): wording only, no change in meaning. No comment period.
- **Minor** (1.1.0): additions that leave existing implementations conforming. A comment period of at least 30 days.
- **Major** (2.0.0): changes that can break an implementation. A comment period of at least 60 days.
- Below 1.0.0, any release may change anything.

A release is a commit that sets `version` and `updated` in the front matter, adds an entry to [CHANGELOG.md](https://agentrelations.org/standards/proposals#repository) and to the proposal's *Changes* section, and is tagged `<proposal>/v<version>` (for example `activity-measurement/v0.1.0`). Earlier versions stay readable at their tags. Schemas live under `schemas/<proposal>/<major.minor>/` so an old version's schema never moves.

### Front matter

Every proposal starts with:

```
---
number: 1
title: Agent Activity Measurement
slug: activity-measurement
status: Public comment          # Draft | Public comment | Accepted | Withdrawn | Superseded | Handed off
version: 0.1.0
created: 2026-11-20
updated: 2026-11-20
editors: Institute for Agent Relations staff
summary: One sentence that says what the proposal does.
comment_opens: 2026-11-20
comment_closes: 2027-01-31
---
```

### Conformance language

The key words MUST, MUST NOT, SHOULD, SHOULD NOT and MAY are used as described in [RFC 2119](https://www.rfc-editor.org/rfc/rfc2119) and [RFC 8174](https://www.rfc-editor.org/rfc/rfc8174) when, and only when, they appear in capitals.

### Patents

Text is contributed under CC BY 4.0 and code under Apache 2.0, which carries a patent grant for code. Before organizations other than the Institute contribute substantial specification text, the Institute will adopt a patent policy for specifications and publish it here.

[← All proposals](https://agentrelations.org/standards/proposals)
