Skip to content

AIFACTORY-FEAT-152: Workflow definition: Observability blueprint

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

The workflow definition observability-blueprint as a published asset: Builds the Observability Blueprint from the Service and Module Blueprints: spans, metrics and log events per module, health checks, service level objectives and the alerts that guard them; validated against the DSL. It has 5 steps, names the agents observability-engineer and the tools blueprint-submit-version, blueprint-validate, and is executed by WorkflowEngineService under Run Control.

Delivers —
Stubs —
Realizes workflows: observability-blueprint
adrs: ADR-0014, ADR-0024, ADR-0026, ADR-0027, ADR-0030
Requirements FR-11, XL-09
Depends on AIFACTORY-FEAT-189 AgentRegistryService: the publication path of releases from I2
Sources model/workflows/observability-blueprint.yaml

Scenarios to trace (6, catalog): SCN-observability-blueprint-001 ✓, SCN-observability-blueprint-002 ✓, SCN-observability-blueprint-003 ✓, SCN-observability-blueprint-004 ✓, SCN-observability-blueprint-005 ✓, SCN-observability-blueprint-006 ✓

AIFACTORY-US-079: The Observability blueprint workflow runs from its published definition

behavior · persona operator As an operator, I want the observability blueprint workflow to run from its published definition with the agents, tools and gates it declares, so that the Observability Blueprint and its validation receipt are produced the same way on every run, with evidence.

The integration PBI of the definition observability-blueprint, the producing definition of the Observability Blueprint kind (ADR-0030). When BlueprintService has published BlueprintValidated with passed true for the Service Blueprint and for the Module Blueprints of a project, WorkflowEngineService satisfies the two required readiness members service-blueprint (blueprint-service-v1) and module-blueprints (blueprint-module-v1) of the project scope and submits the run itself through SubmitRun of RunControlService with a service token that names the project and the bundle idempotency key (D131); the same versions return the existing run and a newer version of either member 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: derive-signals, draft-observability-blueprint, submit-version, validate and check-valid. Agent steps run the observability-engineer release, the tool steps call blueprint-submit-version and blueprint-validate, and the condition loops back to the draft at most twice. 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 release of observability-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 step behaviour is specified in AIFACTORY-US-1202 to AIFACTORY-US-1204; this PBI proves the chain on the recorded fixture.

Acceptance criteria

