Skip to content

Epic: Engineering readiness

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-017 · domain readiness

Work that must be done once before or beside the services: repository and pipeline conventions for one repository per service, the trusted scope chain, the contracts package, the durable execution spike, the local development environment, the command-line client and the owner decisions that are still open.

Features across the increments

Increment Feature Phase State Delivers Depends on
I0 AIFACTORY-FEAT-088 Repository and pipeline conventions for one repository per service development elaborated — AIFACTORY-FEAT-156, AIFACTORY-FEAT-159, AIFACTORY-FEAT-090
I0 AIFACTORY-FEAT-089 Trusted tenant and project scope from the edge to a service development elaborated — —
I0 AIFACTORY-FEAT-090 Contracts package from the published schemas development elaborated — —
I0 AIFACTORY-FEAT-091 Durable execution substrate verified against pinned versions development elaborated — —
I0 AIFACTORY-FEAT-092 Local development environment for a Factory service development elaborated — —
I0 AIFACTORY-FEAT-093 Command-line client for the first outcome development elaborated — —
I0 AIFACTORY-FEAT-094 Import of the backlog draft by the owner development elaborated — —
I1 AIFACTORY-FEAT-187 Commands of the command-line client against the control plane gateway development elaborated — AIFACTORY-FEAT-093, AIFACTORY-FEAT-002, AIFACTORY-FEAT-178
I1 AIFACTORY-FEAT-178 Typed client libraries for the Factory gateways from the API library template development elaborated — AIFACTORY-FEAT-090, AIFACTORY-FEAT-180