Skip to content

Software Factory solution pack

Target

This page describes intended behaviour or structure. No implementation is claimed unless a section is explicitly marked Current implementation or Evidence.

A solution pack is a domain's agents, skills, workflows, templates, blueprints and evaluation suites built on the platform planes. The Software Factory pack is the first and richest: it is where most of this site's detail was written. Read "the Factory generates SaaS" throughout those pages as "this pack generates SaaS on the platform" (decision D1).

What the pack contains

Asset class Content Owner / plane
Engineering agents 100 agent role specifications across 9 clusters (vision and planning, architecture, engineering, QA, DevOps, security, UX, documentation, growth, platform evolution) Design intent of this pack; to be authored in a Factory repository, published by Control, executed by the Agent runtime
Workflows Vision-to-production, deployment and observability, security and compliance, testing and QA, documentation, growth, customer success, platform evolution, cost optimization, SaaS template selection Published assets; deterministic orchestration in the Agent runtime
Blueprints and DSLs (BC-02) Vision, service, module, test, security, pipeline, observability, integration, database, documentation blueprints; DSL studio; context maps; domain models Pack-owned intent model; validation is a capability of the blueprint module
Coordinators Phase control, routing, parallelism Pack workflow definitions over Agent runtime primitives
Templates (BC-14) BaseTemplate (Layer 2), Microservice, Worker, API Gateway (BFF), Library, API Library, AI Skills Library, Agent, Platform, Blazor Shell/MFE/Component, MAUI, Documentation, Marketing Site, Health Checks Aggregator, Identity and Authorization Server, SaaS Tenants/ProductsCatalog/Entitlements/Billing/Metering templates Real repositories; canonical ADR-00xx layering
Libraries ConnectSoft.Extensions.* (Layer 1): application model, domain/entity/persistence models, messaging, AI, MCP, SaaS, identity, telemetry and more Real NuGet packages via the ConnectSoft Azure Artifacts feed
Generation recipe (BC-15) Descriptor → generated projects (EntityModel, PersistenceModel, Migrations, ServiceModel REST/gRPC, MessagingModel) with preserved hand-authored projects; SaaS descriptors are imported into Service and Module blueprints and generated through the same recipe path (ADR-0025) Decided 2026-10-14

Current implementation

  • No Factory agent, skill or workflow is implemented. The AgentKit, Platform, Agents, OpenClaw and Workforce repositories are earlier, non-Factory experiments (user decision D19, 2026-10-09); their contents (100 agent entries, 84 skills, 42 README-only agent folders) are reference input, not pack assets.
  • Templates and libraries are real and composed through BaseTemplate pack/compose scripts and Azure Pipelines; DerechHaLev (nine services) is the production proof.
  • Five SaaS consumer repositories (all updated 2026-09-16) carry descriptors, schemas and regenerate.ps1; no script dispatches to a generator or emits the documented run record.
  • No generation pipeline, blueprint service or coordinator runtime exists; the "Foundation Agents MVP" and "First SaaS MVP" pages are archived worked examples.

Existing pages that belong to this pack

Platform design pages (2026-10-09, design plan P15)

Later capabilities

Folded from the former Template & Library Platform extension roadmap (no dates, no commitments). Principles retained: template-first, always (no ad-hoc code generation); capability over package (libraries declare what they do); immutable, reproducible versions; declarative compatibility rules; canonical events; multi-tenant and governed by default; reuse before regeneration.

Candidate Purpose Owner today
Multi-template composition plans (solution blueprints) as a managed aggregate; scaffold diff against live repositories for drift and re-scaffold preview; tenant/team template overlays without forking Generation at scale BC-15 (later)
Library vulnerability and advisory scanning, SBOM generation, license classification and policy enforcement across dependency closures Supply-chain assurance for templates and libraries BC-14 with Trust & Operations
Auto-opened re-scaffold pull requests for low-risk template upgrades; catalog re-indexing by capability and tag Template operations BC-14 / BC-24
Marketplace sync of catalog assets, partner-contributed templates and libraries, verified/certified badges, capability-driven discovery, usage-based ranking, premium templates gated by entitlements Distribution BC-27 / BC-28
Template-authoring agents that synthesize templates from recurring scaffold patterns and submit them through registration and validation Agents over the catalog Software Factory pack with evaluation gates

Domain-specific templates and additional agent roles remain directions from the archived roadmaps; the four agent specifications filled in this restructure (self-service portal builder, platform cost optimization, low-code API platform, feature-toggle edition manager) are Target roles the user confirmed as part of this pack on 2026-10-09 (D20).

Open questions

Q-01 (first verifiable outcome), Q-14 (delivery and support obligations for generated products), Q-22 (decided 2026-10-14, ADR-0025). R-02 closed by D19.