AC1 Given BlueprintService/BlueprintValidated with passed true for the kinds Service and Module of one project and tenant, when both required members are satisfied, then WorkflowEngineService/ReadinessRunSubmitted is emitted once and the run is submitted through RunControlService/SubmitRun with a service token naming the project (D131); a newer member version emits WorkflowEngineService/ReadinessSuperseded for the open correlation.
AC2 Given the Published release of observability-blueprint, 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 failure policy of each agent and tool step, the idempotency_key documentHash of submit-version and the on_false loop of check-valid exactly as in model/workflows/observability-blueprint.yaml, when RunControlService/RunAccepted arrives for a run that pinned it, then WorkflowEngineService/WorkflowRunStarted is emitted and observability-blueprint/derive-signals, observability-blueprint/draft-observability-blueprint, observability-blueprint/submit-version, observability-blueprint/validate and observability-blueprint/check-valid become ready in that order, each agent step on the pinned Published release of observability-engineer, and no Draft release is loaded.
AC3 Given every step succeeds and the receipt passed, when the run completes, then observability-blueprint (blueprint-observability-v1) and validation-receipt (blueprint-validation-receipt-v1) are the run outputs, WorkflowEngineService/WorkflowRunCompleted is emitted once and RunControlService/RunCompleted follows exactly once (ADR-0014).
AC4 Given a step spends its retry budget or the condition reaches its iteration limit, when the engine applies the compensation policy of model/workflows/observability-blueprint.yaml, then WorkflowEngineService/WorkflowRunFailed names the step, no Draft version is promoted and RunControlService/RunFailed is published exactly once (ADR-0026).
AC5 Given the recorded fixture inputs of model/workflows/observability-blueprint.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 observability-blueprint
Traces: steps observability-blueprint/derive-signals, observability-blueprint/draft-observability-blueprint, observability-blueprint/submit-version, observability-blueprint/validate, observability-blueprint/check-valid
Traces: agents observability-engineer
Traces: tools blueprint-submit-version, blueprint-validate
Traces: services WorkflowEngineService, RunControlService, AgentRegistryService, BlueprintService
Traces: apis RunControlService/SubmitRun, AgentRegistryService/SubmitRelease, AgentRegistryService/PublishRelease
Traces: events AgentRegistryService/AssetReleasePublished, BlueprintService/BlueprintValidated, WorkflowEngineService/ReadinessRunSubmitted, WorkflowEngineService/ReadinessSuperseded, WorkflowEngineService/WorkflowRunStarted, WorkflowEngineService/WorkflowRunCompleted, WorkflowEngineService/WorkflowRunFailed, RunControlService/RunAccepted, RunControlService/RunCompleted, RunControlService/RunFailed
Traces: descriptors workflow-definition-v1, readiness-bundle-v1, blueprint-service-v1, blueprint-module-v1, blueprint-observability-v1, blueprint-validation-receipt-v1
Traces: adrs ADR-0014, ADR-0024, ADR-0026, ADR-0027, ADR-0030
Traces: requirements FR-11, XL-09
Depends on AIFACTORY-US-1202, AIFACTORY-US-1203, AIFACTORY-US-1204, feature:wf-architecture-decomposition, feature:wf-module-blueprints, feature:blueprint-service, feature:workflow-engine-service, feature:run-control-service, feature:agent-registry-service-thin, feature:agent-registry-service-publication
Sources model/workflows/observability-blueprint.yaml, model/agents/operations/observability-engineer.yaml, docs/planes/agent-runtime/workflow-definitions/observability-blueprint.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-347 Author, submit and publish the release of the workflow definition observability-blueprint with its agent release implementation The release of observability-blueprint (workflow-definition-v1) authored with its 5 steps, input mappings, retry policies, timeouts, the failure policy Retry of each agent and tool step, the idempotency_key documentHash of submit-version and the on_false loop of check-valid exactly as in model/workflows/observability-blueprint.yaml and accepted by ValidateWorkflowDefinition; it is submitted through SubmitRelease of AgentRegistryService together with the agent release observability-engineer of AIFACTORY-TASK-348 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-348 Author the agent release observability-engineer with its prompts and skills implementation A Draft release of observability-engineer with its instructions, the skills observability-engineer-derive-signals and observability-engineer-draft-observability-blueprint among its bound skills, the tool bindings and the model profile of model/agents/operations/observability-engineer.yaml; the release passes a smoke run on fixture Service and Module Blueprints in the template tests and is submitted for publication by AIFACTORY-TASK-347, and no evaluation verdict is required for its publication before I4 (D140). ConnectSoft.AI.SoftwareFactory.AgentTemplate
AIFACTORY-TASK-349 Fixture run of observability-blueprint against recorded inputs verification The definition runs end to end on fixture Service and Module Blueprints in the acceptance environment from the readiness start to RunCompleted on the Published releases of AIFACTORY-TASK-347; every step output validates against its descriptor (AC1 to AC3 and AC5 of AIFACTORY-US-079). ConnectSoft.AI.SoftwareFactory.WorkflowEngineService
AIFACTORY-TASK-731 Verify observability-blueprint-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-079, including the failure path of AC4 (WorkflowRunFailed then RunFailed exactly once); the output names the Published release ids of observability-blueprint and observability-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-1202: The Observability Engineer derives the signals and drafts the Observability Blueprint from the design

behavior · persona operator As an operator, I want the spans, metrics, log events, health checks, objectives and alerts of a product derived from its Service and Module Blueprints, so that every generated service is observable from its first deployment without a person writing the plan.

The two agent steps of observability-blueprint. When the engine marks derive-signals ready it resolves service-blueprint from input.service-blueprint (blueprint-service-v1) and module-blueprints from input.module-blueprints (blueprint-module-v1); the observability-engineer release runs the skill observability-engineer-derive-signals in read class with read tools only and writes signal-plan (artifact-v1): spans, metrics and log events per module and per published operation, with the attributes the observability conventions require and the objectives the Service Blueprint states. When draft-observability-blueprint becomes ready it receives both blueprints plus signal-plan from steps.derive-signals.signal-plan, and on a revision pass the findings of the last validation receipt as feedback; the skill observability-engineer-draft-observability-blueprint writes, in sandbox class, the Observability Blueprint against blueprint-observability-v1: the signal catalogue per module, health checks, service level objectives with their indicators and alert rules with their routes, addressing the rules OBS-001 to OBS-003. Neither step touches a shared system 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, any other failure class is not retried, and a step that exceeds PT30M or spends its budget fails the run.

Acceptance criteria

