Skip to content

Template & Library — workflows

Target

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

W1 — A blueprint is validated, derived and published

sequenceDiagram
    participant U as Requester / agent
    participant B as BlueprintService
    participant AS as ArtifactService
    participant AR as AgentRegistryService
    U->>B: CreateBlueprintVersion (service blueprint document)
    B->>AS: store document, validators → ArtifactValidated
    B->>B: schema + rules, derive context map and domain models
    B-)U: BlueprintValidated (report with rule ids)
    U->>B: SubmitBlueprint
    B->>AR: release candidate (blueprint asset)
    AR-)B: AssetReleasePublished → Published
Hold "Alt" / "Option" to enable pan & zoom

W2 — The catalog discovers a template version

Every six hours the Discoverer reads each template repository through the Azure DevOps or GitHub connector and each feed, pins new manifests by hash, and the CompatibilityComputer fills matrix cells with evidence from pipeline builds and conformance runs; a Verified version is submitted to Asset Publication by an Asset maintainer and becomes a Published template release.

W3 — A recipe is proposed, validated and approved

flowchart LR
    BP[BlueprintPublished + derived models] --> PP[PlanProposer · modules per context · templates · libraries]
    PP --> D[Draft recipe]
    D --> V{ValidateRecipe · manifests · switches · matrix evidence}
    V -- findings --> D
    V -- passed --> VAL[Validated]
    VAL --> AP[ApproveRecipe · Requester or Reviewer per policy]
    AP --> APPR[Approved · immutable]
Hold "Alt" / "Option" to enable pan & zoom

W4 — A generation run executes the recipe

sequenceDiagram
    participant R as GenerationRecipeService
    participant RC as RunControlService
    participant A as Agent attempt (backend generator)
    participant T as Tool executor (shell-sandbox, write-file, propose-change-set)
    participant P as PipelineExecutionService
    R-)RC: RecipeApproved → run submitted (workflow: generate-product)
    A->>R: GetApprovedRecipe
    A->>T: dotnet new <template> per module in the sandbox, fill from the domain model
    A->>T: propose-change-set (branch, pull request)
    A->>R: RecordOutput per module (files, hashes, template version, manifest hash)
    P-)R: ChangeProposalMerged → commit linked
    RC-)R: RunCompleted → GenerationCompleted
Hold "Alt" / "Option" to enable pan & zoom

W5 — A template release offers a re-scaffold

TemplateVersionPublished offers a new recipe version pinning the new template version; validation reports which modules change; approval and a generation run follow W3 and W4, and the fleet platform's re-scaffold rollout moves operated products once the resulting release is ready (P12).

W6 — Recovery

Manifests re-read from repositories, compatibility recomputed from evidence, blueprints and recipes restored from backup (RPO 15 min) with their artifacts in the artifact store; provenance records are also mirrored in audit evidence.