Skip to content

AIFACTORY-FEAT-114: Workflow definition: Delivery run

Generated from the architecture model

This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.

A design artefact, not a tracker

This backlog is generated from model/backlog/ and validated against the architecture model. No work item exists in any tracker, and no item carries a date, an estimate or an assignee (ADR-0029).

Epic Factory assets: workflow definitions, agents and skills · Increment I2 Deliver it · State elaborated · Route solution-architect · Build order 103 of 185 (Factory code)

The workflow definition delivery-run as a published asset: Evaluates a completed pipeline run's typed results, prepares the release manifest and requests the promotion; a production promotion waits for its approval. Deployment is a promotion, never a pipeline stage. It has 5 steps, names the agents deployment-orchestrator, devops-engineer, release-manager and the tools none, and is executed by WorkflowEngineService under Run Control.

Delivers —
Stubs —
Realizes workflows: delivery-run
adrs: ADR-0014, ADR-0017, ADR-0027
Requirements FR-05, FR-06, FUX-05, XL-10, XL-11
Depends on AIFACTORY-FEAT-189 AgentRegistryService: the publication path of releases from I2
Sources model/workflows/delivery-run.yaml

Scenarios to trace (5, catalog): SCN-delivery-run-001 ✓, SCN-delivery-run-002 ✓, SCN-delivery-run-003 ✓, SCN-delivery-run-004 ✓, SCN-delivery-run-005 ✓

AIFACTORY-US-077: The Delivery run workflow runs from its published definition

behavior · persona operator As an operator, I want the delivery run workflow to run from its published definition with the agents, tools and gates it declares, so that release manifests are produced the same way on every run, with evidence.

The integration PBI of the definition delivery-run. When PipelineExecutionService publishes PipelineRunCompleted in state Succeeded or PartiallySucceeded, WorkflowEngineService satisfies the required readiness member pipeline-results (artifact-v1, hashed on the commit) of the project scope, and the optional member pipeline-blueprint when a validated Pipeline Blueprint exists; it submits the run itself through SubmitRun of RunControlService with a service token that names the project and the bundle idempotency key (D131), so a repeated completion of the same pipeline run returns the existing run and a newer member version supersedes the open correlation. Run Control accepts the run and publishes RunAccepted; the engine loads the Published release the run pinned through AgentRegistryService and marks the five steps ready in the declared order: evaluate-results, gates-passed, prepare-release, request-promotion and approve-production, with the agents devops-engineer, release-manager and deployment-orchestrator on their pinned releases. Deployment is a promotion and never a pipeline stage. Every step records exactly one outcome, the run reports exactly one outcome to Run Control (ADR-0014) and stays within the declared budget. Before any run, the definition release and the agent releases of its three agents, with any skill, tool or model profile release they need that is not yet Published, are submitted through SubmitRelease and published through PublishRelease of AgentRegistryService (feature agent-registry-service-publication); each publication is approved by a Reviewer who is not the submitter, a Platform admin for a model profile release, no evaluation verdict is required before I4, and the runs pin the Published release, never a Draft one (D140). The step behaviour is specified in AIFACTORY-US-1184 to AIFACTORY-US-1186; this PBI proves the chain on the recorded fixture.

Acceptance criteria