AC1 Given a run accepted with service-blueprint and module-blueprints, when observability-engineer executes observability-blueprint/derive-signals, then signal-plan (artifact-v1) is recorded once under the run envelope with spans, metrics and log events for every module and published operation (SCN-observability-blueprint-001).
AC2 Given steps.derive-signals.signal-plan is recorded, when observability-blueprint/draft-observability-blueprint runs, then observability-blueprint-draft validates against blueprint-observability-v1 with health checks, objectives with indicators and alert rules with routes, and is recorded once (SCN-observability-blueprint-002).
AC3 Given a revision pass after observability-blueprint/check-valid took its false branch, when the draft step re-runs, then the findings of steps.validate.validation-receipt are in its context as feedback and the new draft addresses each finding by rule id (OBS-001 to OBS-003) or schema path (SCN-observability-blueprint-002, ADR-0026).
AC4 Given an attempt of either step exceeds PT30M, settles Failed with a non-transient failure class, or spends the exponential budget of 3 attempts, when Run Control settles the step through RunControlService/StepSettled, then WorkflowEngineService/WorkflowRunFailed names the step and no shared system is changed (SCN-observability-blueprint-001, SCN-observability-blueprint-002, ADR-0014).
Traces: workflows observability-blueprint
Traces: steps observability-blueprint/derive-signals, observability-blueprint/draft-observability-blueprint
Traces: agents observability-engineer
Traces: services WorkflowEngineService
Traces: events WorkflowEngineService/StepReady, WorkflowEngineService/WorkflowRunFailed, RunControlService/StepSettled
Traces: descriptors blueprint-service-v1, blueprint-module-v1, artifact-v1, blueprint-observability-v1
Traces: scenarios SCN-observability-blueprint-001, SCN-observability-blueprint-002
Traces: adrs ADR-0014, ADR-0026, ADR-0030
Traces: requirements FR-11
Depends on feature:workflow-engine-service, feature:run-control-service
Sources model/workflows/observability-blueprint.yaml, model/skills/operations/observability-engineer-derive-signals.yaml, model/skills/operations/observability-engineer-draft-observability-blueprint.yaml, model/blueprints.yaml, model/scenarios/observability-blueprint.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-4762 Recorded fixture of Service and Module Blueprints with the expected signal plan and draft fixture Fixture Service and Module Blueprints with the expected signal plan (artifact-v1) and the expected Observability Blueprint draft (blueprint-observability-v1), plus a receipt with an OBS-002 finding as feedback for the revision pass of SCN-observability-blueprint-002. ConnectSoft.AI.SoftwareFactory.AgentTemplate
AIFACTORY-TASK-4763 Verify the input mappings and skill selection of the two agent steps in the Draft release verification The steps derive-signals and draft-observability-blueprint of the Draft release authored by AIFACTORY-TASK-347 resolve service-blueprint, module-blueprints and signal-plan exactly as mapped in model/workflows/observability-blueprint.yaml and select the skills observability-engineer-derive-signals and observability-engineer-draft-observability-blueprint. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService
AIFACTORY-TASK-4764 Prove the signal and draft steps on the fixture verification A fixture run proves SCN-observability-blueprint-001 and SCN-observability-blueprint-002 (AC1 to AC4 of AIFACTORY-US-1202); the outputs validate against artifact-v1 and blueprint-observability-v1, the revision pass addresses each finding, and the retry exhaustion ends in WorkflowRunFailed naming the step. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService

AIFACTORY-US-1203: The Observability Blueprint draft is stored as a project-scope Draft version and validated with a receipt

behavior · persona operator As an operator, I want the drafted Observability Blueprint stored as a Draft version of my project and validated against its schema and the OBS rules, so that a verdict with findings exists for every draft before infrastructure is planned on it.

The two tool steps of observability-blueprint; they reuse the tool bindings of blueprint-submit-version and blueprint-validate that the feature wf-vision-to-blueprint delivers and fork nothing. When submit-version becomes ready the engine resolves document from steps.draft-observability-blueprint.observability-blueprint-draft and emits StepReady with action class shared-write; Run Control dispatches the attempt through the pipeline of ToolAdapterService. Draft versions are autonomous by default; when the project policy gates blueprint drafts, Policy.Decide answers allow-with-approval for the action kind tool-invocation and an approval whose subject is the run is requested, bound to the invocation request hash, which covers the document hash, with proposal kind tool-invocation; the run waits WaitingForApproval and the write happens only on an approving decision (D64, D129). The tool stores the document as a project-scope Draft BlueprintVersion of kind Observability, idempotent on its document hash, and returns version-ref (blueprint-version-ref-v1). The step declares failure_policy Retry with idempotency_key documentHash, so a Failed attempt of failure class transient is retried under the fixed budget of 2 attempts with backoff 10s (D114); an Uncertain attempt is never retried automatically and waits for an operator decision with a finding (D119). When validate becomes ready the tool blueprint-validate validates the version against blueprint-observability-v1 and the rules OBS-001 to OBS-003 in sandbox class and returns validation-receipt with passed, documentHash and findings; a receipt with passed false is a successful step output. A version reference of another tenant is answered NOT_FOUND and the attempt takes failure class permanent (ADR-0015).

Acceptance criteria

AC1 Given steps.draft-observability-blueprint.observability-blueprint-draft is recorded and the project policy does not gate blueprint drafts, when observability-blueprint/submit-version runs through BlueprintService/Blueprints.SubmitDraftVersion, then a Draft BlueprintService/BlueprintVersion of kind Observability exists in project scope, version-ref is recorded once and the same document submitted again returns the same version (SCN-observability-blueprint-003, D64).
AC2 Given the project policy gates blueprint drafts, when observability-blueprint/submit-version is reached, then RunControlService/ApprovalRequested is published for the run bound to the invocation request hash with proposal kind tool-invocation before any write, the write happens only on an approving RunControlService/ApprovalDecided, and a rejected or expired decision ends in ToolAdapterService/ToolInvocationDenied with no Draft version (SCN-observability-blueprint-003, ADR-0026).
AC3 Given a submit attempt settles Failed with failure class transient, when Run Control evaluates it, then it is retried under the fixed budget of 2 attempts because the step declares idempotency_key documentHash; given it settles Uncertain, then ToolAdapterService/ToolEffectUncertain is emitted, it is not retried and the step waits until an operator settles it through ToolAdapterService/ConfirmToolEffect (SCN-observability-blueprint-003, ADR-0014).
AC4 Given steps.submit-version.version-ref is recorded, when observability-blueprint/validate runs through BlueprintService/Blueprints.Validate, then validation-receipt with passed, documentHash and findings by rule id OBS-001 to OBS-003 or schema path is recorded once whether it passed or not, and BlueprintService/BlueprintValidated is emitted with passed true or false (SCN-observability-blueprint-004).
AC5 Given the version reference belongs to another tenant, or a validate attempt exceeds PT5M or spends the fixed budget of 2 attempts, when the step settles, then a foreign reference is answered NOT_FOUND with no receipt and failure class permanent without a retry, and WorkflowEngineService/WorkflowRunFailed names the step (SCN-observability-blueprint-004, ADR-0015).
Traces: workflows observability-blueprint
Traces: steps observability-blueprint/submit-version, observability-blueprint/validate
Traces: tools blueprint-submit-version, blueprint-validate
Traces: services BlueprintService, ToolAdapterService, RunControlService, WorkflowEngineService
Traces: aggregates BlueprintService/BlueprintVersion
Traces: apis BlueprintService/Blueprints.SubmitDraftVersion, BlueprintService/Blueprints.Validate, ToolAdapterService/ConfirmToolEffect
Traces: events BlueprintService/BlueprintValidated, RunControlService/ApprovalRequested, RunControlService/ApprovalDecided, ToolAdapterService/ToolInvocationDenied, ToolAdapterService/ToolEffectUncertain, WorkflowEngineService/WorkflowRunFailed
Traces: descriptors blueprint-observability-v1, blueprint-version-ref-v1, blueprint-validation-receipt-v1
Traces: scenarios SCN-observability-blueprint-003, SCN-observability-blueprint-004
Traces: adrs ADR-0014, ADR-0015, ADR-0026
Traces: requirements FR-11, XL-09
Depends on AIFACTORY-US-1202, feature:wf-vision-to-blueprint, feature:blueprint-service, feature:tool-adapter-service, feature:run-control-service, feature:workflow-engine-service
Sources model/workflows/observability-blueprint.yaml, model/tools/blueprint-submit-version.yaml, model/tools/blueprint-validate.yaml, model/scenarios/observability-blueprint.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-4765 Bind the submit and validate steps to the shared blueprint tool bindings implementation The steps submit-version and validate of the Draft release call blueprint-submit-version and blueprint-validate as delivered by the feature wf-vision-to-blueprint, with document and version-ref mapped as in model/workflows/observability-blueprint.yaml and the idempotency_key documentHash on submit-version. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService
AIFACTORY-TASK-4766 Fixture Observability Blueprint documents with their expected receipts fixture One fixture document that passes OBS-001 to OBS-003 and one that fails OBS-003, each with its expected blueprint-version-ref-v1 and blueprint-validation-receipt-v1, plus a version reference of another tenant with the expected NOT_FOUND, as the oracle of SCN-observability-blueprint-003 and SCN-observability-blueprint-004. ConnectSoft.AI.SoftwareFactory.BlueprintService
AIFACTORY-TASK-4767 Prove the submit and validate steps on the fixture verification A fixture run proves SCN-observability-blueprint-003 and SCN-observability-blueprint-004 (AC1 to AC5 of AIFACTORY-US-1203), including the idempotent resubmission, the gated path, the transient retry, the Uncertain path settled through ConfirmToolEffect, a failed receipt recorded as a step output and the foreign version reference answered NOT_FOUND. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService

AIFACTORY-US-1204: The engine checks the Observability Blueprint receipt and sends findings back to the draft at most twice

behavior · persona operator As an operator, I want a failed validation of the Observability Blueprint to return its findings to the draft a bounded number of times and then fail with the report, so that the blueprint improves on real findings without looping forever or hiding the verdict.

The condition step of observability-blueprint. When check-valid becomes ready the engine evaluates steps.validate.validation-receipt.passed == true over the recorded receipt; a condition step never retries, never calls a service and completes within PT1M. When the receipt passed, the condition completes with one outcome and, being the last step, the run completes with the validated draft as observability-blueprint and the receipt as validation-receipt. When it did not, the engine takes the on_false branch to draft-observability-blueprint with steps.validate.validation-receipt as feedback: the draft, submit and validate steps re-run in order, the revised document gets its own Draft version and its own receipt, and the iteration count of the run rises by one. The branch is taken at most 2 times; when the receipt is still failed after the last iteration the run fails with the validation report as its evidence, WorkflowRunFailed names check-valid with the failure class validation, Run Control records Failed exactly once and every Draft version created on the way stays a Draft. A missing or unreadable receipt fails the condition with evidence instead of being read as passed (ADR-0026, D61).

Acceptance criteria

AC1 Given steps.validate.validation-receipt is recorded with passed true, when the engine evaluates observability-blueprint/check-valid, then the condition completes with one outcome, no service is called and the run completes with WorkflowEngineService/WorkflowRunCompleted once (SCN-observability-blueprint-005).
AC2 Given the recorded receipt has passed false and fewer than 2 iterations were counted, when the engine evaluates observability-blueprint/check-valid, then it takes the false branch to observability-blueprint/draft-observability-blueprint with the receipt as feedback and the iteration count rises by one (SCN-observability-blueprint-006).
AC3 Given the receipt is still passed false after the second iteration, when the engine evaluates the condition, then WorkflowEngineService/WorkflowRunFailed names check-valid with failure class validation and the report as evidence, RunControlService/RunFailed is published exactly once and no Draft version is promoted (SCN-observability-blueprint-006, ADR-0014).
AC4 Given the receipt is missing or unreadable, or the evaluation exceeds PT1M, when the engine evaluates observability-blueprint/check-valid, then the condition is not retried, it fails with evidence and the run follows the compensation policy of model/workflows/observability-blueprint.yaml (SCN-observability-blueprint-005).
Traces: workflows observability-blueprint
Traces: steps observability-blueprint/check-valid, observability-blueprint/draft-observability-blueprint
Traces: services WorkflowEngineService
Traces: events WorkflowEngineService/WorkflowRunCompleted, WorkflowEngineService/WorkflowRunFailed, RunControlService/RunFailed
Traces: descriptors blueprint-validation-receipt-v1, blueprint-observability-v1
Traces: scenarios SCN-observability-blueprint-005, SCN-observability-blueprint-006
Traces: adrs ADR-0014, ADR-0026
Traces: requirements FR-11
Depends on AIFACTORY-US-1203, feature:workflow-engine-service, feature:run-control-service
Sources model/workflows/observability-blueprint.yaml, model/services/agent-mesh/WorkflowEngineService.yaml, model/scenarios/observability-blueprint.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-4768 Map the run outputs from the passing draft and its receipt implementation When check-valid holds the run outputs observability-blueprint and validation-receipt of the Draft release are set from the draft that passed and its receipt, as model/workflows/observability-blueprint.yaml declares. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService
AIFACTORY-TASK-4769 Fixture receipt sequences for the pass, loop and limit paths fixture Recorded receipt sequences (passed true; passed false then true; passed false three times) that drive check-valid of observability-blueprint through the pass, the single loop and the iteration limit, each with the expected run outcome and iteration count. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService
AIFACTORY-TASK-4770 Prove the condition and the bounded loop on the fixture verification A fixture run proves SCN-observability-blueprint-005 and SCN-observability-blueprint-006 (AC1 to AC4 of AIFACTORY-US-1204); one outcome on pass, a loop back with feedback on a failed receipt, and WorkflowRunFailed naming check-valid with failure class validation after the second iteration. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService