This subclause groups the algorithm families the framework recognises. The draft inserts the transformer and generative model entries here.
What the base framework establishes
The public contents places the categories of ML algorithms under the tools component, between data preparation and optimisation methods. The group is the framework's catalogue of model families, and the public draft of Amendment 1 adds two entries to it: transformer architecture and algorithm at 6.5.3.2.9, and generative model at 6.5.3.2.10. The existing entries and their numbering are not changed in the public record. The full subclause text is not in the public sample, so this page describes the catalogue's function and the two documented additions rather than quoting the list.
Why it matters to an AI management system
A catalogue is a control on vocabulary. If the algorithm choice is recorded against a named family, a reviewer can ask why that family and what evidence it needs. The two additions mean a generative system can now be recorded in the same catalogue as a classifier, instead of in a separate spreadsheet nobody reviews.
The public draft adds material at 6.5.3. Its final wording is not held, so this page records what the draft summary states and does not present it as published text. The public draft summary states two new entries at 6.5.3.2.9 and 6.5.3.2.10. The final wording of the subclause and the new entries is not held.
Evidence a reviewer samples
| Category | Artefact |
|---|---|
| Algorithm catalogue entry | The family, the reason for the choice and the alternatives rejected. |
| Amendment mapping | Which systems fall under the two new entries. |
| Review record | The reviewer, the date and the decision on the family choice. |
One question to prepare for. Which entry in the algorithm catalogue does each of your models sit under?
Common gaps
- Algorithm choices are recorded per project in inconsistent language.
- The catalogue predates the generative systems and has no entry for them.
- No reviewer sees the choice until the model is built.
Prepare before publication
Align the model card's algorithm field to the catalogue, add the two new family values, and put the choice on the design review agenda.
Dates that matter
No separate date attaches to 6.5.3; the record dates are the stage date, the planning estimate and the CEN expectation stated above.
Cross-references
6.5 Tools · 6.5.3.2.9 Transformer architecture and algorithm · 6.5.3.2.10 Generative model · 8.4 Modelling
Source
Source for 6.5.3: ISO/IEC 23053:2022, clause 6.5.3, with FDAmd 1 additions (public draft summary). The public sample stops before 6.5.3, 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.