Skip to content

Epic: Outcome verification

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).

AIFACTORY-EPIC-020 · domain verification

One feature per increment that demonstrates the increment's outcome end to end with recorded evidence. An increment is finished when its verification feature passes, not when its services are deployed.

Features across the increments

Increment Feature Phase State Delivers Depends on
I0 AIFACTORY-FEAT-138 Demonstrate I0: Readiness development elaborated — —
I1 AIFACTORY-FEAT-139 Demonstrate I1: Generate a microservice development elaborated — —
I2 AIFACTORY-FEAT-140 Demonstrate I2: Deliver it development elaborated — —
I3 AIFACTORY-FEAT-141 Demonstrate I3: Studio development elaborated — —
I4 AIFACTORY-FEAT-142 Demonstrate I4: Trust and accountability development elaborated — —
I5 AIFACTORY-FEAT-143 Demonstrate I5: Knowledge and connections development outline — —
I6 AIFACTORY-FEAT-144 Demonstrate I6: Full product generation development outline — —
I7 AIFACTORY-FEAT-145 Demonstrate I7: Operate and commercialise development outline — —
I8 AIFACTORY-FEAT-146 Demonstrate I8: Expansion development outline — —