AC1 Given PipelineExecutionService/PipelineRunCompleted is published in state Succeeded or PartiallySucceeded for a project of the trusted tenant, when the readiness member pipeline-results is satisfied, then WorkflowEngineService/ReadinessRunSubmitted is emitted once, the run is submitted through RunControlService/SubmitRun with a service token naming the project (D131) and a repeated completion of the same pipeline run returns the existing run.
AC2 Given the Published release of delivery-run, submitted through AgentRegistryService/SubmitRelease and published through AgentRegistryService/PublishRelease after an approval by a Reviewer who is not the submitter (D140), with its 5 steps, input mappings, retry policies, timeouts, the idempotency_key of request-promotion and the when guard of approve-production exactly as in model/workflows/delivery-run.yaml, when RunControlService/RunAccepted arrives for a run that pinned it, then WorkflowEngineService/WorkflowRunStarted is emitted and delivery-run/evaluate-results, delivery-run/gates-passed, delivery-run/prepare-release, delivery-run/request-promotion and delivery-run/approve-production become ready in that order, each agent step on the pinned Published release of its agent, and no Draft release is loaded.
AC3 Given every step succeeds or the approval step is skipped by its guard, when the run completes, then release-manifest (release-manifest-v1) is the run output under the run envelope, WorkflowEngineService/WorkflowRunCompleted is emitted once and RunControlService/RunCompleted follows exactly once (ADR-0014).
AC4 Given the gate condition fails or a step spends its retry budget, when the engine applies the failure policy of that step, then WorkflowEngineService/WorkflowRunFailed names the step, RunControlService/RunFailed is published exactly once and no deployment runs outside a promotion (ADR-0017); given the promotion gate the production approval waits on is rejected or expires with no re-request left, then WorkflowEngineService/WorkflowRunFailed names approve-production and RunControlService/RunFailed is published exactly once (D121, D133).
AC5 Given the recorded fixture inputs of model/workflows/delivery-run.yaml, when the fixture run executes in the pipeline, then its outputs match the recorded ones field by field and the run stays within the declared budget (ADR-0024).
Traces: workflows delivery-run
Traces: steps delivery-run/evaluate-results, delivery-run/gates-passed, delivery-run/prepare-release, delivery-run/request-promotion, delivery-run/approve-production
Traces: agents deployment-orchestrator, devops-engineer, release-manager
Traces: services WorkflowEngineService, RunControlService, AgentRegistryService, PipelineExecutionService
Traces: apis RunControlService/SubmitRun, AgentRegistryService/SubmitRelease, AgentRegistryService/PublishRelease
Traces: events AgentRegistryService/AssetReleasePublished, PipelineExecutionService/PipelineRunCompleted, WorkflowEngineService/ReadinessRunSubmitted, WorkflowEngineService/WorkflowRunStarted, WorkflowEngineService/WorkflowRunCompleted, WorkflowEngineService/WorkflowRunFailed, RunControlService/RunAccepted, RunControlService/RunCompleted, RunControlService/RunFailed
Traces: descriptors workflow-definition-v1, readiness-bundle-v1, release-manifest-v1
Traces: adrs ADR-0014, ADR-0017, ADR-0024, ADR-0027
Traces: requirements FR-05, FR-06, FUX-05, XL-10, XL-11
Depends on AIFACTORY-US-1184, AIFACTORY-US-1185, AIFACTORY-US-1186, feature:pipeline-execution-service-complete, feature:workflow-engine-service, feature:run-control-service, feature:agent-registry-service-thin, feature:agent-registry-service-publication
Sources model/workflows/delivery-run.yaml, docs/planes/agent-runtime/workflow-definitions/delivery-run.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-272 Author, submit and publish the release of the workflow definition delivery-run with its agent releases implementation The release of delivery-run (workflow-definition-v1) authored with its 5 steps, input mappings, retry policies, timeouts, the failure policy of each agent and human step, the idempotency_key releaseId + targetEnvironment of request-promotion and the when guard of approve-production exactly as in model/workflows/delivery-run.yaml and accepted by ValidateWorkflowDefinition; it is submitted through SubmitRelease of AgentRegistryService together with the agent releases deployment-orchestrator, devops-engineer and release-manager of AIFACTORY-TASK-273 and any skill, tool or model profile release of their closure that is not yet Published, each publication is approved, through the approval that RunControlService opens with the subject kind asset-release, by a Reviewer who is not the submitter (a Platform admin for a model profile release), and each release is published through PublishRelease with the alias latest moved to it (feature agent-registry-service-publication, D140); no evaluation verdict is required before I4, and the Published release ids are recorded for the fixture run, which pins them. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService
AIFACTORY-TASK-273 Author the agent releases deployment-orchestrator, devops-engineer, release-manager with their prompts and skills implementation Draft releases of deployment-orchestrator, devops-engineer and release-manager with their instructions, the skills devops-engineer-evaluate-results, release-manager-prepare-release and deployment-orchestrator-request-promotion among their bound skills, tool bindings and model profiles of model/agents/devops-delivery/; each release passes a smoke run on a fixture input in the template tests and is submitted for publication by AIFACTORY-TASK-272, and no evaluation verdict of the suite devops-delivery-core-v1 is required for its publication before I4 (D140). ConnectSoft.AI.SoftwareFactory.AgentTemplate
AIFACTORY-TASK-274 Fixture run of delivery-run against recorded inputs verification The definition runs end to end on a fixture pipeline run in the acceptance environment from PipelineRunCompleted to RunCompleted on the Published releases of AIFACTORY-TASK-272; every step output validates against its descriptor and release-manifest matches the recorded one field by field (AC1 to AC3 and AC5 of AIFACTORY-US-077). ConnectSoft.AI.SoftwareFactory.WorkflowEngineService
AIFACTORY-TASK-726 Verify delivery-run-runs-from-its-definition by running the declared command verification Run dotnet test -c Release --filter Category=WorkflowFixture; it passes and proves AC1 to AC5 of AIFACTORY-US-077, including both failure paths of AC4 (WorkflowRunFailed then RunFailed exactly once for a failed gate or step, and for a rejected or expired promotion gate the production approval waits on); the output names the Published release ids of delivery-run, deployment-orchestrator, devops-engineer and release-manager that the run pinned, as AgentRegistryService/GetRelease reports them with their approval by a Reviewer who is not the submitter (D140). ConnectSoft.AI.SoftwareFactory.WorkflowEngineService

AIFACTORY-US-1184: The DevOps Engineer evaluates the typed pipeline results and the run stops on any blocking failure

behavior · persona operator As an operator, I want the typed results of a completed pipeline run evaluated and the run stopped when a blocking failure exists, so that no release manifest is prepared for a build whose tests, scans or quality gates block it.

The first agent step and the gate condition of delivery-run. When the engine marks evaluate-results ready it resolves pipeline-results from input.pipeline-results (artifact-v1) and pipeline-blueprint from input.pipeline-blueprint (blueprint-pipeline-v1, optional); the devops-engineer release runs the skill devops-engineer-evaluate-results in read class with read tools only. It reads tests, scans and quality gates as typed results, names each blocking failure and writes evaluation (artifact-v1) with the field blocking, the count of blocking failures. The step declares failure_policy Retry: a Failed attempt of failure class transient is retried under the exponential budget of 3 attempts with backoff 30s, any other failure class is not retried and a step that exceeds its timeout PT30M or spends the budget fails the run. When gates-passed becomes ready the engine evaluates steps.evaluate-results.evaluation.blocking == 0 over the recorded output without calling any service; the condition never retries and completes within PT1M. When it holds the step completes with one outcome and prepare-release becomes ready. When it does not hold the definition declares no branch, so the engine fails the run with the evaluation as its evidence: WorkflowRunFailed names gates-passed, no manifest is prepared and no promotion is requested. A missing or unreadable evaluation fails the condition with evidence instead of being read as passed.

Acceptance criteria

AC1 Given a run accepted with pipeline-results and an optional pipeline-blueprint, when devops-engineer executes delivery-run/evaluate-results, then evaluation (artifact-v1) is recorded once under the run envelope with the count blocking and every blocking failure named by its typed result (SCN-delivery-run-001).
AC2 Given an attempt of delivery-run/evaluate-results settles Failed with failure class transient until the exponential budget of 3 attempts is spent, settles Failed with any other failure class, or exceeds its timeout PT30M, when Run Control settles the step through RunControlService/StepSettled, then the engine reports WorkflowEngineService/WorkflowRunFailed naming the step and no shared system is changed (SCN-delivery-run-001).
AC3 Given the recorded evaluation has blocking 0, when the engine evaluates delivery-run/gates-passed, then the condition completes with one outcome, no service is called and delivery-run/prepare-release becomes ready (SCN-delivery-run-002).
AC4 Given the recorded evaluation has blocking above 0, or the evaluation is missing or unreadable, or the evaluation exceeds PT1M, when the engine evaluates delivery-run/gates-passed, then the condition is not retried, WorkflowEngineService/WorkflowRunFailed names gates-passed with the evaluation as evidence and no release manifest or promotion request exists for the run (SCN-delivery-run-002, ADR-0014).
Traces: workflows delivery-run
Traces: steps delivery-run/evaluate-results, delivery-run/gates-passed
Traces: agents devops-engineer
Traces: services WorkflowEngineService
Traces: events WorkflowEngineService/StepReady, WorkflowEngineService/WorkflowRunFailed, RunControlService/StepSettled
Traces: descriptors artifact-v1, blueprint-pipeline-v1
Traces: scenarios SCN-delivery-run-001, SCN-delivery-run-002
Traces: adrs ADR-0014
Traces: requirements FR-05, XL-10
Depends on feature:workflow-engine-service, feature:run-control-service
Sources model/workflows/delivery-run.yaml, model/skills/devops-delivery/devops-engineer-evaluate-results.yaml, model/scenarios/delivery-run.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-4728 Bind the evaluate-results skill and the blocking count of its output implementation The step evaluate-results of the Draft release runs devops-engineer-evaluate-results with pipeline-results and pipeline-blueprint mapped as in model/workflows/delivery-run.yaml and returns evaluation with the field blocking that the condition gates-passed reads. ConnectSoft.AI.SoftwareFactory.AgentTemplate
AIFACTORY-TASK-4729 Fixture pipeline results with and without blocking failures fixture Two recorded pipeline results, one with every test, scan and quality gate passing and one with a blocking scan finding, each with the expected evaluation and blocking count, as the oracle of SCN-delivery-run-001 and SCN-delivery-run-002. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService
AIFACTORY-TASK-4730 Prove the evaluation and the gate condition on the fixture verification A fixture run proves SCN-delivery-run-001 and SCN-delivery-run-002 (AC1 to AC4 of AIFACTORY-US-1184); the passing results reach prepare-release, the blocking results fail the run at gates-passed with the evaluation as evidence, and the retry exhaustion of evaluate-results ends in WorkflowRunFailed. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService

AIFACTORY-US-1185: The Release Manager assembles the release manifest with its bill of materials and attestations

behavior · persona operator As an operator, I want a release manifest assembled from the evaluated pipeline results with the bill of materials and the attestations, so that the promotion request and the production decision refer to one exact release version.

The release preparation step of delivery-run. When gates-passed held, the engine marks prepare-release ready and resolves pipeline-results from input.pipeline-results and evaluation from steps.evaluate-results.evaluation. The release-manager release runs the skill release-manager-prepare-release in sandbox class with the tools knowledge-search, read-range and write-file: it assembles the release manifest of the build with its software bill of materials, its attestations and the evaluation it rests on, writes it in the isolated workspace and returns release-manifest (release-manifest-v1) as its step output, which is also the output of the run. This PBI delivers that step output and requests no approval. The definition names ReleaseService and emits ReleaseReady, but the bound skill holds no tool that reaches CreateProductRelease of ReleaseService; this is reported as an open question, and whether a product release record exists after this step is not asserted here. The step declares failure_policy Retry: a Failed attempt of failure class transient is retried under the exponential budget of 3 attempts with backoff 30s, an attempt of any other failure class is not retried, and a step that exceeds its timeout PT30M or spends its budget fails the run with the evidence, the workspace output staying in place and no shared system changed.

Acceptance criteria

AC1 Given delivery-run/gates-passed held, when the engine marks delivery-run/prepare-release ready, then pipeline-results and evaluation are resolved from the mappings of model/workflows/delivery-run.yaml and release-manager executes the step on its pinned release (SCN-delivery-run-003).
AC2 Given the step runs, when it returns release-manifest, then the output validates against release-manifest-v1, carries the bill of materials, the attestations and the reference of the evaluation, is recorded once under the run envelope and delivery-run/request-promotion becomes ready with it mapped as release (SCN-delivery-run-003).
AC3 Given an attempt exceeds its timeout PT30M, settles Failed with a non-transient failure class, or spends the exponential budget of 3 attempts, when Run Control settles the step, then WorkflowEngineService/WorkflowRunFailed names the step, no promotion is requested and no shared system is changed (SCN-delivery-run-003, ADR-0014).
Traces: workflows delivery-run
Traces: steps delivery-run/prepare-release
Traces: agents release-manager
Traces: services WorkflowEngineService
Traces: events WorkflowEngineService/WorkflowRunFailed
Traces: descriptors release-manifest-v1, artifact-v1
Traces: scenarios SCN-delivery-run-003
Traces: adrs ADR-0014
Traces: requirements FR-06, XL-11
Depends on AIFACTORY-US-1184, feature:workflow-engine-service
Sources model/workflows/delivery-run.yaml, model/skills/devops-delivery/release-manager-prepare-release.yaml, model/scenarios/delivery-run.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-4731 Bind the prepare-release skill and map the run output implementation The step prepare-release of the Draft release runs release-manager-prepare-release with pipeline-results and evaluation mapped as in model/workflows/delivery-run.yaml and returns release-manifest (release-manifest-v1), which is set as the run output. ConnectSoft.AI.SoftwareFactory.AgentTemplate
AIFACTORY-TASK-4732 Fixture expected release manifest fixture The expected release-manifest of the fixture build with its bill of materials, attestations and evaluation reference, as the oracle of SCN-delivery-run-003. ConnectSoft.AI.SoftwareFactory.AgentTemplate
AIFACTORY-TASK-4733 Prove the release preparation step on the fixture verification A fixture run proves SCN-delivery-run-003 (AC1 to AC3 of AIFACTORY-US-1185); the manifest validates against release-manifest-v1 and is recorded once, and the timeout path ends in WorkflowRunFailed with no promotion requested. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService

AIFACTORY-US-1186: The Deployment Orchestrator requests the promotion and a production target waits for its approval

behavior · persona reviewer As a reviewer of the project, I want a promotion into production to wait for my decision on the exact release version, while lower environments proceed without me, so that production changes only on a decision that someone other than the requester took.

The promotion request and the production approval of delivery-run. When prepare-release succeeded the engine marks request-promotion ready and resolves release from steps.prepare-release.release-manifest. The deployment-orchestrator release runs the skill deployment-orchestrator-request-promotion in shared-write class and requests the promotion of the release to the next environment through EnvironmentPromotionService with the tool deploy-environment, then returns promotion-request (artifact-v1) with the target environment and the flag isProduction. The step declares failure_policy Retry with idempotency_key releaseId + targetEnvironment, so a Failed attempt of failure class transient is retried under the exponential budget of 3 attempts and never creates a second promotion (D114); an Uncertain attempt is never retried automatically and goes to an operator decision of the project (D119). approve-production carries the guard steps.request-promotion.promotion-request.isProduction == true: for a lower environment the engine records it Skipped and the run completes (ADR-0027). For production a person gives one production approval: the approval gate of the promotion that request-promotion opened, bound to the release id and the production environment (D133). The engine opens no approval of its own; the step declares waits_on that gate, which requests the approval through RequestApproval of RunControlService with the service identity of EnvironmentPromotionService, the subject kind promotion and the promotion id as subject id, of action class production, with the approver rule role Reviewer in project scope, where the requester never decides (ADR-0015, D18, D135). An approving ApprovalDecided that names the gate for that release id and environment completes the step; a rejection, an expiry the on-expiry rule does not re-request, or the timeout P7D ends the promotion Rejected and fails the step under failure_policy Fail, so the engine reports WorkflowRunFailed naming approve-production and Run Control publishes RunFailed once (D121). A promotion that EnvironmentPromotionService refuses or ends Rejected at a gate other than the approval, because the release is not Ready there or a gate fails, fails request-promotion with failure class permanent and is not retried; a request without a strategy is refused with 422 (D135). deploy-environment is production class inside a shared-write step; whether that class mismatch is allowed is reported as an open question, so AC1 asserts the promotion request for a non-production target and AC4 the gate a production request opens.

Acceptance criteria

