Updates and evolution
Separate what is available now, what changed, how evidence becomes proposals, and what remains future work.
Use this section to distinguish delivered capability from ongoing learning and future candidates.
Four different questions
| Question | Read |
|---|---|
| What is supported now? | Current state |
| What changed for consumers? | Changelog |
| How do skills evolve safely? | Evolution layer |
| What may happen later? | Efficiency Layer roadmap |
A roadmap item is not delivered capability. An observation is not an approved proposal. A proposal is not a merged skill change.
Governed evolution
The Evolution layer describes how observations, proposals, reviews, protected surfaces, and validation interact.
Supporting references include Optimization boundaries, Skill evolution experiments, Validation case guidelines, and Recommended telemetry.
Roadmaps and candidates
The Efficiency Layer pages describe a bounded evolution track:
Treat candidates and next signals as future-facing until canonical files and validation state show delivery.
Next steps
- Start with Current state for a present-tense view.
- Use Cases and evidence when evaluating maturity claims.
- Maintainers should continue to Maintainer reference.