Skip to content

Extension Roadmap

Target Architecture — Final-State Design

This page describes how the Template & Library Platform grows beyond its initial ConnectSoft.Factory.Templates.* decomposition. Items here are future, planned capabilities; the 16 microservices, 10 APIs, 7 workers, and 15 aggregate roots documented in the sibling pages are the baseline target architecture they extend.

The platform is designed to be extended without disrupting the catalog or breaking reproducibility. New generators, libraries, analysis services, and agent integrations slot into the same registry, event, and compatibility model. This page sets the principles for that growth and enumerates the planned next steps.

Extension principles

  1. Template-first, always — every new generation capability is expressed as a registered, versioned template, never as ad-hoc code generation. New asset types extend the category taxonomy rather than bypassing the registry.
  2. Capability over package — new libraries declare LibraryCapability so agents discover them by what they do; renames and re-homing never break consumers.
  3. Immutable, reproducible versions — extensions preserve the guarantee that a pinned version + parameters yields an equivalent output; new engines must produce the same ScaffoldOutput shape and provenance.
  4. Compatibility is declarative — new constraints are added as TemplateCompatibilityRules, keeping the safety model machine-evaluable and auditable.
  5. Everything emits canonical events — new services and workers publish NounVerbPastTense events in the event envelope so traceability and observability extend for free.
  6. Multi-tenant and governed by default — new surfaces inherit tenant isolation, OAuth2 scopes, and publishing approvals.
  7. Reuse before regeneration — extensions strengthen discovery (search, capability index, API client catalog) so the factory prefers existing assets.

Future microservices

Planned service Responsibility Builds on
TemplateComposerService First-class multi-template composition plans (solution blueprints) as a managed aggregate ScaffoldEngineService, TemplateCompatibilityService
TemplateMarketplaceSyncService Bidirectional sync of catalog assets with the Marketplace, including external partner submissions TemplatePublishingService, PackagePublisherService
LibraryVulnerabilityService Continuous CVE/advisory scanning and SBOM generation for library versions DependencyAnalyzerService
TemplateLicenseComplianceService License classification and policy enforcement across templates and transitive dependencies DependencyAnalyzerService, Governance platform
ScaffoldDiffService Structured diffing between scaffold outputs and live product repos for drift detection and re-scaffold preview ScaffoldEngineService
TemplatePersonalizationService Tenant- and team-specific template variants/overlays without forking the canonical template TemplateVersionService, TemplateParameterService

Future workers

Planned worker Trigger Purpose
VulnerabilityScanWorker LibraryVersionCreated, scheduled Scan published packages against advisory feeds; emit VulnerabilityDetected
SbomGenerationWorker LibraryPublished, ScaffoldGenerated Produce and attach an SBOM to each published artifact
DriftDetectionWorker scheduled / product repo webhook Compare live product repos to their scaffold provenance; emit ScaffoldDriftDetected
LicenseScanWorker DependencyScanned Classify licenses across the dependency closure; flag policy violations
TemplateAutoUpgradeWorker TemplateUpgradePlanCreated (low-risk) Auto-open re-scaffold pull requests for low-risk upgrades via DevOps
CatalogReindexWorker scheduled Rebuild the capability/tag search index from the registry

Future APIs

Planned endpoint Purpose
POST /v1/compositions Register and version a multi-template solution blueprint
POST /v1/compositions/{id}/execute Generate a full multi-service solution from a blueprint
POST /v1/templates/{templateId}/diff Diff two template versions or a version against a product repo
GET /v1/libraries/{libraryId}/vulnerabilities Retrieve CVE/advisory findings for a library
GET /v1/libraries/{libraryId}/sbom Retrieve the SBOM for a library version
POST /v1/templates/{templateId}/personalize Create a tenant/team overlay of a template
GET /v1/analytics/templates Adoption and reuse analytics for templates and libraries

Marketplace opportunities

  • Partner-contributed templates and libraries — external vendors publish generators and packages into the Marketplace, governed by the same validation, compatibility, and approval flow.
  • Verified/certified badges — assets that pass enhanced validation, vulnerability, and license checks earn certification surfaced in marketplace ranking.
  • Capability-driven discovery — marketplace search backed by the LibraryCapability index lets teams find assets by need, not name.
  • Usage-based ranking and recommendations — TemplateAnalyticsService signals feed marketplace recommendations ("teams building booking SaaS also use…").
  • Monetization and entitlements — premium templates/libraries gated through ConnectSoft.Extensions.Saas.Entitlements and the SaaS billing family.

Agent opportunities

The platform is the primary tool surface for the Agent Mesh; these extensions deepen agent autonomy:

  • Template authoring agents — agents that synthesize new templates from recurring scaffold patterns observed across products, then submit them through the registration/validation flow.
  • Library recommendation agents — agents that, given a capability need and context from the Knowledge Platform, recommend the optimal compatible library set and pre-evaluate compatibility.
  • Upgrade orchestration agents — agents that consume TemplateUpgradePlanCreated/PackageUpgradeAdvised, open re-scaffold PRs, and shepherd them through DevOps with governance approvals.
  • Compatibility-repair agents — agents that, on a failed CompatibilityEvaluated, automatically search for a satisfying version set and retry generation.
  • Drift-remediation agents — agents that react to ScaffoldDriftDetected and propose bringing a product back in line with its template provenance.
  • MCP tool exposure — registry, search, compatibility, and execution APIs exposed as Model Context Protocol tools via ConnectSoft.Extensions.ModelContextProtocol, so any Microsoft Agent Framework agent can use the platform natively.