AC1 Given steps.prepare-release.release-manifest is recorded and the next environment of the promotion path is a non-production environment, when deployment-orchestrator executes delivery-run/request-promotion, then the promotion is requested once through EnvironmentPromotionService/Promotions.Request, EnvironmentPromotionService/PromotionRequested names the run, and promotion-request (artifact-v1) with the target environment and isProduction is recorded once under the run envelope (SCN-delivery-run-004).
AC2 Given an attempt of delivery-run/request-promotion settles Failed with failure class transient, when Run Control evaluates the step, then it is retried under the exponential budget of 3 attempts because the shared-write step declares idempotency_key releaseId + targetEnvironment and no second promotion is created; given it settles Uncertain, then it is not retried and the run waits for an operator decision; given the release is not Ready in ReleaseService or a gate fails, then the promotion is refused or ends Rejected, promotion-request records the refusal and the step fails with failure class permanent without a retry; on exhaustion or refusal WorkflowEngineService/WorkflowRunFailed names the step (SCN-delivery-run-004, D114).
AC3 Given isProduction is false, when the engine reaches delivery-run/approve-production, then the step is recorded Skipped, no RunControlService/ApprovalRequested is published and the run completes (SCN-delivery-run-005, ADR-0027).
AC4 Given isProduction is true, when delivery-run/approve-production becomes ready, then the engine opens no approval request of its own, RunControlService/ApprovalRequested is published only for the promotion gate that request-promotion opened, with the subject kind promotion, action class production, the binding to the release id and the production environment and the approver rule role Reviewer that excludes the requester, and the step waits until RunControlService/ApprovalDecided names that gate (SCN-delivery-run-005, ADR-0015, D133).
AC5 Given the gate is rejected, expires with no re-request left, or the step reaches P7D without a decision, when the outcome is recorded, then the promotion ends Rejected, delivery-run/approve-production fails under failure_policy Fail, WorkflowEngineService/WorkflowRunFailed names approve-production, RunControlService/RunFailed is published exactly once and nothing is deployed to production (SCN-delivery-run-005, D121, D133).
Traces: workflows delivery-run
Traces: steps delivery-run/request-promotion, delivery-run/approve-production
Traces: agents deployment-orchestrator
Traces: services WorkflowEngineService, RunControlService, EnvironmentPromotionService
Traces: aggregates RunControlService/ApprovalRequest, EnvironmentPromotionService/Promotion
Traces: apis EnvironmentPromotionService/Promotions.Request
Traces: events EnvironmentPromotionService/PromotionRequested, RunControlService/ApprovalRequested, RunControlService/ApprovalDecided, RunControlService/RunFailed, WorkflowEngineService/WorkflowRunFailed
Traces: descriptors release-manifest-v1, artifact-v1, approval-request-v1
Traces: scenarios SCN-delivery-run-004, SCN-delivery-run-005
Traces: adrs ADR-0014, ADR-0015, ADR-0017, ADR-0027
Traces: requirements FR-06, FUX-05, XL-11
Depends on AIFACTORY-US-1185, feature:environment-promotion-service, feature:workflow-engine-service, feature:run-control-service
Sources model/workflows/delivery-run.yaml, model/skills/devops-delivery/deployment-orchestrator-request-promotion.yaml, model/tools/deploy-environment.yaml, model/services/devops-gitops/EnvironmentPromotionService.yaml, model/scenarios/delivery-run.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-4734 Bind the request-promotion skill, its idempotency key and the guarded approval block implementation The step request-promotion of the Draft release runs deployment-orchestrator-request-promotion with release mapped from steps.prepare-release.release-manifest and the idempotency_key releaseId + targetEnvironment, and approve-production carries the when guard and waits on the promotion gate of EnvironmentPromotionService with subject kind promotion, bound to the release id and the production environment, opening no approval of its own, exactly as model/workflows/delivery-run.yaml declares. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService
AIFACTORY-TASK-4735 Fixture promotion requests to a test and a production environment fixture Two recorded promotion requests, one to a test environment with isProduction false and one to production with isProduction true, with the expected Skipped approval step and the expected ApprovalRequested of the promotion gate bound to the release id and the production environment, plus a request for a release that is not Ready with its expected refusal, as the oracle of SCN-delivery-run-004 and SCN-delivery-run-005. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService
AIFACTORY-TASK-4736 Prove the promotion request and the production approval on the fixture verification A fixture run proves SCN-delivery-run-004 and SCN-delivery-run-005 (AC1 to AC5 of AIFACTORY-US-1186); one promotion per release and target under transient retries, an Uncertain attempt waiting for an operator decision, a refused promotion that fails the step without a retry, the skipped approval for a test target, and the approve path for production with no approval opened by the engine, the requester refused as decider and the reject and expire paths ending in WorkflowRunFailed naming approve-production and RunFailed once. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService