Skip to content

AIFACTORY-FEAT-121: Workflow definition: Plan a 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 I4 Trust and accountability · State elaborated · Route solution-architect · Build order 140 of 185 (Factory code)

The workflow definition plan-run as a published asset: Turns an accepted run submission into a workflow-definition instance: classifies the intent, selects a Published definition or composes a plan validated against the DSL, and hands the first steps to the engine. It has 5 steps, names the agents factory-workflow-orchestrator and the tools knowledge-search, and is executed by WorkflowEngineService under Run Control.

Delivers —
Stubs —
Realizes workflows: plan-run
adrs: ADR-0014, ADR-0024, ADR-0027
Requirements FR-02, FR-03, FUX-03, XL-03
Depends on AIFACTORY-FEAT-189 AgentRegistryService: the publication path of releases from I2
Sources model/workflows/plan-run.yaml

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

AIFACTORY-US-093: The Plan a run workflow runs from its published definition

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

The integration PBI of the definition plan-run, one of the four definitions a person submits rather than a readiness bundle (ADR-0026, D63). A requester submits a run whose release pins the definition through SubmitRun of RunControlService; Run Control accepts it and publishes RunAccepted with the inputs run-submission (run-submission-v1) and vision-blueprint (blueprint-vision-v1). WorkflowEngineService loads the Published release the run pinned through AgentRegistryService and marks the five steps ready in order: classify-intent on the factory-workflow-orchestrator release, the condition select-definition, compose-plan on the same release under its when guard, the condition validate-plan and start-steps, declared as a read-class tool step bound to knowledge-search. The two agent steps declare failure_policy Retry, applied by Run Control only to a Failed attempt of failure class transient, the steps being of read class; start-steps declares Fail and is never retried. Every step reads or writes inside the run envelope only, and no approval is needed. No step declares a compensation (ADR-0014). The run reports exactly one outcome within its budget. Before any run, the definition release and the agent release of factory-workflow-orchestrator, 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. In I4 the evaluation gate of the complete delivery applies: where an evaluation suite exists for the asset kind, a release is published only with a passed evaluation record (ADR-0021), and an agent release published before I4 without one is resubmitted through the gate as a new version; the runs pin the Published release, never a Draft one (D140). Under the model as it stands only the unmatched branch can reach start-steps: on the matched branch compose-plan is skipped and validate-plan reads an absent plan and fails the run (AIFACTORY-US-1241), and on the unmatched branch the verdict valid that validate-plan reads is set by no act of the model (AIFACTORY-US-1242); both are open questions for the owner. The step behaviour is specified in AIFACTORY-US-1241 to AIFACTORY-US-1243; this PBI proves the chain on the recorded fixture.

Acceptance criteria

