The final clause walks the pipeline as one example process, so a reader can see the stages in sequence rather than as separate definitions.
What the base framework establishes
The public contents gives this clause its own page and title. It uses the pipeline to show an example machine learning process, which is the framework's way of turning the stage definitions into a sequence a project can follow. The clause is descriptive and creates no duty. Its value is pedagogical: a team can compare its own delivery process with the example and see which stage it has skipped. The clause text is not in the public sample, so this page describes the role the public contents gives it and does not invent its steps.
Why it matters to an AI management system
An example is a mirror. Most project post-mortems find a stage that was compressed or skipped, and the example makes that visible without anyone having to admit it first. Use it in the project kickoff and again at the retrospective.
The public draft summary names no change to 8.8 Example machine learning process based on the pipeline. The final text could still touch it.
Evidence a reviewer samples
| Category | Artefact |
|---|---|
| Project pipeline map | The project's stages set against the example process. |
| Skipped-stage note | Any stage compressed or omitted, with the risk accepted. |
| Retrospective record | What the comparison showed and what changed next time. |
One question to prepare for. Which stage of the pipeline did your last project compress, and who accepted that risk?
Common gaps
- The project has no pipeline map and cannot be compared.
- A stage is skipped and the skip is not recorded as a risk decision.
- The example is treated as a mandatory sequence rather than an illustration.
Prepare before publication
Map one live project to the example and record any skipped stage with its risk acceptance. Repeat at the next retrospective.
Dates that matter
No separate date attaches to 8.8; the record dates are the stage date, the planning estimate and the CEN expectation stated above.
Cross-references
8.1 General · 8.2 Data acquisition · 8.7 Operation
Source
Source for 8.8: ISO/IEC 23053:2022, clause 8.8. The public sample stops before 8.8, so this page relies on the public contents and the public summary and does not quote the clause. The two official records are linked on this page so any line can be checked.
Not legal advice; does not certify. A reading of the framework and the evidence a reviewer commonly samples, not a substitute for the standard or your auditor's rules.