Skip to content

Post-MVP roadmap

Evidence-backed roadmap candidates surfaced by real dogfooding, per ADR-0029's capability-gap decision framework. This page exists per PLAN-0007 Phase 3's required deliverable — it lists only findings classified roadmap candidate: Compono genuinely needs a new capability, backed by real observed frequency and workaround cost, each with a Proposed ADR recording the problem. Per ADR-0029: "bugs get fixed, intentional design differences and acceptable alternatives do not become roadmap items" — this page is not a general findings log, and non-candidate findings belong in the research record and their governing ADR's Amendments, not here.

Current state: no roadmap candidates

Per docs/roadmap/index.md, this page is a status-filtered index of capability gaps that are not yet available — a shipped capability doesn't stay listed here once it's implemented, even though the evidence that motivated it remains a permanent part of the record elsewhere (the ADR, the research doc, the plan). Two dogfooding passes have run so far:

  • Milestone 7's pass (migrating ncipollina/cosmere-tracker's AutoFixture-based test kit to Compono) surfaced ten findings, none classified roadmap candidate — every finding's evidence pointed toward Compono's existing model already being the right answer, a project-local fix, or an unexercised theoretical constraint, not a missing capability. See RESEARCH-0001's "Classifications (Phase 3)" and "Decisions" sections for the full per-finding reasoning.
  • A subsequent pre-migration capability survey of ncipollina/trivia-platform's (much larger) AutoFixture test kit — see RESEARCH-0002 — surfaced one finding classified roadmap candidate: call-site values influencing nested composition, motivated by trivia-platform's parameterized custom AutoDataAttribute subclasses (e.g. PersistenceAutoData(repositoryName), ~45 call sites). That finding is no longer a candidate — it's been designed, Accepted, and shipped: ADR-0036 records the decision, PLAN-0036 (Done) records the implementation, and Compono.XunitV3's Package Guide is the current-state usage documentation — ComposeAttribute<TProfile, TConfig> is available today, not planned.

That two dogfooding passes together produced zero outstanding roadmap items is itself a real, evidence-backed outcome, not a shortfall in the process — it doesn't mean Compono is "done": a different real-world project, or a future package, may surface a finding neither of these two did (each is one data point, not an exhaustive survey).