DevOps / GitOps — later capabilities¶
Target
This page describes intended behaviour or structure. No implementation is claimed unless a section is explicitly marked Current implementation or Evidence.
No later-stage services.
| Capability | Owner when built | Taken up when |
|---|---|---|
| Pipeline definitions generated from the pipeline blueprint and validated before commit | BC-23 with Template & Library | the pipeline blueprint schema (B1) is published |
| Test-impact selection from repository intelligence | BC-23 with BC-39 | the dependency index covers test projects |
| Flaky-test tracking as a typed result | BC-23 | enough runs per project to detect flakiness |
| Signed releases with the Factory's workload identity; SLSA level targets per edition | BC-24 with the Secret Broker | an edition requires it (D34) |
| Dependency-vulnerability re-scans of Released components with advisories as alerts | BC-24 with Observability | a scanner connector is certified |
| Automatic canary analysis against SLOs | BC-24 with Observability | objectives per product exist (P12) |
| Promotion windows and freeze periods per tenant | BC-24 | a tenant asks for change-calendar control |
| Second system of record (GitLab) | BC-23 with Integration | a certified connector exists |
| Fleet-wide rollout orchestration over single-environment promotions | Product Fleet Operations (BC-36) | P12 |