# 5.1 General, ISO 42102 Previous: 5 AI system methods dimensionNext: 5.2 Traditional AI 5.1 Clause # General The general subclause introduces the method descriptors and the way they are intended to be read. The public preview does not carry the descriptor list, so this page describes the method of reading rather than inventing entries. - methods clause - ISO/IEC DIS 42102 - Last updated: 2026-10-22 ## What this settles A descriptor set is only comparable if readers agree what counts as an entry. The general subclause is where that agreement belongs, before the four families are populated. ## Who it binds The organisation, as a method choice. It sets no duty, but it sets the discipline a comparable description needs. ## What to do in your practice Write a short rule for when a method gets its own row: does it change the mechanism, the failure mode or the evidence needed? If not, it belongs inside the parent row as a note. That rule keeps the register from becoming a parts list. ## Evidence an auditor or regulator asks for Three artefacts that make this unit checkableA method entry rule with two worked examples.Shows the register has a consistent granularity. Two systems entered under the same rule.Proves the rule is usable by more than its author. A review note where an entry was merged or split.Shows the rule is applied and revisable. Ask your teamWhat makes a method worth its own row in our register, and would a colleague apply the same test? ## Common gaps this page catches - Every component becomes a row, so the register is a parts list rather than a description. - Rows are merged so aggressively that a different failure mode is hidden. - No entry rule exists, so two teams produce incompatible registers. ## What to prepare before publication Write the entry rule on one page and test it on two dissimilar systems. Adjust it before the wider roll-out. ## How to test it here Take one live system rather than a template, find the field or sentence where General is used, and put this page beside it. Record the answer, the artefact and the date. A glossary entry on its own is an intention; a dated record beside a live artefact is evidence. ## What this page does not claim The page does not reproduce the draft, does not know the descriptor wording that the public preview withholds, and does not certify the system or the organisation. It states the unit at the claim level "methods clause" and stops where the public record stops. ## Common questions What does General mean in ISO/IEC DIS 42102? The general subclause introduces the method descriptors and the way they are intended to be read. The public preview does not carry the descriptor list, so this page describes the method of reading rather than inventing entries. What evidence should we keep for 5.1? A method entry rule with two worked examples. Two systems entered under the same rule. Is General a requirement? No. The draft is a descriptive framework. It sets no management system requirement and no conformity test. It becomes binding only when a contract, a regulator or a management system adopts it. ## Related units - 5 AI system methods dimension - 5.2 Traditional AI - 5.4 Machine learning ## Source and claim ISO/IEC DIS 42102, Clause 5.1, General Open the ISO public entry https://www.iso.org/standard/86898.html Retrieved 22 October 2026. The heading is in the public preview; the body is not. ## The record Stage 40.60, Close of voting, recorded 8 September 2026. Planning date 16 September 2027, an estimate. See the basis. The draft record · How it is built ## Check your own system Build the method and capability matrix from ten answers and see which cells still need evidence. Run the free check Nothing here is guessed while you wait. Every line is written from the public ISO record and the public preview, and points to the exact clause it came from. How the record is built. Last updated: 2026-10-22 · Markdown version · Check your system Source: https://iso-42102-revision-checker.theartofservice.com/methods/methods-general/