Skip to content

AIFACTORY-FEAT-113: Workflow definition: Project bootstrap

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 102 of 185 (Factory code)

The workflow definition project-bootstrap as a published asset: Creates the system-of-record project, repositories, pipelines and boards for a new Factory project through connectors, under one shared-write approval, and records the trace scaffolding. It has 5 steps, names the agents devops-engineer and the tools propose-change-set, and is executed by WorkflowEngineService under Run Control.

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

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

AIFACTORY-US-021: A new project gets its bootstrap change proposal and trace scaffolding under one approval

behavior · persona workspace-admin As a workspace administrator, I want the repositories, pipeline definitions and boards of a new project proposed to the system of record as one approved change set, with its trace scaffolding recorded, so that delivery starts from a proposal that matches the plan and that nobody assembled by hand.

The integration PBI of the definition project-bootstrap. When ProjectService publishes ProjectCreated with a key, WorkflowEngineService satisfies the one required readiness member project (execution-scope-v1) of the project scope, computes the bundle fingerprint and submits the run itself through SubmitRun of RunControlService with a service token that names the project, the idempotency key {scope}:{operation}:{workflowReleaseId}:{bundleFingerprint} and the release alias latest resolved when the correlation opens (D131). The same key returns the existing run, so a repeated ProjectCreated never starts a second bootstrap; 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: plan-bootstrap, scaffold-resources, approve-shared-write, apply-bootstrap and record-trace. Agent steps run the devops-engineer release, the tool step calls propose-change-set and the human step is the one shared-write approval of the run. Every step records exactly one outcome under the run envelope, the run reports exactly one outcome to Run Control (ADR-0014) and stays within the declared budget of model/workflows/project-bootstrap.yaml. The definition says the resources are created, but the bound tool propose-change-set only opens a pull request; creating repositories, pipelines and boards has no modelled operation, so this PBI promises the change proposal and the trace scaffolding only and the creation is reported as an open question. Before any run, the definition release and the agent release of devops-engineer, 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 behaviour of the steps is specified in AIFACTORY-US-1181 to AIFACTORY-US-1183; this PBI proves the whole chain on the recorded fixture.

Acceptance criteria

AC1 Given ProjectService/ProjectCreated is published with a key for a project of the trusted tenant, when the readiness member project is satisfied, then WorkflowEngineService/ReadinessSatisfied and WorkflowEngineService/ReadinessRunSubmitted are emitted once, the run is submitted through RunControlService/SubmitRun with a service token naming the project (D131) and the bundle idempotency key, and a repeated ProjectCreated for the same project returns the existing run instead of a second one.
AC2 Given the Published release of project-bootstrap, 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 and the failure policy each step declares exactly as in model/workflows/project-bootstrap.yaml, when RunControlService/RunAccepted arrives for a run that pinned it, then WorkflowEngineService/WorkflowRunStarted is emitted and the steps project-bootstrap/plan-bootstrap, project-bootstrap/scaffold-resources, project-bootstrap/approve-shared-write, project-bootstrap/apply-bootstrap and project-bootstrap/record-trace become ready in that order, each agent step on the pinned Published release of devops-engineer, and no Draft release is loaded.
AC3 Given every step succeeds, when the run completes, then the opened change proposal bootstrap-change-proposal (pull-request-proposal-v1) and trace-scaffolding (artifact-v1) are the run outputs under the run envelope, WorkflowEngineService/WorkflowRunCompleted is emitted once and RunControlService/RunCompleted follows exactly once (ADR-0014); no repository, pipeline or board is asserted as created beyond the opened proposal.
AC4 Given a step fails after its retry budget, the apply step fails before its effect is confirmed, or record-trace fails after the confirmed apply and the compensation of apply-bootstrap runs, when the engine applies the failure policy of that step, then WorkflowEngineService/WorkflowRunFailed names the failed step and RunControlService/RunFailed is published exactly once (ADR-0014, D133); given the approval is rejected or expires with no re-request left, then Run Control moves the run from WaitingForApproval to Failed (ApprovalRejectedOrExpired) and publishes RunControlService/RunFailed exactly once, the engine closes its projection on RunFailed and publishes no WorkflowEngineService/WorkflowRunFailed (D119, D121), and nothing is written to the system of record.
AC5 Given the recorded fixture inputs of model/workflows/project-bootstrap.yaml, when the fixture run executes in the pipeline, then its outputs match the recorded ones field by field, every step output validates against its descriptor and the run stays within the declared budget (ADR-0024).
Traces: services WorkflowEngineService, RunControlService, AgentRegistryService, ProjectService, ToolAdapterService
Traces: workflows project-bootstrap
Traces: steps project-bootstrap/plan-bootstrap, project-bootstrap/scaffold-resources, project-bootstrap/approve-shared-write, project-bootstrap/apply-bootstrap, project-bootstrap/record-trace
Traces: agents devops-engineer
Traces: tools propose-change-set
Traces: apis RunControlService/SubmitRun, AgentRegistryService/SubmitRelease, AgentRegistryService/PublishRelease
Traces: events AgentRegistryService/AssetReleasePublished, ProjectService/ProjectCreated, WorkflowEngineService/ReadinessSatisfied, WorkflowEngineService/ReadinessRunSubmitted, WorkflowEngineService/WorkflowRunStarted, WorkflowEngineService/WorkflowRunCompleted, WorkflowEngineService/WorkflowRunFailed, RunControlService/RunAccepted, RunControlService/RunCompleted, RunControlService/RunFailed
Traces: descriptors workflow-definition-v1, readiness-bundle-v1, execution-scope-v1, pull-request-proposal-v1, artifact-v1
Traces: adrs ADR-0014, ADR-0024, ADR-0027
Traces: requirements FR-05, FR-06, FR-08, FUX-05, XL-01, XL-10
Depends on AIFACTORY-US-1181, AIFACTORY-US-1182, AIFACTORY-US-1183, feature:project-service, feature:workflow-engine-service, feature:run-control-service, feature:agent-registry-service-thin, feature:agent-registry-service-publication
Sources model/workflows/project-bootstrap.yaml, model/agents/devops-delivery/devops-engineer.yaml, docs/planes/agent-runtime/workflow-definitions/project-bootstrap.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-314 Readiness start on a created project implementation The readiness bundle of project-bootstrap is satisfied by ProjectCreated with a key, the run is submitted through SubmitRun with a service token naming the project and the bundle idempotency key, and a repeated ProjectCreated returns the existing run (AC1 of AIFACTORY-US-021). ConnectSoft.AI.SoftwareFactory.WorkflowEngineService
AIFACTORY-TASK-269 Author, submit and publish the release of the workflow definition project-bootstrap with its agent release implementation The release of project-bootstrap (workflow-definition-v1) authored with its 5 steps, input mappings, retry policies, timeouts, the failure policy each step declares (Retry on the agent steps, Fail on approve-shared-write, Compensate on apply-bootstrap with its compensation) and the approval block of the human step exactly as in model/workflows/project-bootstrap.yaml and accepted by ValidateWorkflowDefinition; it is submitted through SubmitRelease of AgentRegistryService together with the agent release devops-engineer of AIFACTORY-TASK-270 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-270 Author the agent release devops-engineer with its prompts and skills implementation A Draft release of devops-engineer with its instructions, the skills devops-engineer-plan-bootstrap, devops-engineer-scaffold-resources and devops-engineer-record-trace among its bound skills, the tool bindings and the model profile of model/agents/devops-delivery/devops-engineer.yaml; the release passes a smoke run on a fixture project in the template tests and is submitted for publication by AIFACTORY-TASK-269, 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-271 Fixture run of project-bootstrap against recorded inputs verification The definition runs end to end on a fixture project in the acceptance environment from ProjectCreated to RunCompleted on the Published releases of AIFACTORY-TASK-269; every step output validates against its descriptor and the run outputs match the recorded ones field by field (AC2, AC3 and AC5 of AIFACTORY-US-021). ConnectSoft.AI.SoftwareFactory.WorkflowEngineService
AIFACTORY-TASK-735 Verify bootstrap-project-resources by running the declared command verification Run dotnet test -c Release --filter Category=WorkflowFixture; it passes and proves AC1 to AC5 of AIFACTORY-US-021, including both failure paths of AC4 (WorkflowRunFailed then RunFailed exactly once for a failed step, RunFailed alone for a rejected or expired approval); the output names the Published release ids of project-bootstrap and devops-engineer 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-1181: The DevOps Engineer plans the bootstrap and scaffolds the resources in the run's isolated workspace

behavior · persona workspace-admin As a workspace administrator, I want the repositories, pipelines and boards my project needs planned and scaffolded before anything is written to the system of record, so that the reviewer decides on one exact change set that nothing outside the run has touched.

The first two agent steps of project-bootstrap. When the engine marks plan-bootstrap ready it resolves project from input.project (execution-scope-v1) and system-of-record-connection from input.system-of-record-connection (artifact-v1, optional); the devops-engineer release runs the skill devops-engineer-plan-bootstrap in read class with read tools only and writes one artifact, bootstrap-plan (artifact-v1), naming every repository, pipeline definition and board the project needs from its edition and the capabilities of the connection, with lineage to the project scope. When scaffold-resources becomes ready it receives project and bootstrap-plan from steps.plan-bootstrap.bootstrap-plan; the skill devops-engineer-scaffold-resources writes repository layouts, pipeline files and board templates in sandbox class inside the run's isolated workspace with apply-patch, write-file, shell-sandbox and build-and-test, and returns change-set (change-set-v1) with its diff reference and hash. Neither step touches the system of record or needs an approval. Both declare 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 while no shared system has changed.

Acceptance criteria

AC1 Given a run accepted with project and an optional system-of-record-connection, when the engine marks project-bootstrap/plan-bootstrap ready and devops-engineer executes it, then bootstrap-plan (artifact-v1) is recorded once under the run envelope, names every repository, pipeline definition and board with lineage to the project, and project-bootstrap/scaffold-resources becomes ready (SCN-project-bootstrap-001).
AC2 Given steps.plan-bootstrap.bootstrap-plan is recorded, when project-bootstrap/scaffold-resources runs in the isolated workspace, then change-set (change-set-v1) is recorded once with its diff reference and hash, every planned resource has its scaffold in the change set and nothing is written to the system of record (SCN-project-bootstrap-002).
AC3 Given an attempt of either step 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, the sandbox output stays in place as evidence and no shared system is changed (SCN-project-bootstrap-001, SCN-project-bootstrap-002, ADR-0014).
Traces: workflows project-bootstrap
Traces: steps project-bootstrap/plan-bootstrap, project-bootstrap/scaffold-resources
Traces: agents devops-engineer
Traces: services WorkflowEngineService
Traces: events WorkflowEngineService/StepReady, WorkflowEngineService/WorkflowRunFailed, RunControlService/StepSettled
Traces: descriptors execution-scope-v1, artifact-v1, change-set-v1
Traces: scenarios SCN-project-bootstrap-001, SCN-project-bootstrap-002
Traces: adrs ADR-0014
Traces: requirements FR-05
Depends on feature:workflow-engine-service, feature:run-control-service
Sources model/workflows/project-bootstrap.yaml, model/skills/devops-delivery/devops-engineer-plan-bootstrap.yaml, model/skills/devops-delivery/devops-engineer-scaffold-resources.yaml, model/scenarios/project-bootstrap.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-315 Plan and scaffold in the isolated workspace implementation The devops-engineer skills devops-engineer-plan-bootstrap and devops-engineer-scaffold-resources produce the bootstrap plan (artifact-v1) and the change set (change-set-v1) of repository, pipeline and board files in the sandbox workspace, with the input mappings of model/workflows/project-bootstrap.yaml. ConnectSoft.AI.SoftwareFactory.AgentTemplate
AIFACTORY-TASK-4721 Recorded fixture of a project scope with its expected plan and change set fixture A fixture project scope and connection with the expected bootstrap plan naming each repository, pipeline definition and board, and the expected change set with its hash, as the oracle of SCN-project-bootstrap-001 and SCN-project-bootstrap-002. ConnectSoft.AI.SoftwareFactory.AgentTemplate
AIFACTORY-TASK-4722 Prove the plan and scaffold steps on the fixture verification A fixture run proves SCN-project-bootstrap-001 and SCN-project-bootstrap-002 (AC1 to AC3 of AIFACTORY-US-1181), including the transient retry to exhaustion and the WorkflowRunFailed that names the step with no shared system changed. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService

AIFACTORY-US-1182: A reviewer approves the exact change set and only then is the change proposal opened through the connector

behavior · persona reviewer As a reviewer of the project, I want to decide on the exact change set that will create the project's resources, and see it applied only after my decision, so that no repository, pipeline or board appears in the system of record without a decision bound to what is written.

The human step and the tool step of project-bootstrap. When approve-shared-write becomes ready the engine emits StepReady for a Human step, with action class shared-write and no task contract; Run Control opens an approval request whose subject is the run and the step, of action class shared-write and proposal kind diff, with the hash of steps.scaffold-resources.change-set as proposal hash and the approver rule role Reviewer in project scope, where the requester of the run never decides (ADR-0015, D18, D129). ApprovalRequested is published, the run waits WaitingForApproval and the engine projection WaitingForHuman. An approving ApprovalDecided bound to that hash completes the step; on a rejection, or an expiry without a re-request left, Run Control moves the run from WaitingForApproval to Failed (ApprovalRejectedOrExpired) and publishes RunFailed exactly once, and the engine closes its projection on RunFailed without WorkflowRunFailed (D119, D121), with nothing written; a regenerated change set makes the pending request Stale. Until I4 this approval always runs; from I4 the step carries a policy guard: before the approval opens the engine asks PolicyEngineService with the action kind tool-invocation and the action class shared-write over the change set, an answer allow records the step run Skipped and opens no approval, and any other answer opens it (D133); this PBI asserts the I2 behaviour, where the approval always runs. The definition says the step creates the resources, but the bound tool only opens a pull request; creating repositories, pipelines and boards has no modelled operation and is reported as an open question. When apply-bootstrap becomes ready the tool propose-change-set receives change-set from steps.scaffold-resources.change-set and, through ToolAdapterService under the run's workload identity, pushes the branch and opens the pull request through the connection, IntegrationService with the credential the Secret Broker issues, auditing repository, branch, changeSetHash and pullRequestRef; it then records the proposal with Pipelines.RecordProposal of PipelineExecutionService (change-proposal-record-v1, scope factory.delivery.propose), which carries the run, the attempt, the agent release, the pull-request reference and the tool receipt, and the proposal starts in PullRequestOpen (D135). The output bootstrap-change-proposal (pull-request-proposal-v1) is recorded once. The step is shared-write with failure_policy Compensate and no idempotency key, so a Failed attempt is never retried although the definition declares a fixed budget of 2 attempts. Its own compensation runs only after its effect is confirmed (D133), so a Failed attempt, whose proposal was never confirmed, withdraws nothing: the step fails, CompensationStarted finds no confirmed effect to compensate and the run ends Failed. An Uncertain attempt goes to an operator decision of the project (D119).

Acceptance criteria

AC1 Given project-bootstrap/scaffold-resources succeeded in an increment before I4, when project-bootstrap/approve-shared-write becomes ready, then the approval always runs: RunControlService/ApprovalRequested is published for the run and the step with action class shared-write, proposal kind diff, the change-set hash as proposal hash and the approver rule role Reviewer with separation of duties, and the run waits WaitingForApproval (SCN-project-bootstrap-003, ADR-0015, D129, D133).
AC2 Given the pending request, when RunControlService/ApprovalDecided records an approval bound to that hash, then the step completes with one outcome and project-bootstrap/apply-bootstrap becomes ready; when it records a rejection, or the request expires and the on-expiry rule leaves no re-request, then Run Control moves the run from WaitingForApproval to Failed (ApprovalRejectedOrExpired) and publishes RunControlService/RunFailed exactly once; the engine hears RunFailed, moves its projection from WaitingForHuman to Failed and its open step runs to Cancelled, and publishes no WorkflowEngineService/WorkflowRunFailed (D119, D121); nothing is written to the system of record (SCN-project-bootstrap-003).
AC3 Given the approval holds, when propose-change-set runs for project-bootstrap/apply-bootstrap, then the pull request is opened through the connection with the credential the Secret Broker issues, the audit record carries repository, branch, changeSetHash and pullRequestRef, the proposal is recorded once through PipelineExecutionService/Pipelines.RecordProposal in PullRequestOpen with the run, the attempt, the agent release, the pull-request reference and the tool receipt, and bootstrap-change-proposal (pull-request-proposal-v1) is recorded once under the run envelope (SCN-project-bootstrap-004, D135).
AC4 Given an attempt of project-bootstrap/apply-bootstrap settles Failed or exceeds its timeout PT30M, when Run Control settles the step, then it is not retried because the shared-write step declares no idempotency key, the engine emits WorkflowEngineService/CompensationStarted, no proposal is withdrawn because the effect of the step was never confirmed, and the run ends Failed with WorkflowEngineService/WorkflowRunFailed naming apply-bootstrap; given the attempt settles Uncertain, then ToolAdapterService/ToolEffectUncertain is emitted and the step waits for an operator decision (SCN-project-bootstrap-004, ADR-0014, D133).
Traces: workflows project-bootstrap
Traces: steps project-bootstrap/approve-shared-write, project-bootstrap/apply-bootstrap
Traces: tools propose-change-set
Traces: services WorkflowEngineService, RunControlService, ToolAdapterService, PipelineExecutionService
Traces: aggregates RunControlService/ApprovalRequest
Traces: apis PipelineExecutionService/Pipelines.RecordProposal
Traces: events WorkflowEngineService/StepReady, WorkflowEngineService/CompensationStarted, WorkflowEngineService/WorkflowRunFailed, RunControlService/ApprovalRequested, RunControlService/ApprovalDecided, RunControlService/RunFailed, ToolAdapterService/ToolEffectUncertain
Traces: descriptors change-set-v1, pull-request-proposal-v1, change-proposal-record-v1, approval-request-v1
Traces: scenarios SCN-project-bootstrap-003, SCN-project-bootstrap-004
Traces: adrs ADR-0014, ADR-0015
Traces: requirements FR-06, XL-10
Depends on AIFACTORY-US-1181, feature:workflow-engine-service, feature:run-control-service, feature:tool-adapter-service, feature:integration-service-thin, feature:connector-registry-service-thin, feature:secret-broker-service, feature:pipeline-execution-service-thin
Sources model/workflows/project-bootstrap.yaml, model/tools/propose-change-set.yaml, model/services/control-plane/RunControlService.yaml, model/scenarios/project-bootstrap.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-4723 Bind the approval block and the compensation of the bootstrap steps in the Draft release implementation The human step approve-shared-write carries action class shared-write, proposal kind diff, proposal from steps.scaffold-resources.change-set, the approver rule, the stale rule and the policy guard that applies from I4, apply-bootstrap carries failure policy Compensate with its compensation, and record-trace carries failure policy Compensate, exactly as model/workflows/project-bootstrap.yaml declares. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService
AIFACTORY-TASK-316 Approved apply through the connector with receipts verification The propose-change-set invocation of apply-bootstrap runs only after the approval bound to the change-set hash, writes the audit fields of model/tools/propose-change-set.yaml, records the proposal once through Pipelines.RecordProposal in PullRequestOpen and yields one bootstrap-change-proposal per run; a rejected or expired approval writes nothing (SCN-project-bootstrap-003, SCN-project-bootstrap-004). ConnectSoft.AI.SoftwareFactory.ToolAdapterService
AIFACTORY-TASK-4724 Prove the approval and the apply paths on the fixture verification A fixture run proves SCN-project-bootstrap-003 and SCN-project-bootstrap-004 (AC1 to AC4 of AIFACTORY-US-1182) with an approving decision, a rejecting and an expiring decision that end in RunFailed without WorkflowRunFailed, a stale request after a regenerated change set, a Failed apply that is not retried and withdraws nothing, and an Uncertain apply that waits for an operator decision. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService

AIFACTORY-US-1183: The DevOps Engineer verifies the opened proposal and records the trace scaffolding of the project

behavior · persona workspace-admin As a workspace administrator, I want the result of the bootstrap verified and recorded as trace scaffolding with its receipts, so that every later run of the project can trace its work back to the resources the bootstrap created.

The last agent step of project-bootstrap. When apply-bootstrap succeeded the engine marks record-trace ready and resolves project from input.project and bootstrap-change-proposal from steps.apply-bootstrap.bootstrap-change-proposal. The devops-engineer release runs the skill devops-engineer-record-trace in read class with read tools only: it compares the opened proposal with the resources the project needs and writes trace-scaffolding (artifact-v1), the trace scaffolding of the project with the receipts of the apply, recorded once under the run envelope. The run then completes with bootstrap-change-proposal and trace-scaffolding as its outputs and Run Control records one Completed outcome. The step changes nothing in the system of record and requests no approval. It is read class and follows the effect of apply-bootstrap, so it declares failure_policy Compensate (D133): a Failed attempt of failure class transient is retried under the declared exponential budget of 3 attempts with backoff 30s, and an attempt that exceeds its timeout PT30M, fails with any other failure class or spends the budget fails the step. The engine then moves the run to Compensating (StepFailedWithCompensatePolicy) and emits CompensationStarted; the compensation of the confirmed apply-bootstrap runs, which withdraws the proposal and records the partial creation as a finding, and WorkflowRunFailed names record-trace with compensated true. No operation withdraws a recorded proposal, so the withdrawal itself is reported as an open question and this PBI asserts that the compensation is started for the confirmed apply and that the finding of the partial creation is recorded.

Acceptance criteria

AC1 Given project-bootstrap/apply-bootstrap succeeded, when the engine marks project-bootstrap/record-trace ready, then project and bootstrap-change-proposal are resolved from the mappings of model/workflows/project-bootstrap.yaml and devops-engineer executes the step on its pinned release (SCN-project-bootstrap-005).
AC2 Given the step runs, when it returns trace-scaffolding, then the output is recorded once under the run envelope with the producer run, attempt and agent and the run completes with WorkflowEngineService/WorkflowRunCompleted once (SCN-project-bootstrap-005, ADR-0014).
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 Failed, then the engine emits WorkflowEngineService/CompensationStarted, the compensation of the confirmed project-bootstrap/apply-bootstrap runs and records the partial creation as a finding, and WorkflowEngineService/WorkflowRunFailed names record-trace with compensated true (StepFailedWithCompensatePolicy, SCN-project-bootstrap-005, D133).
Traces: workflows project-bootstrap
Traces: steps project-bootstrap/record-trace, project-bootstrap/apply-bootstrap
Traces: agents devops-engineer
Traces: services WorkflowEngineService
Traces: events WorkflowEngineService/WorkflowRunCompleted, WorkflowEngineService/WorkflowRunFailed, WorkflowEngineService/CompensationStarted
Traces: descriptors artifact-v1, pull-request-proposal-v1
Traces: scenarios SCN-project-bootstrap-005
Traces: adrs ADR-0014
Traces: requirements FR-08, XL-01
Depends on AIFACTORY-US-1182, feature:artifact-service, feature:agent-runtime-service, feature:workflow-engine-service
Sources model/workflows/project-bootstrap.yaml, model/skills/devops-delivery/devops-engineer-record-trace.yaml, model/scenarios/project-bootstrap.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-4725 Bind the record-trace skill and map the run outputs implementation The step record-trace of the Draft release runs devops-engineer-record-trace with project and bootstrap-change-proposal mapped as in model/workflows/project-bootstrap.yaml, and the run outputs bootstrap-change-proposal and trace-scaffolding are set from the recorded step outputs. ConnectSoft.AI.SoftwareFactory.AgentTemplate
AIFACTORY-TASK-4726 Fixture expected trace scaffolding with its receipts fixture The expected trace-scaffolding artifact (artifact-v1) of the fixture run with its producer run and the receipts of the apply recorded once, and a failing verification with the expected compensation of the apply and its finding, as the oracle of SCN-project-bootstrap-005. ConnectSoft.AI.SoftwareFactory.AgentTemplate
AIFACTORY-TASK-4727 Prove the record step, the run completion and the compensation of the apply verification A fixture run proves SCN-project-bootstrap-005 (AC1 to AC3 of AIFACTORY-US-1183); trace-scaffolding recorded once, WorkflowRunCompleted and RunCompleted exactly once, and a timeout path that emits CompensationStarted, runs the compensation of apply-bootstrap with its finding of the partial creation and ends the run Failed with WorkflowRunFailed naming record-trace with compensated true. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService