Roadmap¶

Audience: anyone asking "is X available, experimental, or planned?" Purpose: the single, indexed home for everything not fully available today.

• Today. Compono's shipped package set — Compono, Compono.XunitV3, Compono.NSubstitute, Compono.Bogus, Compono.TUnit, Compono.TestDoubles, Compono.DependencyInjection, and Compono.Http — covers the full MVP package set (docs/mvp.md's "MVP Package Set") plus Compono.TUnit and Compono.TestDoubles, the two candidates to graduate the whole way through Future Packages' admission model (PLAN-0040, PLAN-0043), plus Compono.DependencyInjection (ADR-0047), which didn't graduate through that admission model at all — see that ADR and RESEARCH-0007 for how it came about instead — and, the same way, Compono.Http (ADR-0051), which also didn't graduate from Future Packages' own candidate list; it came from a dedicated admission research doc triggered by a real alexa-vox-craft dogfooding need — see RESEARCH-0009. Compono.Options (ADR-0061) reached this shipped state the same way, via a dedicated admission research doc (RESEARCH-0028) triggered by an explicit product-owner request rather than this page's own candidate pipeline. If a capability isn't documented in Concepts, How-to Guides, or a Package Guide, it isn't available yet — see below for where it might be headed.
• Experimental / under discussion. Proposed ADRs — design decisions still being discussed, not yet Accepted.
• Planned / candidate. Post-MVP roadmap — evidence-backed capability gaps surfaced by real dogfooding, and Future Packages — integration packages beyond the shipped set that could follow the same pattern Compono.NSubstitute/Compono.Bogus already established, but aren't committed yet.

Each of these is deliberately a status-filtered index, not new narrative content of its own — every candidate/proposal it lists is backed by a real ADR, research finding, or explicit non-goal recorded elsewhere, per this repo's evidence-over-prediction bias (ADR-0029).