Collective
Governance.
How proposals move from draft to ratified. Every change to the standard is public, versioned, and reviewable.
Process
Author writes a short RFC describing the change and its rationale.
The RFC opens for feedback from any contributor for 7 days.
The relevant working group formalizes objections and requested changes.
Contributors vote. Simple majority ratifies most changes; breaking changes require 2/3.
Accepted changes ship in the next standard version with a full changelog entry.
Open proposals
| ID | Title | Author | Stage | Objects | Opened | Closes |
|---|---|---|---|---|---|---|
| GTM-014 | Add cloud_spend as required field on ICP for Enterprise tier Introduce cloud_spend as a required firmographic on ICP objects for the Enterprise segment. 12 accepts, 3 rejects so far. | Marcus Aurelius | Voting | ICP | Nov 3 | Nov 17 |
| GTM-013 | Deprecate legacy intent_score in favor of decayed_score Move Signal scoring to a time-decayed model. Deprecation window of two minor versions. | Sarah Kaur | Review | Signal | Oct 28 | Nov 20 |
| GTM-011 | Introduce Campaign v1.0 (out of draft) Promote the Campaign object from Draft to v1.0. Includes required window and audience_ref fields. | Nash Delarosa | Draft | Campaign | Oct 22 | TBD |
Recently ratified
Working groups
Core objects, versioning, deprecation policy.
Prompt authoring, evaluation, and grounding.
Adapter conformance and mapping reviews.