Skip to content

ADR-0014: Template-Driven Delivery Model for the Ecosystem

  • Status: accepted
  • Deciders: ConnectSoft Architecture Team
  • Date: 2026-06-10

Context and Problem Statement

To deliver a large ecosystem consistently and at speed, we need a uniform way to create services, libraries, UI modules, connectors, and agents. Hand-crafting each one diverges in structure, quality, and cross-cutting concerns.

Decision Drivers

  • Consistency of architecture, security, observability, and tenancy across many components.
  • Speed of delivery via the AI Software Factory.
  • Reuse of the existing template and agent infrastructure.

Considered Options

Option 1: Hand-craft each component

  • Inconsistent, slow, hard to govern. Rejected.

Option 2: Generate every serious component from factory templates (Selected)

Decision

Every serious candidate is generated from ConnectSoft factory templates and evolved by agents:

  • Services from the microservice template and agent microservice standard blueprint.
  • Libraries, UI modules, connectors, and agents from their respective templates.
  • Cross-cutting concerns (tenancy, identity, config, audit, observability) are inherited from shared libraries and overlays, not re-implemented.

The catalog's reference architecture describes the resulting structure.

Rationale

  • Guarantees baseline quality and consistency across 1,500 candidates.
  • Leverages the AI factory for generation, QA, and documentation.
  • Reduces the marginal cost of each new component.

Consequences

Positive

  • Faster, more consistent delivery; easier governance and review.

Negative

  • Templates must be maintained and versioned; drift between template and generated code must be managed (see template lifecycle).