Skip to content

AIFACTORY-FEAT-140: Demonstrate I2: Deliver it

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 Outcome verification · Increment I2 Deliver it · State elaborated · Route qa-engineer · Build order 109 of 185 (Factory code)

The outcome of increment I2 is demonstrated end to end and the evidence is recorded: The merged service is built by a pipeline, deployed to a preview environment and promoted under approval; the infrastructure it runs on is planned by the Factory from the design. Demonstrations: The merged change triggers a pipeline run whose results are recorded. The Security, Observability and Infrastructure Blueprints of the product are produced and validated without a person writing them. A preview environment is provisioned, used and torn down. A promotion to the next environment waits for an approval bound to the exact release.

Delivers —
Stubs —
Realizes —
Requirements —
Depends on —
Sources model/backlog/increments.yaml

AIFACTORY-US-1342: Delivery proof: the merged change triggers a recorded pipeline run, becomes a ready release and is promoted to production only after the one approval bound to that release and environment

evidence · persona operator As an operator, I want the merged service of the replayed first-outcome chain built by a pipeline, released and promoted under the one production approval bound to that release and environment, so that no release of a generated service reaches production without recorded results and a decision on that exact release.

This PBI proves two demonstrations of increment I2: the merged change triggers a pipeline run whose results are recorded, and a promotion waits for an approval bound to the exact release. Decision D132 records that the chain is not yet closed in the model, so the proof first checks an I2 precondition register, in the shape of the register of AIFACTORY-US-1339. Its entries are: the pipeline of the generated repository, since no operation creates the repository or the pipeline of a generated product (model/workflows/project-bootstrap.yaml); the inbound deliveries of Azure DevOps, which the feature connector-registry-service-deliveries delivers in I2 so that DeliveryReceived brings the review states, merges and pipeline runs to PipelineExecutionService (D135, model/services/integration/ConnectorRegistryService.yaml); the tool of delivery-run/prepare-release that calls CreateProductRelease of ReleaseService and readies the release so that ReleaseReady is published (model/workflows/delivery-run.yaml); the tool of release/promote-staging that calls RequestPromotion of EnvironmentPromotionService (model/workflows/release.yaml); the action kind promotion with which the Policy gate of EnvironmentPromotionService asks Policy.Decide with the class of the target environment, allowed by the platform bundle for an Operator or a Workspace admin of the project and answered allow-with-approval by the seeded tenant bundle for the class production, whose approval is the one production approval (D140, model/services/governance/PolicyEngineService.yaml), entered as aligned, which does not cover the creation of a preview environment, so the action kind of that entry of AIFACTORY-US-1344 stays open; the publication of the I2 definitions, by which delivery-run, release, preview-environment and the blueprint workflows of I2 with their agents and any new skill, tool and model profile release are loadable, because each I2 workflow feature submits and publishes them through the publication path that feature agent-registry-service-publication delivers in I2, approved by a Reviewer who is not the submitter and without an evaluation verdict before I4, and the runs pin the Published release (D140, model/services/control-plane/AgentRegistryService.yaml), entered as aligned; and the preview entries of AIFACTORY-US-1344. While an entry is open the run is not started and the blocker is the evidence. The wait of release/approve-production and delivery-run/approve-production on the gate of EnvironmentPromotionService is decided and in the model (D133, D135), and so is the order of release, in which promote-production requests the production promotion first, which opens the gate, approve-production then waits on that gate and verify follows, so the promotion is handed off to production only after the approval (D139); neither is an entry of the register. When the register is aligned, the run starts from the change proposal of the replayed I1 chain, after its preview. A reviewer merges it; PipelineExecutionService records the merge, which ChangeProposalMerged carries, and the typed results of the pipeline run of the merged commit, which PipelineRunCompleted carries. The workflow delivery-run evaluates them and, in prepare-release, creates the release through CreateProductRelease, which ReleaseCreated records, and readies it, which ReleaseReady records; together with the pipeline results that event activates release. Its step promote-staging requests the staging promotion; the bake window then passes as a timer, because no I2 service evaluates the SLO guards (model/scenarios/release.yaml, SCN-release-003). A person gives one production approval (D133): after the gates of the production promotion pass, its Policy gate answered allow-with-approval for the class production among them (D140), EnvironmentPromotionService requests the approval of class production with the subject kind Promotion and the promotion id as subject (D135), bound to the release id and the target environment, decided by someone other than the requester, and the decision returns to EnvironmentPromotionService; release/approve-production waits on that approval and requests none of its own, and no approval opens through delivery-run/approve-production. On an approving decision PromotionApproved and PromotionCompleted are recorded and GetCurrentRelease returns the release; a decision bound to another release id or another environment, a rejection or an expiry leaves the environment on its earlier release.

Acceptance criteria

AC1 Given the I2 precondition register, when it is checked before the run, then the pipeline of the generated repository, the inbound deliveries of the feature connector-registry-service-deliveries, the tool of delivery-run/prepare-release that calls CreateProductRelease and readies the release and the tool of release/promote-staging that calls RequestPromotion each name the model file that closes it and its state, the action kind promotion of the Policy gate and the publication of the I2 definitions through the I2 publication path, with AssetReleasePublished recorded for each definition the runs pin, are listed as aligned, and while an entry is open the run is not started and the blocker is recorded as the evidence (D132, D135, D140, ConnectorRegistryService/DeliveryReceived, AgentRegistryService/PublishRelease, AgentRegistryService/AssetReleasePublished, model/services/governance/PolicyEngineService.yaml, model/workflows/delivery-run.yaml, model/workflows/release.yaml).
AC2 Given the change proposal of the replayed I1 chain after its preview, when a reviewer merges it, then the merge and the pipeline run of the merged commit are recorded with their typed results, and the run identifier and results are in the evidence (PipelineExecutionService/ChangeProposalMerged, PipelineExecutionService/PipelineRunCompleted).
AC3 Given the recorded results with no blocking failure, when delivery-run reaches prepare-release, then the release is created through CreateProductRelease and readied, ReleaseCreated and ReleaseReady are recorded, release is activated by ReleaseReady with the pipeline results, promote-staging requests the staging promotion and the bake passes as a timer with the SLO guard evaluation recorded as a stated gap of I2 (ReleaseService/CreateProductRelease, ReleaseService/ReleaseCreated, ReleaseService/ReleaseReady, delivery-run/prepare-release, release/promote-staging, release/bake).
AC4 Given release/promote-production requested the production promotion and its gates passed, the Policy gate with a decision of PolicyEngineService/Policy.Decide of the action kind promotion that answered allow-with-approval for the class production, when EnvironmentPromotionService requests its approval, then exactly one approval of class production is open, with the subject kind Promotion and the promotion id as subject, bound to the release id and the target environment, release/approve-production waits on it without a request of its own, release/verify runs only after the promotion was handed off, and a decision by the requester of the run is refused (EnvironmentPromotionService/RequestPromotion, RunControlService/ApprovalRequested, release/approve-production, D133, D135, D139, D140, ADR-0015).
AC5 Given an approving decision on that approval, when the promotion completes, then PromotionApproved and PromotionCompleted are recorded and GetCurrentRelease of the target environment returns that release; a decision bound to another release id or another environment, a rejection or an expiry leaves GetCurrentRelease on the earlier release (EnvironmentPromotionService/PromotionApproved, EnvironmentPromotionService/PromotionCompleted, EnvironmentPromotionService/GetCurrentRelease, release/promote-production).
Traces: services PipelineExecutionService, ReleaseService, EnvironmentPromotionService, RunControlService, ConnectorRegistryService, PolicyEngineService, AgentRegistryService
Traces: workflows delivery-run, release
Traces: steps delivery-run/prepare-release, release/promote-staging, release/bake, release/approve-production, release/promote-production, release/verify
Traces: apis ReleaseService/CreateProductRelease, EnvironmentPromotionService/RequestPromotion, EnvironmentPromotionService/GetCurrentRelease, PolicyEngineService/Policy.Decide, AgentRegistryService/PublishRelease
Traces: events ConnectorRegistryService/DeliveryReceived, AgentRegistryService/AssetReleasePublished, PipelineExecutionService/ChangeProposalMerged, PipelineExecutionService/PipelineRunCompleted, ReleaseService/ReleaseCreated, ReleaseService/ReleaseReady, RunControlService/ApprovalRequested, EnvironmentPromotionService/PromotionApproved, EnvironmentPromotionService/PromotionCompleted
Traces: adrs ADR-0015
Traces: requirements FR-06
Depends on feature:verify-generate-a-microservice, feature:pipeline-execution-service-complete, feature:release-service, feature:environment-promotion-service, feature:delivery-host, feature:run-control-service, feature:connector-registry-service-deliveries, feature:agent-registry-service-publication, feature:policy-engine-service, feature:wf-project-bootstrap, feature:wf-delivery-run, feature:wf-release
Sources model/backlog/increments.yaml, model/workflows/delivery-run.yaml, model/workflows/release.yaml, model/workflows/project-bootstrap.yaml, model/services/devops-gitops/EnvironmentPromotionService.yaml, model/services/integration/ConnectorRegistryService.yaml, model/services/governance/PolicyEngineService.yaml, model/services/control-plane/AgentRegistryService.yaml, model/scenarios/release.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-5416 Precondition register of the delivery proof documentation A precondition register on the evidence page that lists each open link of D132 with the model file that closes it and its state, aligned or blocking: the pipeline of the generated repository (model/workflows/project-bootstrap.yaml), the inbound deliveries of the feature connector-registry-service-deliveries (model/services/integration/ConnectorRegistryService.yaml, D135), the tool of prepare-release that calls CreateProductRelease and readies the release (model/workflows/delivery-run.yaml), the tool of promote-staging that calls RequestPromotion (model/workflows/release.yaml), the action kind promotion of the Policy gate of EnvironmentPromotionService, aligned (model/services/governance/PolicyEngineService.yaml, D140), the publication of the I2 workflow definitions and their agents through the publication path of feature agent-registry-service-publication with the Published release each run pins, aligned (model/services/control-plane/AgentRegistryService.yaml, D140), and the preview entries of AIFACTORY-US-1344, whose action kind for creating a non-production environment the action kind promotion does not cover. ConnectSoft.AI.SoftwareFactory.Documentation
AIFACTORY-TASK-5397 Merge, pipeline run, release and promotion of the generated service operations One recorded pass on the acceptance environment from the merge of the change proposal of the replayed chain to the completed production promotion: the merged commit, the pipeline run identifier and its typed results, the release identifier with ReleaseCreated and ReleaseReady, the run of release, the staging promotion, the bake timer, the one production approval with its release id and environment and the decision. ConnectSoft.AI.SoftwareFactory.Documentation
AIFACTORY-TASK-5398 Refused, mismatched, rejected and expired production decisions operations Recorded refusals on the production approval: a decision by the requester of the run, which is refused; a decision bound to another release id and one bound to another environment, which do not promote; and a rejection and an expiry on separate promotions; GetCurrentRelease of the target environment keeps its earlier release in every case. ConnectSoft.AI.SoftwareFactory.Documentation
AIFACTORY-TASK-5399 Verify the delivery and promotion proof against its criteria verification The register, recorded runs, release, approval and current release are compared with AC1 to AC5 of AIFACTORY-US-1342 (PipelineExecutionService/PipelineRunCompleted, ReleaseService/ReleaseReady, EnvironmentPromotionService/PromotionApproved, EnvironmentPromotionService/GetCurrentRelease); a second production approval, an open register entry presented as passed, or a mismatch is named with its run identifier. ConnectSoft.AI.SoftwareFactory.Documentation

AIFACTORY-US-1343: Delivery proof: the Security, Observability and Infrastructure Blueprints of the product are produced and validated by their workflows with no person writing them

evidence · persona operator As an operator, I want the three blueprints the product needs to run produced and validated by the Factory from its design, so that the infrastructure of a generated service is planned by the Factory and not written by hand.

This PBI proves the demonstration of increment I2 that the Security, Observability and Infrastructure Blueprints of the product are produced and validated without a person writing them. The recorded run replays the I1 chain from the fixture brief on the I2 estate, after the I2 definitions are published, so that the readiness events of the replayed design arrive when the I2 definitions can hear them; the blueprints are the first part of the recorded run, before the preview, the merge and the promotion. Each blueprint has its producing workflow, as ADR-0030 requires of every blueprint kind: security-blueprint and observability-blueprint start when their readiness members are satisfied, and infrastructure-plan starts when the module, database, security and observability blueprints its activation names are recorded (model/workflows/infrastructure-plan.yaml). The fixture product has persistence, so it has a Database Blueprint and the database member is satisfied; under the D133 reading a product without persistence gets none. Each workflow drafts its blueprint with its agent, submits the draft through the tool step submit-version, which BlueprintService records as BlueprintSubmitted, and validates it through the tool step validate, which BlueprintService records as BlueprintValidated with the result. A person may decide an approval a step asks for, but no person writes or edits a blueprint version: the evidence shows that each version was submitted by the run that produced it. The infrastructure plan also generates its Pulumi program and a preview of it in a sandbox. A blueprint that fails validation fails its run with the issues as evidence, and the proof is recorded as failed.

Acceptance criteria

AC1 Given the I1 chain replayed from the fixture brief on the I2 estate with a product that has persistence, when the workflows security-blueprint, observability-blueprint and infrastructure-plan run, then each starts without a manual submission once the readiness members of model/workflows/infrastructure-plan.yaml and of its own definition are recorded, the database member is satisfied, and the run identifiers are in the evidence (ADR-0030, docs/architecture/adr/0030-a-producing-workflow-for-every-blueprint-kind.md).
AC2 Given each of the three runs, when its steps submit-version and validate complete, then a blueprint version of the kinds blueprint-security-v1, blueprint-observability-v1 and blueprint-infrastructure-v1 is submitted and validated as passed (BlueprintService/BlueprintSubmitted, BlueprintService/BlueprintValidated, security-blueprint/validate, observability-blueprint/validate, infrastructure-plan/validate).
AC3 Given the three validated versions, when their provenance is read, then each was submitted by the run that produced it and no version was created or edited by a person, and the infrastructure plan holds its generated program and the result of its preview (infrastructure-plan/preview, ADR-0030).
Traces: services BlueprintService
Traces: workflows security-blueprint, observability-blueprint, infrastructure-plan
Traces: steps security-blueprint/validate, observability-blueprint/validate, infrastructure-plan/validate, infrastructure-plan/preview
Traces: tools blueprint-submit-version, blueprint-validate
Traces: events BlueprintService/BlueprintSubmitted, BlueprintService/BlueprintValidated
Traces: descriptors blueprint-security-v1, blueprint-observability-v1, blueprint-infrastructure-v1
Traces: adrs ADR-0030
Depends on feature:verify-generate-a-microservice, feature:blueprint-service, feature:wf-security-blueprint, feature:wf-observability-blueprint, feature:wf-infrastructure-plan
Sources model/backlog/increments.yaml, docs/architecture/adr/0030-a-producing-workflow-for-every-blueprint-kind.md, model/workflows/infrastructure-plan.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-5400 Runs of the three blueprint workflows with the provenance of each version operations The run identifiers of security-blueprint, observability-blueprint and infrastructure-plan from the replayed chain on the acceptance environment, the satisfied readiness members including the database member, the three blueprint versions with their validation results and the submitter of each version, the generated Pulumi program and the result of its sandbox preview. ConnectSoft.AI.SoftwareFactory.Documentation
AIFACTORY-TASK-5401 Verify the blueprint proof against its criteria verification The recorded runs and versions are compared with AC1 to AC3 of AIFACTORY-US-1343 (BlueprintService/BlueprintValidated, infrastructure-plan/preview, ADR-0030); a version with a person as its author or a failed validation fails the check and is named. ConnectSoft.AI.SoftwareFactory.Documentation

AIFACTORY-US-1344: Delivery proof: a preview environment is created from the change proposal after its approval, used while its fixed time to live runs and torn down with its lifetime recorded

evidence · persona operator As an operator, I want a preview environment of the change proposal approved, created, used and torn down by the Factory, so that a preview never outlives its purpose and is never created without a decision.

This PBI proves the demonstration of increment I2 that a preview environment is provisioned, used and torn down. Decision D132 records three open links, entered in the precondition register of AIFACTORY-US-1342: RuntimeEnvironmentService models no operation that creates an environment (model/scenarios/preview-environment.yaml, SCN-preview-environment-003), policy-decision-v1 has no action kind for creating a non-production environment, and there is no source of the cost figure of a preview. While the operation or the action kind is missing the run is not started and the blocker is the evidence; no other action kind is borrowed. The missing cost source does not block: the teardown records the lifetime and marks the cost as unknown. The recorded run replays the I1 chain on the I2 estate, so preview-environment is activated by the new change proposal together with the passed Infrastructure Blueprint, after the three blueprints and before the merge. It resolves the proposal to a buildable change set. In I2 the step approve-preview always opens its approval request, because a policy guard on a Human step arrives only in I4 (D133): action class shared-write, proposal kind deployment-manifest, the change-set hash as proposal hash and the role Reviewer in project scope, never the requester of the run. A rejection or an expiry fails the run (ApprovalRejectedOrExpired) and no environment is created. On approval request-preview asks RuntimeEnvironmentService for the environment and the run output names its identity and address. A person uses it: the service answers its health route and one endpoint. The time to live is fixed once the timer of time-to-live is stored, since no signal extends a timer (SCN-preview-environment-004). The step teardown removes the environment and the inventory no longer lists it; a failed teardown ends the run Failed with an operator follow-up.

Acceptance criteria

AC1 Given the preview entries of the precondition register of AIFACTORY-US-1342, when they are checked before the run, then an operation of RuntimeEnvironmentService that creates an environment and an action kind for creating a non-production environment exist, and while either is missing the run is not started and the blocker is recorded; the missing source of the cost figure is recorded and does not block (D132, model/services/runtime-cloud/RuntimeEnvironmentService.yaml, model/scenarios/preview-environment.yaml).
AC2 Given the change proposal of the replayed chain and the passed Infrastructure Blueprint, when preview-environment reaches preview-environment/approve-preview, then an approval request opens with action class shared-write, proposal kind deployment-manifest, the change-set hash and the role Reviewer in project scope, and on an approving decision by a reviewer who is not the requester preview-environment/request-preview creates the environment and its observed state is recorded (RunControlService/ApprovalRequested, RuntimeEnvironmentService/ObservedStateChanged, RuntimeEnvironmentService/GetRuntimeInventory, D133).
AC3 Given the approval request of a second preview run, when it is rejected or expires, then the run ends Failed through ApprovalRejectedOrExpired and the inventory shows that no environment was created (RunControlService/RunFailed, RuntimeEnvironmentService/GetRuntimeInventory, preview-environment/approve-preview).
AC4 Given the created environment, when a person calls the health route and one endpoint of the service on its address, then both answer and the calls are recorded with the environment identity (preview-environment/request-preview).
AC5 Given the time to live fixed when its timer was stored, when it passes and the step preview-environment/teardown runs, then the environment is removed, its lifetime is recorded with the cost marked unknown while no cost source exists, and the inventory no longer lists it; a failed teardown ends the run Failed with an operator follow-up (preview-environment/time-to-live, RuntimeEnvironmentService/GetRuntimeInventory).
Traces: services RuntimeEnvironmentService, RunControlService
Traces: workflows preview-environment
Traces: steps preview-environment/approve-preview, preview-environment/request-preview, preview-environment/time-to-live, preview-environment/teardown
Traces: apis RuntimeEnvironmentService/GetRuntimeInventory
Traces: events RuntimeEnvironmentService/ObservedStateChanged, RunControlService/ApprovalRequested, RunControlService/RunFailed
Traces: adrs ADR-0015
Depends on AIFACTORY-US-1342, feature:verify-generate-a-microservice, feature:runtime-environment-service, feature:wf-preview-environment, feature:run-control-service
Sources model/backlog/increments.yaml, model/workflows/preview-environment.yaml, model/scenarios/preview-environment.yaml, model/services/runtime-cloud/RuntimeEnvironmentService.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-5402 Lifecycle of one preview environment on the acceptance environment operations One recorded run of preview-environment from the replayed chain with its approval request and decision, the identity and address of the environment, two calls of a person to the service on that address, the inventory before and after the teardown and the lifetime the teardown recorded with the cost marked unknown; and a second run whose approval is rejected or expires, with no environment in the inventory. ConnectSoft.AI.SoftwareFactory.Documentation
AIFACTORY-TASK-5403 Verify the preview proof against its criteria verification The register entries, recorded runs, calls and inventory are compared with AC1 to AC5 of AIFACTORY-US-1344 (preview-environment/approve-preview, preview-environment/request-preview, preview-environment/teardown, RuntimeEnvironmentService/GetRuntimeInventory); an environment created without an approving decision, or still listed after the teardown, fails the check. ConnectSoft.AI.SoftwareFactory.Documentation

AIFACTORY-US-030: Delivery is demonstrated with evidence

evidence · persona operator As an operator, I want to see the generated service built by a pipeline, running in a preview environment and promoted under approval, with the evidence recorded, so that the second outcome is accepted on facts.

This is the integration PBI of the feature and the closing proof of increment I2. The outcome of I2, as model/backlog/increments.yaml states it, is that the merged service is built by a pipeline, deployed to a preview environment and promoted under approval, and that the infrastructure it runs on is planned by the Factory from the design. The increment is finished when this proof passes, not when its services are deployed. The precondition register of AIFACTORY-US-1342 is checked first, including the inbound deliveries of the feature connector-registry-service-deliveries (D135); while an entry of D132 is open the run is not started and the blocker is the evidence. The change proposal and the blueprints of the proof of I1 were published before the I2 definitions existed, so they cannot open readiness correlations of I2. The recorded acceptance run therefore replays the I1 chain from the fixture brief on the I2 estate, so that its readiness events arrive after the I2 definitions are published, and runs the demonstrations in this order: the Security, Observability and Infrastructure Blueprints of AIFACTORY-US-1343, then the preview of the new change proposal of AIFACTORY-US-1344, then its merge, then the pipeline run, the release and the promotion under the one production approval of AIFACTORY-US-1342. The evidence pack holds the run identifiers in that order, the pipeline and release references, the approval with its release id and environment, the blueprint versions and the environment inventory. A demonstration that fails is recorded with its failing step and the increment stays open; nothing is waived. The done_when of the epics devops-gitops and runtime-cloud reads this proof as the outcome verification of I2.

Acceptance criteria

AC1 Given the precondition register and the I1 chain replayed from the fixture brief on the I2 estate, when the recorded acceptance run is read by its run identifiers, then the blueprint runs precede the preview run, the preview run precedes the merge of the same change proposal, and the merge precedes the pipeline run, the release and the promotion, as AIFACTORY-US-1342, AIFACTORY-US-1343 and AIFACTORY-US-1344 record them (preview-environment, delivery-run, release, model/backlog/increments.yaml).
AC2 Given the merged change of the replayed chain, when its pipeline runs, then the recorded results and the ready release are linked from the evidence, as AIFACTORY-US-1342 proves it (PipelineExecutionService, ReleaseService).
AC3 Given the design of the product, when the security, observability and infrastructure workflows run, then three validated blueprints exist and no person wrote one of them, as AIFACTORY-US-1343 proves it (security-blueprint, observability-blueprint, infrastructure-plan).
AC4 Given the change proposal, when a preview environment is approved, created and its time to live passes, then creation, use and teardown are recorded, as AIFACTORY-US-1344 proves it (preview-environment, RuntimeEnvironmentService).
AC5 Given the ready release, when it is promoted to production, then the one approval names the release id and the environment and the current release of the target environment is that release; and the evidence pack, reviewed against the outcome of I2 in model/backlog/increments.yaml, has every demonstration or its recorded failure or blocker (EnvironmentPromotionService, ADR-0029).
Traces: services PipelineExecutionService, ReleaseService, EnvironmentPromotionService, RuntimeEnvironmentService
Traces: workflows delivery-run, security-blueprint, observability-blueprint, infrastructure-plan, preview-environment, release
Traces: adrs ADR-0029
Depends on AIFACTORY-US-1342, AIFACTORY-US-1343, AIFACTORY-US-1344
Sources model/backlog/increments.yaml, model/backlog/epics.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-342 Run the four demonstrations and record the evidence documentation An evidence page with the precondition register, the run identifiers in the order of the recorded run, pipeline and release references, the approval with its release id and environment, the blueprint versions and the environment inventory, from one recorded acceptance run of AIFACTORY-US-1343, AIFACTORY-US-1344 and AIFACTORY-US-1342. ConnectSoft.AI.SoftwareFactory.Documentation
AIFACTORY-TASK-305 Evidence pack for increment I2 documentation A recorded run of every demonstration below with its run identifiers, artifacts and logs: The merged change triggers a pipeline run whose results are recorded. The Security, Observability and Infrastructure Blueprints of the product are produced and validated without a person writing them. A preview environment is provisioned, used and torn down. A promotion to the next environment waits for an approval bound to the exact release. ConnectSoft.AI.SoftwareFactory.Documentation
AIFACTORY-TASK-775 Verify delivery-demonstrated against the recorded acceptance run verification The evidence pack is compared with AC1 to AC5 of AIFACTORY-US-030 and with the outcome of I2 in model/backlog/increments.yaml; the run identifiers show the order blueprints, preview, merge, pipeline run, release and promotion, every demonstration has its evidence or its blocker, and python -I tools/docs_model validate passes with the evidence page in place. ConnectSoft.AI.SoftwareFactory.Documentation