So far every lesson in X4 has delivered a check: scans (4.3), cases for the limits (4.5), pin and canary (4.6). Single pieces become a procedure only when a pipeline puts them in an order and every stage knows what it must know before the next one begins. The lesson asks: Which check runs when, what stops a gate, and in which order does the infrastructure come into being?
Prior knowledge. "K3, lesson 3.7.1" (CI with GitHub Actions), "3.7.3" (tests in the build: exit code, results, minimum number of tests) and "3.7.6" (approvals before the deploy) teach the pipeline; "K3, lesson 3.8.1" the integration test against real dependencies, "3.2.4" what-if and its limits. "AI-103, lesson 1.2" shows Bicep per environment, sign-in without a key and two identities for infrastructure and agent version. "AI track, lesson T9.5" puts the quality gate with thresholds into the build. None of this is repeated; new is what a team of agents adds to it.
New in this lesson. (1) Four stages of the pipeline are named like the environments: pr (no account), test, abnahme, prod (4.6). (2) The gate to acceptance from 4.6 is a function with four numbers (below); it is not the change gate from 3.2, which adopts a suggestion only on a gain, but demands: not worse than the stable version. (3) The pipeline writes a release entry per version (hash of the files, number per environment, result of the gate), as 4.6 demands.
The requirement
All numbers are assumptions of the task.
| No. | Requirement | Type | Measure | Weight | Source |
|---|---|---|---|---|---|
| 4.7-01 | Every change (code, prompt file, rule data, Bicep) runs through the same pipeline. | R | 0 manual steps | Must | F-07 |
| 4.7-02 | A pull request needs no account and no model call. | F | 0 calls | Must | F-06 |
| 4.7-03 | The evaluation with a model runs only after the merge and has an upper limit. | Q | at most 60 cases times 20 calls per evaluation | Must | R-09, 0.2 |
| 4.7-04 | No rollout without a prior what-if preview; prod only after approval by a person. |
R | 100 % | Must | M-09 |
| 4.7-05 | The pipeline holds no secret. | R | 0 keys | Must | R-07 |
| 4.7-06 | For every version in prod there is an entry that traces it back to files and gate. |
F | 100 % | Should | 4.6 |