Skip to content

BDR-0011 – Ecosystem Catalog as Canonical Long-Term Map

  • Type: Business Decision
  • Status: Accepted
  • Date: 2026-06-10
  • Owner: ConnectSoft Architecture & Product
  • Related Areas: Product Portfolio / Long-Term Vision / Ecosystem

This decision establishes the SaaS Ecosystem Catalog as the canonical long-term map of ConnectSoft's ~1,500 candidate products, services, and components. It is written for executives, product managers, and architects planning multi-year strategy.

Decision

The Ecosystem Catalog is the single canonical, long-term superset of ConnectSoft's product and service ambitions. Roadmaps remain authoritative for timelines; the catalog is authoritative for what could exist, how items are classified, and how they map to bounded contexts and waves.

Context

ConnectSoft can name far more products than it can build at once. BDR-0008 set the long-term horizontal + vertical + ecosystem strategy; we now need a single, machine-readable map that operationalizes it without implying 1,500 microservices.

The question: where does the authoritative long-term list of ecosystem items live, and how does it relate to the roadmaps?

Decision

  1. The Ecosystem Catalog under product-portfolio/ecosystem-catalog/ is the canonical long-term map.
  2. It is a superset: the 2026 Roadmap and Platforms Roadmap remain authoritative for timelines and commitments.
  3. The machine-readable catalog (master-service-catalog.yaml / .csv) is the source of truth for tooling, backlog generation, and Azure DevOps planning.
  4. Classification and topology follow ADR-0010 and ADR-0011; sequencing follows ADR-0012.

Rationale

  • One canonical map prevents divergent, conflicting product lists.
  • A superset model lets us capture ambition without over-committing timelines.
  • Machine-readability enables automation across planning and delivery.

Consequences

Positive

  • Clear, durable reference for strategy, architecture, and planning.
  • Roadmaps stay lean and time-bound; the catalog absorbs the long tail.

Negative

  • The catalog must be kept current (regenerated from data) to retain trust.