AC1 Given the Published release of plan-run, submitted through AgentRegistryService/SubmitRelease and published through AgentRegistryService/PublishRelease after an approval by a Reviewer who is not the submitter and with a passed evaluation record where an evaluation suite exists for its asset kind (ADR-0021, D140), carries the 5 steps, input mappings, the when guard of plan-run/compose-plan, the conditions, retry policies, timeouts, the failure_policy Retry of the two agent steps and Fail of plan-run/start-steps exactly as in model/workflows/plan-run.yaml, when RunControlService/RunAccepted arrives for a run that a requester submitted through RunControlService/SubmitRun with the inputs run-submission and vision-blueprint, then WorkflowEngineService/WorkflowRunStarted is emitted and, on the unmatched branch of plan-run/select-definition, plan-run/classify-intent, plan-run/select-definition, plan-run/compose-plan, plan-run/validate-plan and plan-run/start-steps become ready in that order on the pinned Published release of factory-workflow-orchestrator, no Draft release being loaded; this declared order covers the unmatched branch only, the matched branch ending at plan-run/validate-plan as AC3 states.
AC2 Given the unmatched branch, the owner's decision on which act sets the verdict valid read by plan-run/validate-plan, and every step succeeding, when the run completes, then plan (workflow-definition-v1) is recorded as the run output under the run envelope, WorkflowEngineService/WorkflowRunCompleted is emitted once and RunControlService/RunCompleted follows exactly once (ADR-0014); this Completed outcome covers the unmatched branch only and is not proven on the fixture until that decision (AIFACTORY-US-1242).
AC3 Given an agent step is settled Failed with its retry budget spent or with a failure class that is not retried, plan-run/validate-plan reads an absent or unreadable verdict (on the matched branch, where plan-run/compose-plan was skipped and no plan is recorded, and under the model as it stands on the unmatched branch too), or plan-run/start-steps fails under its policy Fail, when the engine applies the compensation policy of model/workflows/plan-run.yaml, then WorkflowEngineService/WorkflowRunFailed names the step and the failure class, the recorded outputs stay in place as evidence and RunControlService/RunFailed is published exactly once (recovery, not replay, ADR-0014).
AC4 Given the recorded fixture inputs of model/workflows/plan-run.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: workflows plan-run
Traces: steps plan-run/classify-intent, plan-run/select-definition, plan-run/compose-plan, plan-run/validate-plan, plan-run/start-steps
Traces: agents factory-workflow-orchestrator
Traces: tools knowledge-search
Traces: services WorkflowEngineService, RunControlService, AgentRegistryService
Traces: apis RunControlService/SubmitRun, AgentRegistryService/SubmitRelease, AgentRegistryService/PublishRelease
Traces: events AgentRegistryService/AssetReleasePublished, RunControlService/RunAccepted, RunControlService/RunCompleted, RunControlService/RunFailed, WorkflowEngineService/WorkflowRunStarted, WorkflowEngineService/WorkflowRunCompleted, WorkflowEngineService/WorkflowRunFailed
Traces: descriptors workflow-definition-v1, run-submission-v1, blueprint-vision-v1
Traces: adrs ADR-0014, ADR-0021, ADR-0024, ADR-0026, ADR-0027
Traces: requirements FR-02, FR-03, FUX-03, XL-03
Depends on AIFACTORY-US-1241, AIFACTORY-US-1242, AIFACTORY-US-1243, feature:workflow-engine-service, feature:run-control-service, feature:agent-registry-service-complete, feature:agent-registry-service-publication, feature:vector-memory-service-thin
Sources model/workflows/plan-run.yaml, model/agents/vision-planning/factory-workflow-orchestrator.yaml, docs/planes/agent-runtime/workflow-definitions/plan-run.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-407 Author, submit and publish the release of the workflow definition plan-run with its agent release implementation The release of plan-run (workflow-definition-v1) authored with its 5 steps, input mappings, the when guard of compose-plan, the conditions of select-definition and validate-plan, retry policies, timeouts and the compensation policy as in model/workflows/plan-run.yaml, the failure_policy of every agent and tool step copied as it stands (Retry on classify-intent and compose-plan, Fail on start-steps), and accepted by ValidateWorkflowDefinition of WorkflowEngineService; it is submitted through SubmitRelease of AgentRegistryService together with the agent release factory-workflow-orchestrator of AIFACTORY-TASK-408 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); the evaluation gate of the complete delivery applies, so a release of an asset kind with an evaluation suite is published only with a passed evaluation record, and the Published release ids are recorded for the fixture run, which pins them. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService
AIFACTORY-TASK-408 Author the agent release factory-workflow-orchestrator with its prompts and skills implementation A Draft release of factory-workflow-orchestrator with its instructions, the three bound skills of model/agents/vision-planning/factory-workflow-orchestrator.yaml, the tool bindings and the model profile reasoning; the release is evaluated with the suite vision-planning-core-v1 on a fixture submission and carries a passed evaluation record before AIFACTORY-TASK-407 submits it for publication, and a release of the agent published before I4 without an evaluation record is resubmitted through the evaluation gate as a new version (D140). ConnectSoft.AI.SoftwareFactory.AgentTemplate
AIFACTORY-TASK-409 Fixture run of plan-run against recorded inputs verification The definition runs end to end on a fixture project in the acceptance environment from RunAccepted to its one outcome for a matched and an unmatched submission on the Published releases of AIFACTORY-TASK-407; every step output validates against its descriptor, the matched submission ends Failed at validate-plan, and the recorded outputs match the recorded ones field by field (AC1, AC3 and AC4 of AIFACTORY-US-093); the Completed run of AC2 is added once the owner decides which act sets the verdict valid. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService
AIFACTORY-TASK-733 Verify plan-run-runs-from-its-definition by running the declared command verification Run dotnet test -c Release --filter Category=WorkflowFixture; it passes and proves AC1, AC3 and AC4 of AIFACTORY-US-093, including the matched submission failing at validate-plan and the failure path of AC3 (WorkflowRunFailed then RunFailed exactly once); AC2 is proven once the owner decides which act sets the verdict valid; the output names the Published release ids of plan-run and factory-workflow-orchestrator that the run pinned, as AgentRegistryService/GetRelease reports them with their approval by a Reviewer who is not the submitter and their evaluation record (D140). ConnectSoft.AI.SoftwareFactory.WorkflowEngineService

