How drafts become standards in The Gathering.
The Gathering is an open, community-governed standards body for Machine Experience (MX). Work begins as a draft, improves through review, and becomes a ratified standard when the community reaches consensus and the document is ready to ship.
Stream is where the process happens. It hosts drafts, discussions, review notes, and the decision record, so anyone can follow the history and understand how a standard was formed.
2Review3Call for consensus4RatifyA proposal starts a new draft in Stream. It should explain the problem, define scope and non-goals, and include an initial outline. The goal is clarity, not completeness.
Drafts are improved through public review. Participants leave review notes, suggest edits, request evidence, and flag ambiguity. Editors keep structure, terminology, and versioning consistent.
When a draft is stable enough, a call for consensus is opened in Stream for a defined review window. This is the point where the community checks for unresolved objections and confirms the document is ready to ratify.
If consensus is reached, the draft is ratified and published as a versioned standard. The standard remains available along with its history, and future changes happen through new proposals and revisions.
No membership
There is no membership in The Gathering. Anyone can read drafts and follow progress. Accounts exist for practical reasons (attribution, anti-spam, and process history) and are needed to comment, propose changes, or signal consensus in Stream.
