AIFACTORY-FEAT-111: Workflow definition: Database 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 I1 Generate a microservice · State elaborated · Route solution-architect · Build order 89 of 185 (Factory code)
The workflow definition database-blueprint as a published asset: Builds the Database Blueprint from the Service Blueprint and the derived domain model: stores per context, tables with tenant and classification conventions, retention and migration policy; validated against the DSL. A product without persistence yields a blueprint with no stores. It has 5 steps, names the agents database-engineer and the tools blueprint-submit-version, blueprint-validate, and is executed by WorkflowEngineService under Run Control.
| Delivers | — |
| Stubs | — |
| Realizes | workflows: database-blueprint adrs: ADR-0014, ADR-0024, ADR-0026, ADR-0027 |
| Requirements | FR-11, XL-09 |
| Depends on | — |
| Sources | model/workflows/database-blueprint.yaml |
Scenarios to trace (6, catalog): SCN-database-blueprint-001 ✓, SCN-database-blueprint-002 ✓, SCN-database-blueprint-003 ✓, SCN-database-blueprint-004 ✓, SCN-database-blueprint-005 ✓, SCN-database-blueprint-006 ✓
AIFACTORY-US-012: A Database Blueprint from the domain model¶
behavior · persona requester
As a requester, I want stores, tables and conventions designed from the domain model before any code is generated, so that the database role generates mappings and migrations from an approved design.
The integration PBI of the definition database-blueprint. The run is activated, not submitted by a person: the readiness correlation of WorkflowEngineService for the project waits for two required members, service-blueprint satisfied by BlueprintValidated of kind Service with passed true and domain-model satisfied by DomainModelDerived with at least one aggregate, and then submits exactly one run through SubmitRun of RunControlService with a service token that names the project and the idempotency key of scope, operation, workflow release and bundle fingerprint. After RunAccepted the engine loads the Draft release through AgentRegistryService and runs five steps in order: derive-stores and draft-database-blueprint on the database-engineer release, the tools blueprint-submit-version and blueprint-validate, and the condition check-valid, which loops back to the draft at most twice. Every agent and tool step declares failure_policy Retry and submit-version declares idempotency_key documentHash (ADR-0014). The run outputs are the last database-blueprint-draft as database-blueprint and the receipt; a passed receipt publishes BlueprintValidated of kind Database, which lets GenerationRecipeService pin the blueprint for a module with persistence. The workflow summary says a product without persistence yields a blueprint with no stores, but blueprint-database-v1 describes one store per document and requires owningModule, storeClass, profile, backupClass, tables and migrations, so a blueprint without a store cannot pass its schema; this conflict, and whether one draft covers the stores of several contexts, is reported to the owner, and no schema validity is asserted for a product without persistence until it is decided. The run reports exactly one outcome within the declared budget. The step behaviour is specified in AIFACTORY-US-1152 to AIFACTORY-US-1154; this PBI proves the chain on the recorded fixture with persistence. The tasks AIFACTORY-TASK-213 and AIFACTORY-TASK-214 of this PBI moved to AIFACTORY-US-1152, the PBI whose behaviour they prove, with their repository and kind unchanged.
Acceptance criteria
| AC1 | Given the Draft release of database-blueprint (workflow-definition-v1) with its readiness activation, 5 steps, mappings, retry policies, timeouts and the idempotency_key documentHash of database-blueprint/submit-version exactly as in model/workflows/database-blueprint.yaml, when BlueprintService/BlueprintValidated of kind Service with passed true and BlueprintService/DomainModelDerived for that blueprint arrive, then the WorkflowEngineService/ReadinessCorrelation submits one run through RunControlService/SubmitRun with a service token naming the project and WorkflowEngineService/ReadinessRunSubmitted is published. |
| AC2 | Given RunControlService/RunAccepted with inputs service-blueprint and domain-model, when the run executes, then WorkflowEngineService/WorkflowRunStarted is emitted and database-blueprint/derive-stores, database-blueprint/draft-database-blueprint, database-blueprint/submit-version, database-blueprint/validate and database-blueprint/check-valid become ready in that order on the pinned release of database-engineer. |
| AC3 | Given every step succeeds, when the run completes, then database-blueprint (blueprint-database-v1) and validation-receipt are the run outputs, BlueprintService/BlueprintValidated carries the Database kind with passed true, WorkflowEngineService/WorkflowRunCompleted is emitted once and RunControlService/RunCompleted follows exactly once; the run of a product without persistence is not asserted, because the store-less blueprint the workflow summary names conflicts with the required fields of blueprint-database-v1, a point pending the owner (ADR-0014, FR-11). |
| AC4 | Given a step settles Failed with a non-transient failure class, exhausts its retry budget or the condition database-blueprint/check-valid reaches its iteration limit, when the engine applies the compensation policy of model/workflows/database-blueprint.yaml, then WorkflowEngineService/WorkflowRunFailed names the step, every Draft version stays a Draft and RunControlService/RunFailed is published exactly once; a gated submit waits on RunControlService/ApprovalRequested until RunControlService/ApprovalDecided (ADR-0026). |
| AC5 | Given the recorded fixture inputs of model/workflows/database-blueprint.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 | database-blueprint |
| Traces: steps | database-blueprint/derive-stores, database-blueprint/draft-database-blueprint, database-blueprint/submit-version, database-blueprint/validate, database-blueprint/check-valid |
| Traces: agents | database-engineer |
| Traces: tools | blueprint-submit-version, blueprint-validate |
| Traces: services | WorkflowEngineService, RunControlService, AgentRegistryService, BlueprintService |
| Traces: aggregates | WorkflowEngineService/ReadinessCorrelation |
| Traces: apis | RunControlService/SubmitRun |
| Traces: events | BlueprintService/DomainModelDerived, BlueprintService/BlueprintValidated, WorkflowEngineService/ReadinessRunSubmitted, WorkflowEngineService/WorkflowRunStarted, WorkflowEngineService/WorkflowRunCompleted, WorkflowEngineService/WorkflowRunFailed, RunControlService/RunAccepted, RunControlService/RunCompleted, RunControlService/RunFailed, RunControlService/ApprovalRequested, RunControlService/ApprovalDecided |
| Traces: descriptors | workflow-definition-v1, readiness-bundle-v1, blueprint-service-v1, blueprint-database-v1, blueprint-validation-receipt-v1 |
| Traces: adrs | ADR-0014, ADR-0024, ADR-0026, ADR-0027 |
| Traces: requirements | FR-11, XL-09 |
| Depends on | AIFACTORY-US-1152, AIFACTORY-US-1153, AIFACTORY-US-1154, feature:workflow-engine-service, feature:run-control-service, feature:agent-registry-service-thin, feature:blueprint-service, feature:wf-architecture-decomposition |
| Sources | model/workflows/database-blueprint.yaml, model/agents/engineering/database-engineer.yaml, docs/planes/agent-runtime/workflow-definitions/database-blueprint.md |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-178 Author the release of the workflow definition database-blueprint from the model |
implementation | A Draft release of database-blueprint (workflow-definition-v1) with its readiness activation on BlueprintValidated of kind Service and DomainModelDerived, its 5 steps, input mappings, retry policies, timeouts, the on_false loop of check-valid, the compensation policy and the budget as in model/workflows/database-blueprint.yaml, with the failure_policy Retry of derive-stores, draft-database-blueprint, submit-version and validate copied as it stands and the idempotency_key documentHash of submit-version; loadable by AgentRegistryService. | ConnectSoft.AI.SoftwareFactory.WorkflowEngineService |
AIFACTORY-TASK-179 Author the agent releases database-engineer with their prompts and skills |
implementation | A Draft release of database-engineer with its instructions, the skills database-engineer-derive-stores and database-engineer-draft-database-blueprint among its bound skills, the tool bindings and the model profile code-agent; the release passes a smoke evaluation of the suite engineering-core-v1 on a fixture domain model. | ConnectSoft.AI.SoftwareFactory.AgentTemplate |
AIFACTORY-TASK-180 Fixture run of database-blueprint against recorded inputs |
verification | The definition runs end to end on a fixture project from the readiness signals to RunCompleted; every step output validates against its descriptor and the outputs database-blueprint and validation-receipt match the recorded ones field by field (AC1 to AC3 and AC5 of AIFACTORY-US-012). | ConnectSoft.AI.SoftwareFactory.WorkflowEngineService |
AIFACTORY-TASK-724 Verify database-blueprint by running the declared command |
verification | Run dotnet test -c Release --filter Category=WorkflowFixture; it passes and proves AC1 to AC5 of AIFACTORY-US-012 on the fixture product with persistence, including the failure path of AC4 with RunFailed exactly once; a product without persistence is added only once the owner decides the store-less blueprint. |
ConnectSoft.AI.SoftwareFactory.WorkflowEngineService |
AIFACTORY-US-1152: The Database Engineer derives the stores per context and drafts the Database Blueprint¶
behavior · persona requester
As a requester, I want the stores of my product derived from its aggregates and written into a Database Blueprint with tenant, classification and retention conventions, so that persistence is designed explicitly, and a product without persistence says so instead of getting an empty guess.
The two agent steps of database-blueprint, both on the database-engineer release. When derive-stores becomes ready the engine resolves domain-model from input.domain-model and service-blueprint from input.service-blueprint; the read-class skill database-engineer-derive-stores returns store-plan (artifact-v1): per context the store it owns and the aggregates it persists, one owning service per store, and the contexts that have no persistence named as such. When draft-database-blueprint becomes ready it receives the same inputs and store-plan from steps.derive-stores.store-plan, and on a revision pass the findings of the last receipt as feedback; the sandbox-class skill database-engineer-draft-database-blueprint writes the Database Blueprint with write-file in the isolated workspace and returns database-blueprint-draft (blueprint-database-v1): its owning module, tables and keys, the TenantId column on every table not marked platform-scoped, the store class and engine profile, the classification and retention per table and the migration policy, so that DB-001 to DB-004 can hold. Two points are not settled and are reported to the owner. The schema holds one owningModule per document, so whether one draft covers the stores of several contexts of the plan is open. The workflow summary says a product without persistence yields a blueprint with no stores, while blueprint-database-v1 requires owningModule, storeClass, profile, backupClass, tables and migrations, so such a draft fails its schema; this PBI asserts no draft for a store plan without stores. Neither step writes outside the run envelope or needs an approval. Each declares failure_policy Retry: a Failed attempt of failure class transient is retried under the exponential budget of 3 attempts with backoff 30s, another failure class is not retried, and a step that exceeds PT30M or exhausts the budget fails the run with evidence, the sandbox output staying in place.
Acceptance criteria
| AC1 | Given a run accepted with service-blueprint and domain-model, when database-engineer executes database-blueprint/derive-stores, then store-plan (artifact-v1) names per context its store, its owning service and its persisted aggregates, names every context without persistence, and is recorded once under the run envelope (SCN-database-blueprint-001). |
| AC2 | Given steps.derive-stores.store-plan is recorded with a store, when database-blueprint/draft-database-blueprint runs, then database-blueprint-draft validates against blueprint-database-v1 with its owning module, tables, keys, the TenantId convention, store class, classification, retention and migration policy, and is recorded once; the draft for a store plan without stores, and a draft that covers several contexts, are pending the owner and not asserted (SCN-database-blueprint-002, FR-11). |
| AC3 | Given a revision pass after database-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 and the new draft addresses each by rule id DB-001 to DB-004 or schema path (SCN-database-blueprint-002, ADR-0026). |
| AC4 | Given an attempt of either step exceeds PT30M, settles Failed with a non-transient failure class or exhausts the exponential budget of 3 attempts, when the engine applies the policy of model/workflows/database-blueprint.yaml, then the attempt fails with evidence, WorkflowEngineService/WorkflowRunFailed names the step and no shared system is changed (SCN-database-blueprint-001, SCN-database-blueprint-002, ADR-0014). |
| Traces: workflows | database-blueprint |
| Traces: steps | database-blueprint/derive-stores, database-blueprint/draft-database-blueprint |
| Traces: agents | database-engineer |
| Traces: services | WorkflowEngineService |
| Traces: events | WorkflowEngineService/StepReady, WorkflowEngineService/WorkflowRunFailed |
| Traces: descriptors | artifact-v1, blueprint-service-v1, blueprint-database-v1 |
| Traces: scenarios | SCN-database-blueprint-001, SCN-database-blueprint-002 |
| Traces: adrs | ADR-0014, ADR-0026, ADR-0027 |
| Traces: requirements | FR-11 |
| Depends on | feature:workflow-engine-service, feature:run-control-service |
| Sources | model/workflows/database-blueprint.yaml, model/skills/engineering/database-engineer-derive-stores.yaml, model/skills/engineering/database-engineer-draft-database-blueprint.yaml, model/blueprints.yaml, model/scenarios/database-blueprint.yaml |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-213 Database engineer release for blueprint authoring |
implementation | The steps derive-stores and draft-database-blueprint of the release authored by AIFACTORY-TASK-178 run database-engineer-derive-stores in read class and database-engineer-draft-database-blueprint in sandbox class with domain-model, service-blueprint and store-plan mapped as in model/workflows/database-blueprint.yaml; the fixture draft validates against blueprint-database-v1. | ConnectSoft.AI.SoftwareFactory.AgentTemplate |
AIFACTORY-TASK-4586 Fixture domain models with and without persistence and their expected drafts |
fixture | A fixture domain model with one persisted context and one context without persistence, with the expected store-plan (artifact-v1) and database-blueprint-draft (blueprint-database-v1), as the oracle of SCN-database-blueprint-001 and SCN-database-blueprint-002; the fixture product without persistence and its store-plan are recorded, while its expected draft declaring no stores depends on the owner decision on store-less blueprints and on drafts covering several contexts. | ConnectSoft.AI.SoftwareFactory.AgentTemplate |
AIFACTORY-TASK-214 Fixture runs with and without persistence |
verification | Both fixture products run derive-stores and prove SCN-database-blueprint-001, and the product with persistence runs draft-database-blueprint and proves SCN-database-blueprint-002 (AC1 to AC4 of AIFACTORY-US-1152); the product without persistence yields a store plan that names its contexts without persistence, its draft is asserted only once the owner decides the store-less blueprint, the revision pass resolves a DB-002 finding by rule id, and the timeout path ends in WorkflowRunFailed naming the step. | ConnectSoft.AI.SoftwareFactory.WorkflowEngineService |
AIFACTORY-US-1153: The Database Blueprint draft is stored as a Draft version and validated with a receipt against the DB rules¶
behavior · persona requester
As a requester, I want the drafted Database Blueprint stored as a Draft version of my project and validated against its schema and the DB rules, so that only a Database Blueprint with tenant, classification and retention conventions reaches a generation recipe.
The two tool steps of database-blueprint, whose service behaviour BlueprintService and ToolAdapterService deliver; this PBI binds them and proves what the definition expects. submit-version resolves document from steps.draft-database-blueprint.database-blueprint-draft, the engine emits StepReady with actionClass shared-write, and blueprint-submit-version reaches Blueprints.SubmitDraftVersion, which stores a project-scope Draft BlueprintVersion of kind Database, idempotent on its document hash. Draft versions are autonomous unless the project policy (BC-20) gates blueprint drafts, in which case the invocation waits on an approval requested through RunControl.RequestApproval with proposalKind tool-invocation that names the run and the step and is bound to the request hash and the exact tool version, and a rejected or expired decision denies it (D64). The declared idempotency_key documentHash lets Run Control retry a Failed attempt of failure class transient under the fixed budget of 2 attempts; an Uncertain attempt is settled only by an operator through ConfirmToolEffect. validate calls Blueprints.Validate with the version reference: BlueprintService checks blueprint-database-v1 and the rules DB-001 to DB-004 from what the document declares, records the receipt whether it passed or not, moves a passed version to Validated, leaves a failed one Draft and publishes BlueprintValidated with the Database kind, passed and the document hash; the call writes only the receipt. A blueprint that declares no stores is not asserted to pass: blueprint-database-v1 requires owningModule, storeClass, profile, backupClass, tables and migrations, and the conflict with the workflow summary is reported to the owner. A version reference of another tenant is answered NOT_FOUND like an unknown one, and the attempt takes failure class permanent and is not retried (ADR-0015).
Acceptance criteria
| AC1 | Given the draft is recorded and the project policy does not gate blueprint drafts, when database-blueprint/submit-version runs blueprint-submit-version through BlueprintService/Blueprints.SubmitDraftVersion, then a Draft BlueprintService/BlueprintVersion of kind Database exists in project scope, version-ref is recorded once and the same document submitted again returns the same reference (SCN-database-blueprint-003, D64). |
| AC2 | Given the project policy gates blueprint drafts, or an attempt settles Failed transient or Uncertain, when database-blueprint/submit-version runs, then the approval is requested through RunControlService/RunControl.RequestApproval with proposalKind tool-invocation, bound to the invocation request hash and the exact tool version, the write waits for an approving RunControlService/ApprovalDecided after RunControlService/ApprovalRequested naming the run and the step, a rejection yields ToolAdapterService/ToolInvocationDenied, a transient failure is retried under the fixed budget of 2 attempts, and an Uncertain attempt raises ToolAdapterService/ToolEffectUncertain and waits for ToolAdapterService/ConfirmToolEffect (SCN-database-blueprint-003, ADR-0014). |
| AC3 | Given steps.submit-version.version-ref is recorded, when database-blueprint/validate runs blueprint-validate through BlueprintService/Blueprints.Validate, then validation-receipt with findings by rule id DB-001 to DB-004 or schema path is recorded once whether it passed or not, BlueprintService/BlueprintValidated carries the Database kind and passed, a passed version is Validated and a failed one stays Draft (SCN-database-blueprint-004). |
| AC4 | Given a version reference of another tenant, or an attempt of database-blueprint/validate that exceeds PT5M or settles Failed transient until the fixed budget of 2 attempts is spent, when the step runs, then the other tenant is answered NOT_FOUND with no receipt and the attempt is permanent and not retried, the exhausted case fails with evidence, and the version keeps its state (SCN-database-blueprint-004, ADR-0015). |
| Traces: workflows | database-blueprint |
| Traces: steps | database-blueprint/submit-version, database-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, RunControlService/RunControl.RequestApproval |
| Traces: events | BlueprintService/BlueprintValidated, RunControlService/ApprovalRequested, RunControlService/ApprovalDecided, ToolAdapterService/ToolInvocationDenied, ToolAdapterService/ToolEffectUncertain |
| Traces: descriptors | blueprint-database-v1, blueprint-version-ref-v1, blueprint-validation-receipt-v1 |
| Traces: scenarios | SCN-database-blueprint-003, SCN-database-blueprint-004 |
| Traces: adrs | ADR-0014, ADR-0015, ADR-0026 |
| Traces: requirements | FR-11 |
| Depends on | AIFACTORY-US-1152, feature:blueprint-service, feature:tool-adapter-service, feature:run-control-service, feature:workflow-engine-service |
| Sources | model/workflows/database-blueprint.yaml, model/tools/blueprint-submit-version.yaml, model/tools/blueprint-validate.yaml, model/services/template-library/BlueprintService.yaml, model/blueprints.yaml, model/scenarios/database-blueprint.yaml |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-4587 Fixture Database Blueprints with their expected receipts |
fixture | One fixture Database Blueprint that passes DB-001 to DB-004 with its expected receipt and Validated state, one that omits TenantId on a tenant table with its DB-002 finding and Draft state, and a version reference of another tenant with the expected NOT_FOUND; a fixture that declares no stores, and its expected receipt, depend on the owner decision on store-less blueprints and are not part of this task until it is taken. | ConnectSoft.AI.SoftwareFactory.BlueprintService |
AIFACTORY-TASK-4588 Verify submit-version and validate of the Draft release against the definition |
verification | A check of the release authored by AIFACTORY-TASK-178 against model/workflows/database-blueprint.yaml proves that the steps submit-version and validate name the tools blueprint-submit-version and blueprint-validate, carry side_effect_class shared-write and sandbox, failure_policy Retry, the idempotency_key documentHash on submit-version only, the fixed retry of 2 attempts with backoff 10s, the timeouts PT2M and PT5M and the mappings document from steps.draft-database-blueprint.database-blueprint-draft and version-ref from steps.submit-version.version-ref; the tool bindings are consumed from feature tool-adapter-service and nothing is authored here. | ConnectSoft.AI.SoftwareFactory.WorkflowEngineService |
AIFACTORY-TASK-4589 Prove the submit and validate steps for Database Blueprints on the fixture |
verification | A fixture run proves SCN-database-blueprint-003 and SCN-database-blueprint-004 (AC1 to AC4 of AIFACTORY-US-1153), including the idempotent resubmission, the gated path, the Uncertain path settled through ConfirmToolEffect, the DB-002 finding leaving the version Draft and the NOT_FOUND of another tenant; a blueprint without stores is not proven until the owner decides it. | ConnectSoft.AI.SoftwareFactory.WorkflowEngineService |
AIFACTORY-US-1154: The engine checks the Database Blueprint receipt and sends findings back to the draft at most twice¶
behavior · persona requester
As a requester, I want a failed Database Blueprint validation to send its findings back to the draft a bounded number of times and then fail the run with the report, so that the blueprint improves on real findings without looping forever.
The condition step of database-blueprint. When check-valid becomes ready the engine evaluates steps.validate.validation-receipt.passed == true over the recorded receipt; the condition is read class, calls no service, never retries and completes within PT1M. A passed receipt completes the condition with one outcome, no further step exists and the run completes with the last draft as database-blueprint and the receipt as validation-receipt. A failed one takes the on_false branch to draft-database-blueprint with the receipt as feedback; the draft, submit and validate steps re-run in order, derive-stores does not, the revised document gets its own Draft version and 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 second iteration the run fails with the validation report as evidence, WorkflowRunFailed names check-valid with failure class validation, Run Control records Failed exactly once and every Draft version stays a Draft, so no Database Blueprint becomes available to a recipe. 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 database-blueprint/check-valid, then the condition completes with exactly one outcome, no service is called and WorkflowEngineService/WorkflowRunCompleted follows with the run outputs set (SCN-database-blueprint-005). |
| AC2 | Given the receipt has passed false and fewer than 2 iterations were counted, when the engine evaluates database-blueprint/check-valid, then it takes the false branch to database-blueprint/draft-database-blueprint with the receipt as feedback, the submit and validate steps re-run and the iteration count rises by one, while database-blueprint/derive-stores does not re-run (SCN-database-blueprint-006). |
| AC3 | Given the receipt is still passed false after the second iteration, when the engine evaluates database-blueprint/check-valid, then WorkflowEngineService/WorkflowRunFailed names check-valid with failure class validation and the report, and RunControlService/RunFailed is published exactly once (SCN-database-blueprint-006, ADR-0014). |
| AC4 | Given the receipt is missing or unreadable or the evaluation exceeds PT1M, when the engine evaluates database-blueprint/check-valid, then the condition is not retried and the step fails with evidence as the compensation policy of model/workflows/database-blueprint.yaml says (SCN-database-blueprint-005, ADR-0026). |
| Traces: workflows | database-blueprint |
| Traces: steps | database-blueprint/check-valid, database-blueprint/draft-database-blueprint |
| Traces: services | WorkflowEngineService |
| Traces: events | WorkflowEngineService/WorkflowRunCompleted, WorkflowEngineService/WorkflowRunFailed, RunControlService/RunFailed |
| Traces: descriptors | blueprint-validation-receipt-v1 |
| Traces: scenarios | SCN-database-blueprint-005, SCN-database-blueprint-006 |
| Traces: adrs | ADR-0014, ADR-0026 |
| Traces: requirements | FR-11 |
| Depends on | AIFACTORY-US-1153, feature:workflow-engine-service, feature:run-control-service |
| Sources | model/workflows/database-blueprint.yaml, model/services/agent-mesh/WorkflowEngineService.yaml, model/scenarios/database-blueprint.yaml |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-4590 Fixture receipt sequences for the pass, loop and limit paths of the Database Blueprint |
fixture | Recorded receipt sequences (passed true; passed false then true; passed false three times) that drive check-valid of database-blueprint through the pass, a single loop and the iteration limit, each with the expected run outcome and iteration count. | ConnectSoft.AI.SoftwareFactory.WorkflowEngineService |
AIFACTORY-TASK-4591 Prove the condition and the bounded loop of database-blueprint on the fixture |
verification | A fixture run proves SCN-database-blueprint-005 and SCN-database-blueprint-006 (AC1 to AC4 of AIFACTORY-US-1154); one outcome on pass, a loop back to draft-database-blueprint without re-running derive-stores, and WorkflowRunFailed naming check-valid with failure class validation after the second iteration. | ConnectSoft.AI.SoftwareFactory.WorkflowEngineService |