AIFACTORY-US-1241: The orchestrator classifies the intent of a submission and the engine checks for a matching Published definition

behavior · persona requester As a requester, I want my submission classified into an intent class with the candidate definitions that could serve it, so that a Published definition is reused unchanged when one fits, and a plan is composed only when none does.

The first two steps of plan-run. When the engine marks classify-intent ready it resolves goal from input.run-submission and vision-blueprint from the run input. The factory-workflow-orchestrator release runs in read class with the reasoning profile, the skill factory-workflow-orchestrator-propose-workflow-definitions and only the tools of its card without side effects (knowledge-search, graph-query, list-files, read-range); it names the intent class, the candidate definitions with the reason for each, and matchedDefinition when a Published definition matches the intent class and the scope, and writes intent. It declares failure_policy Retry, exponential, 3 attempts, backoff 30s, timeout PT30M. When classify-intent succeeded the engine evaluates the condition select-definition, steps.classify-intent.intent.matchedDefinition != null, over the recorded output without a service call and within PT1M. When it holds, the summary says a Published definition fits and the run instantiates it unchanged; the guard of compose-plan does not hold and the engine records that step Skipped (ADR-0027). The model declares no step that instantiates the matched definition, and validate-plan depends on compose-plan and reads steps.compose-plan.plan.valid, while start-steps maps plan from steps.compose-plan.plan; under the model as it stands every run of the matched branch therefore reaches validate-plan with no recorded plan and fails there with evidence. How a matched definition is instantiated is an open question for the owner. When the condition does not hold compose-plan runs. The condition never retries; a missing or unreadable intent fails it with evidence instead of being read as a match.

Acceptance criteria

AC1 Given a run accepted with run-submission (run-submission-v1) and vision-blueprint (blueprint-vision-v1), when factory-workflow-orchestrator executes plan-run/classify-intent, then the output intent (artifact-v1) is recorded once under the run envelope with the intent class, the candidate definitions with their reasons and matchedDefinition set or empty, and no tool with side effects is called (SCN-plan-run-001).
AC2 Given an attempt of plan-run/classify-intent exceeds its timeout PT30M, settles Failed with a failure class other than transient, or settles Failed with failure class transient until the exponential budget of 3 attempts is spent, when the engine applies the policy of model/workflows/plan-run.yaml, then WorkflowEngineService/WorkflowRunFailed names the step and no shared system is changed (SCN-plan-run-001, ADR-0014).
AC3 Given steps.classify-intent.intent names a matched Published definition, when the engine evaluates plan-run/select-definition, then the condition holds with exactly one outcome and no service call, and the guard of plan-run/compose-plan does not hold, so that step is recorded Skipped (SCN-plan-run-002, ADR-0027).
AC4 Given the recorded intent names no matched definition, when the engine evaluates plan-run/select-definition, then the condition completes with one outcome and plan-run/compose-plan becomes ready; given the intent is missing or unreadable or the evaluation exceeds PT1M, then the condition is not retried, it fails with evidence and WorkflowEngineService/WorkflowRunFailed names it (SCN-plan-run-002).
AC5 Given plan-run/select-definition held and plan-run/compose-plan was recorded Skipped, when the engine evaluates plan-run/validate-plan, then under the model as it stands it reads an absent steps.compose-plan.plan and fails with evidence without a retry, WorkflowEngineService/WorkflowRunFailed names validate-plan and RunControlService/RunFailed is published exactly once; how a matched Published definition is instantiated instead is an open question for the owner (SCN-plan-run-002, ADR-0014).
Traces: workflows plan-run
Traces: steps plan-run/classify-intent, plan-run/select-definition, plan-run/compose-plan
Traces: agents factory-workflow-orchestrator
Traces: services WorkflowEngineService
Traces: events WorkflowEngineService/StepReady, WorkflowEngineService/WorkflowRunFailed, RunControlService/RunFailed
Traces: descriptors run-submission-v1, blueprint-vision-v1, artifact-v1
Traces: scenarios SCN-plan-run-001, SCN-plan-run-002
Traces: adrs ADR-0014, ADR-0027
Traces: requirements FR-02, FUX-03
Depends on feature:workflow-engine-service, feature:run-control-service
Sources model/workflows/plan-run.yaml, model/agents/vision-planning/factory-workflow-orchestrator.yaml, model/scenarios/plan-run.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-4951 Recorded fixture submissions with and without a matching definition fixture Two fixture submissions with their Vision Blueprint, one whose intent matches a Published fixture definition and one whose intent matches none, each with the expected intent artifact (intent class, candidates with reasons, matchedDefinition set or empty), the expected outcome of select-definition and, for the matched submission, the expected run outcome Failed with WorkflowRunFailed naming validate-plan after compose-plan was recorded Skipped, as the oracle of SCN-plan-run-001 and SCN-plan-run-002. ConnectSoft.AI.SoftwareFactory.AgentTemplate
AIFACTORY-TASK-4952 Load select-definition and the when guard of compose-plan in the Draft release implementation The condition select-definition and the when guard of compose-plan of the Draft release read only the recorded intent, as model/workflows/plan-run.yaml declares; a guard that does not hold records compose-plan Skipped and its dependants treat it as satisfied (ADR-0027). ConnectSoft.AI.SoftwareFactory.WorkflowEngineService
AIFACTORY-TASK-4953 Prove the classification and the definition check on the fixture verification A fixture run proves SCN-plan-run-001 and SCN-plan-run-002 (AC1 to AC5 of AIFACTORY-US-1241); the matched submission records compose-plan Skipped and then ends Failed with WorkflowRunFailed naming validate-plan and RunFailed once, the unmatched one makes compose-plan ready, and an unreadable intent fails select-definition with evidence. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService

AIFACTORY-US-1242: The orchestrator composes a plan from Published agent releases and the engine checks it against the DSL

behavior · persona requester As a requester, I want a plan composed for my intent when no Published definition fits, with every step on a Published agent release, so that a run without a ready-made definition still executes a validated graph and never an ad hoc one.

The composing branch of plan-run. When the guard steps.classify-intent.intent.matchedDefinition == null holds the engine marks compose-plan ready and resolves goal from input.run-submission and intent from steps.classify-intent.intent. The factory-workflow-orchestrator release runs in read class with the skill factory-workflow-orchestrator-decompose-goals-into-steps-with-gates: from the intent, the blueprint and the agent catalog it composes a plan as a workflow-definition instance in which every step names a Published agent release, declares its action class and failure policy, and records it as plan. It writes nothing outside the run envelope and declares failure_policy Retry, exponential, 3 attempts, backoff 30s, timeout PT30M. When compose-plan succeeded the engine evaluates the condition validate-plan, steps.compose-plan.plan.valid == true, which the summary describes as the validation of the instance against workflow-definition-v1, the release states of the agents it names and the budget of the run; a condition reads recorded outputs only, never calls a service and completes within PT1M. workflow-definition-v1 has no valid member and no act of the model sets the verdict the condition reads, so which act sets it (for example an in-process use of the rules of ValidateWorkflowDefinition of WorkflowEngineService before the condition runs) is an open question for the owner. Until that decision the condition reads an absent member and fails the run with evidence under the missing-or-unreadable rule. Once it is decided, a valid plan lets start-steps become ready and an invalid plan fails the run with the validation report as evidence and the failure class validation. The definition declares no false branch, so an invalid plan is never revised in the same run.

Acceptance criteria

AC1 Given plan-run/select-definition found no matched definition, when factory-workflow-orchestrator executes plan-run/compose-plan with goal and intent, then the output plan (workflow-definition-v1) is recorded once under the run envelope and every step of it names a Published agent release, an action class and a failure policy (SCN-plan-run-003).
AC2 Given an attempt of plan-run/compose-plan exceeds its timeout PT30M, settles Failed with a failure class other than transient, or settles Failed with failure class transient until the exponential budget of 3 attempts is spent, when the engine applies the policy of model/workflows/plan-run.yaml, then WorkflowEngineService/WorkflowRunFailed names the step and the recorded intent stays in place (SCN-plan-run-003, ADR-0014).
AC3 Given steps.compose-plan.plan is recorded as workflow-definition-v1, which has no valid member, when the engine evaluates plan-run/validate-plan, then the condition reads the recorded plan only, without a service call, finds the member absent and fails with evidence instead of being read as valid, without a retry, WorkflowEngineService/WorkflowRunFailed names validate-plan and RunControlService/RunFailed is published exactly once; the same holds for a missing plan or an evaluation over PT1M (SCN-plan-run-004, ADR-0014).
AC4 Given the owner has decided which act sets the verdict valid before the condition runs, when the engine evaluates plan-run/validate-plan, then a valid plan completes the condition with exactly one outcome and makes plan-run/start-steps ready, and an invalid plan (a step names an agent release that is not Published, a step without an action class or failure policy, or a plan over the run budget) fails the run with the validation report as evidence, WorkflowEngineService/WorkflowRunFailed naming validate-plan with failure class validation and RunControlService/RunFailed published exactly once; this criterion depends on that decision and is not proven on the fixture until then (SCN-plan-run-004, ADR-0014).
Traces: workflows plan-run
Traces: steps plan-run/compose-plan, plan-run/validate-plan
Traces: agents factory-workflow-orchestrator
Traces: services WorkflowEngineService
Traces: events WorkflowEngineService/StepReady, WorkflowEngineService/WorkflowRunFailed, RunControlService/RunFailed
Traces: descriptors run-submission-v1, artifact-v1, workflow-definition-v1
Traces: scenarios SCN-plan-run-003, SCN-plan-run-004
Traces: adrs ADR-0014, ADR-0024
Traces: requirements FR-02, FR-03, XL-03
Depends on AIFACTORY-US-1241, feature:workflow-engine-service, feature:run-control-service
Sources model/workflows/plan-run.yaml, model/agents/vision-planning/factory-workflow-orchestrator.yaml, model/services/agent-mesh/WorkflowEngineService.yaml, model/scenarios/plan-run.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-4954 Fixture plans that pass and fail the DSL check fixture A fixture intent with no matched definition, the expected valid plan (workflow-definition-v1) whose steps name Published fixture agent releases, and three invalid plans (an InReview agent release, a step without failure policy, a plan over budget) with the expected validation report, as the oracle of SCN-plan-run-003 and SCN-plan-run-004; under the model as it stands the expected outcome of validate-plan is Failed for every plan, the verdict valid being absent, and the expected verdicts per plan are asserted once the owner decides which act sets it. ConnectSoft.AI.SoftwareFactory.AgentTemplate
AIFACTORY-TASK-4955 Load validate-plan and the compose-plan mappings in the Draft release implementation The agent step compose-plan of the Draft release maps goal and intent as declared in model/workflows/plan-run.yaml, and the condition validate-plan reads the recorded plan only, without a service call; an absent valid member, a missing plan or an unreadable one fails the condition with evidence and is never read as valid; the act that sets the verdict is added once the owner decides it. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService
AIFACTORY-TASK-4956 Prove the composition and the DSL check on the fixture verification A fixture run proves SCN-plan-run-003 and SCN-plan-run-004 (AC1 to AC3 of AIFACTORY-US-1242); every recorded plan reaches validate-plan, which reads the absent verdict and ends in WorkflowRunFailed naming validate-plan and RunFailed once; AC4 (the valid plan making start-steps ready and the invalid plans failing with failure class validation) is proven once the owner decides which act sets the verdict. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService

AIFACTORY-US-1243: The engine records the validated plan and announces its first steps for Run Control to dispatch

behavior · persona requester As a requester, I want the validated plan recorded and its first steps handed to Run Control, so that the work I asked for starts on a graph that was checked before any step ran.

The last step of plan-run. When validate-plan held the engine marks start-steps ready and resolves plan from steps.compose-plan.plan. The step is declared kind: tool with tool: knowledge-search and failure_policy Fail. Under the StepKind rule of WorkflowEngineService an Agent or Tool step becomes an attempt that Run Control dispatches and the engine does not run, so the engine emits StepReady for start-steps with actionClass read, Run Control dispatches an attempt of the tool knowledge-search (VectorMemoryService, read class, delivered thin in I1 with an empty, well-formed result), and when Run Control settles that step the engine records the plan and, as the summary says, announces the steps of the plan without dependencies; the engine itself never owns run authority (ADR-0014). The step writes nothing outside the run envelope and needs no approval. It declares no retry and a timeout PT1M, so any Failed attempt fails the step at once and the engine reports WorkflowRunFailed with the plan kept as evidence. Four points are open and reported to the owner: the double reading of the step, an engine action in the summary against a dispatched knowledge-search attempt in the declaration; how the engine executes a composed plan that is not a loaded release; why the run completes with plan as its output once the plan's first steps are announced; and how a matched Published definition is instantiated when compose-plan was skipped. This PBI delivers the step exactly as the definition declares it.

Acceptance criteria

AC1 Given plan-run/validate-plan held and plan resolves from steps.compose-plan.plan, when the engine marks plan-run/start-steps ready, then WorkflowEngineService/StepReady for start-steps is emitted with actionClass read, Run Control dispatches an attempt of the tool knowledge-search, and when that step is settled (RunControlService/StepSettled) the engine records the plan under the run envelope and emits WorkflowEngineService/StepReady once for each root step of the plan, the steps without dependencies, and for no other step (SCN-plan-run-005).
AC2 Given the step succeeded, when the run completes, then the run output plan (workflow-definition-v1) is set, WorkflowEngineService/WorkflowRunCompleted is emitted once and RunControlService/RunCompleted follows exactly once, as the definition declares; why the run completes once the plan's first steps are announced is an open question for the owner (SCN-plan-run-005, ADR-0014).
AC3 Given an attempt of plan-run/start-steps settles Failed with any failure class or exceeds its timeout PT1M, when the engine applies its failure_policy Fail from model/workflows/plan-run.yaml, then the step is not retried, WorkflowEngineService/WorkflowRunFailed names start-steps, the recorded plan stays as evidence and RunControlService/RunFailed is published exactly once (SCN-plan-run-005, ADR-0014).
Traces: workflows plan-run
Traces: steps plan-run/start-steps
Traces: tools knowledge-search
Traces: services WorkflowEngineService, RunControlService
Traces: events WorkflowEngineService/StepReady, RunControlService/StepSettled, WorkflowEngineService/WorkflowRunCompleted, WorkflowEngineService/WorkflowRunFailed, RunControlService/RunCompleted, RunControlService/RunFailed
Traces: descriptors workflow-definition-v1
Traces: scenarios SCN-plan-run-005
Traces: adrs ADR-0014, ADR-0024
Traces: requirements FR-03, XL-03
Depends on AIFACTORY-US-1242, feature:workflow-engine-service, feature:run-control-service, feature:vector-memory-service-thin
Sources model/workflows/plan-run.yaml, model/tools/knowledge-search.yaml, model/scenarios/plan-run.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-4957 Fixture validated plan with its expected first steps fixture The valid fixture plan of AIFACTORY-TASK-4954 with the expected set of steps without dependencies that are announced, the expected run output plan and a fixture attempt that fails start-steps, as the oracle of SCN-plan-run-005. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService
AIFACTORY-TASK-4958 Load start-steps with its failure policy Fail and map the run output implementation The tool step start-steps of the Draft release is loaded with tool knowledge-search, actionClass read, failure_policy Fail, no retry and timeout PT1M as in model/workflows/plan-run.yaml, maps plan from steps.compose-plan.plan, and the recorded plan is set as the run output plan when the run completes. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService
AIFACTORY-TASK-4959 Prove the start of the first steps and the run completion on the fixture verification A fixture run proves SCN-plan-run-005 (AC1 to AC3 of AIFACTORY-US-1243), starting from a recorded run state in which validate-plan held, since no act of the model sets its verdict until the owner decides; StepReady for start-steps with actionClass read, one dispatched knowledge-search attempt, StepReady exactly once for each root step of the plan, WorkflowRunCompleted and RunCompleted exactly once, and a failed attempt ending in WorkflowRunFailed naming start-steps without a retry. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService