Capability Lifecycle
Every capability progresses through four stages (GOVERNANCE.md §2):
| Stage | Meaning |
|---|---|
| PROPOSED | RFC filed as a GitHub Issue; open for community discussion. |
| DRAFT | Experimental implementation exists; conformance tests written; API may change. |
| STABLE | API locked; conformance tests locked; only backwards-compatible changes allowed. |
| FROZEN | Immutable — the capability's interface and tests will never change. |
All ten capabilities defined in v0.2 are FROZEN — including AUDIT and SUPERSESSION_CHAIN.
Two invariants underpin this:
- Append-only. The
Capabilityenum is append-only across versions; capabilities are added in minor releases, never repurposed or removed. - Semantic versioning. GMP follows
MAJOR.MINOR.PATCH(see Protocol governance). A capability's meaning is fixed within a version; only a MAJOR bump can break it.
GOVERNANCE.md is the single source of truth for capability status across the docs and grafomem.com.