Standard Lifecycle
Document status model for HEXT Standard releases
Lifecycle Stages
HEXT Standard documents progress through defined lifecycle stages comparable to W3C and IETF practice. The current public release is at Stable.
Draft
↓
Candidate
↓
Stable
↓
Maintenance
↓
Deprecated
| Stage | Description |
|---|---|
| Draft | Work in progress. Requirements may change without notice. Not suitable for implementation claims. |
| Candidate | Feature-complete review release. Implementers may test against candidate text pending final stabilization. |
| Stable | Normative release suitable for production implementation and citation. |
| Maintenance | Stable release receiving errata, clarifications, and non-breaking corrections. |
| Deprecated | Superseded by a newer stable release. Retained for historical reference only. |
Current Release
| Document | Version | Lifecycle |
|---|---|---|
| HEXT Standard | 1.0.0 | Stable |
Historical Transitions
- RFC era — Design history archived under informative references
- v2.2.0 draft — Superseded by HEXT Standard 1.0 Stable (2026-07-07)
- HEXT Standard 1.0 — Initial public stable release
Implementation Profiles
HEXT uses additive Implementation Profiles to describe optional capability sets beyond the frozen Core Standard. Profiles never redefine Core conformance. See Conformance — Profiles for full definitions.
| Profile | Status | Standard |
|---|---|---|
| Core | Stable | HEXT Standard 1.0 |
| Discovery | Stable | HEXT Standard 1.0 |
| Registry | Planned | HEXT Standard 1.1 |
| MCP | Planned | HEXT Standard 1.1 |
| WebMCP | Planned | HEXT Standard 1.1 |
Future Minor Releases
Registry, MCP, WebMCP, and SDK profiles are expected in HEXT Standard 1.1 under Maintenance-track minor releases without breaking 1.0 Core conformance. Major version 2.0 remains reserved for breaking changes.