Status
Every feature documented on this site carries exactly one of six status labels. The vocabulary is defined here so you always know whether a section describes something real today or something planned.
The six-level model
Label |
Meaning |
|---|---|
Stable |
Frozen and production-safe. Behavior is guaranteed and will not change without a major version bump. |
Implemented |
Real and tested. Verifyable through gates (unit tests, parity tests, E2E CLI tests). May still evolve. |
Experimental |
Real but subject to change. The capability exists and is testable, but the surface is not yet guaranteed. |
Developer Preview |
Functional but incomplete. Real partial capability with documented gaps. |
Planned |
Designed but not implemented. May appear as roadmap entries or documented intentions; no code exists. |
Not Yet Implemented |
An identified need with no code and no design contract. Nothing is presented as available. |
Honesty rules
Never describe a hypothetical feature as available. A feature is
Implementedonly when it is exercised by a gate test through the real pipeline.Plannedpages must not invent APIs, signatures or examples.Experimentalpages must state exactly why they are experimental (e.g. Go-engine only, wasmtime-gated, kcc parity deferred).A category placeholder (no examples yet) is labeled
Not Yet Implemented, not silently omitted.
Scope-to-vocabulary mapping
The release-candidate matrix (Release-Candidate Scope) uses operational buckets for the 1.0.0 readiness review. Each bucket maps onto exactly one vocabulary label above — this mapping is the single rule, so the two pages can never drift apart:
Stable Beta Core→ StableProduction Candidate→ Implemented, with the single-engine bound stated (e.g. Go-engine only, wasmtime-gated)Experimental→ Experimental, with the reason statedPlanned→ Planned (no code exists)Known Limitation→ Implemented or Experimental with the constraint stated loudly (never silently wrong)Release Candidate Blocker→ not a maturity level — a defect-tracker entry, removed the moment it is fixed
New documentation pages must use the six labels. The scope matrix keeps its operational buckets; this mapping is stated once here and must not be redefined anywhere else.
The catalog pages
Note
The overall project status is Karkain 1.2.0 (Stable) — see
Beta 1 for the Beta 1 capability assessment it builds on.
Individual
features are labeled per the model above; the Developer Preview label
in the vocabulary remains a feature maturity level (functional but
incomplete) rather than the project status.
Practical status pages
Release-Candidate Scope — the authoritative release-candidate status matrix (Stable / Experimental / Planned / Known Limitation / RC Blocker).
Compatibility Policy — the compatibility guarantees attached to each bucket.
Release-Candidate Checklist — the release-candidate acceptance checklist.
Migration to Beta 1 — what changed between Developer Preview and Beta 1.
See also
Karkain by Example — category pages using this vocabulary. Roadmap — where the planned surface fits over time.