Release roadmap¶
This roadmap describes proposed review goals for the CapOps community framework. It is not a promise of delivery dates or evidence of standardization. Content can arrive before its wider release goal is considered complete.
Version 0.1 - A coherent foundation¶
Establish the canonical definition, principles, domains, capabilities, operating model, maturity model, and initial templates. The initial public repository supplies these materials for review; independent practitioner adoption is not assumed.
Exit evidence: maintainers resolve foundational terminology issues, demonstrate a complete fictional iteration, and retain a clean documentation build.
Version 0.2 - Broader application and review¶
Review the expanded scenario library, provider-specific mappings, and original diagrams with external contributors. Initial drafts of this material are included now; their presence is not equivalent to community validation.
Exit evidence: public review records show that scenarios expose meaningful alternatives and residual risks, product claims have current sources, and diagrams remain understandable without rendering.
Version 0.3 - Evidence and reusable assessment¶
Explore an assessment workbook or tool, additional implementation examples, useful practice metrics, and contributions from external practitioners. Any tool should preserve separate capability scores and expose critical weaknesses rather than calculate a reassuring average.
Exit evidence: maintainers can explain the data model, privacy boundaries, metric limitations, and maintenance responsibilities before adopting automation.
How priorities change¶
Accuracy and confidentiality corrections take priority over new features. Proposals should identify the decision improved, the audience, evidence needed, and maintenance burden. Maintainers may defer work lacking a responsible reviewer. No certification, benchmark, or provider integration is implied.