-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathplaybook_remediation_proposals.json
More file actions
496 lines (496 loc) · 27.8 KB
/
Copy pathplaybook_remediation_proposals.json
File metadata and controls
496 lines (496 loc) · 27.8 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
{
"version": "0.4.0",
"total_divergences": 41,
"by_severity": {
"1": 31,
"2": 9,
"3": 1
},
"by_type": {
"wording": 25,
"typo": 1,
"semantic": 1,
"whitespace": 6,
"capitalisation": 8
},
"systemic_findings": [
{
"id": "S-1",
"title": "Function-name casing inconsistency",
"summary": "AI RMF Core uses lowercase function names with the definite article inside control statements (e.g., 'as identified in the map function'). Playbook consistently uses uppercase ('the MAP function').",
"scope": "12 controls",
"controls_affected": [
"MAP-3.5 (GOVERN function reference, with article addition)",
"MEASURE-1.1, 2.4, 2.7, 2.8, 2.10, 2.11, 2.12 (MAP function — pure capitalisation)",
"MEASURE-2.6, 2.9 (MAP function — capitalisation bundled with other wording changes)",
"MEASURE-2.13 (MEASURE function — self-reference)",
"MANAGE-1.3 (MAP function reference, with comma addition)"
],
"recommendation": "Rather than 12 per-control patches, the Playbook editorial process should adopt a single style rule: 'When referring to the four AI RMF functions inside a control description, use lowercase ({govern, map, measure, manage}) preceded by the definite article'. This matches AI RMF Core Section 5 and brings all 12 controls into alignment in one edit."
},
{
"id": "S-2",
"title": "Hyphenation of 'third-party'",
"summary": "AI RMF Core itself is internally inconsistent: GOVERN 6.1 uses hyphenated 'third-party's intellectual property'; MAP 4.1 uses open 'third party's intellectual property'. Playbook mirrors the inverse choice in each location.",
"scope": "2 controls (Core + Playbook both involved)",
"controls_affected": [
"GOVERN-6.1",
"MAP-4.1"
],
"recommendation": "This is a Core-side finding, not a Playbook-side correction. Recommend the AI RMF Core editorial team standardise to one form — Chicago Manual of Style and APA both prefer hyphenated 'third-party' as an attributive adjective. Once Core is consistent, Playbook can be aligned."
}
],
"proposals": [
{
"control_id": "ai-rmf-gv-1.2",
"function": "GOVERN",
"subcategory": "1.2",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Append ', and practices' after 'processes, procedures'.",
"rationale": "Core text enumerates 'policies, processes, procedures, and practices'. Playbook drops the 'and practices' clause, narrowing the enumeration.",
"core_text": "The characteristics of trustworthy AI are integrated into organizational policies, processes, procedures, and practices."
},
{
"control_id": "ai-rmf-gv-1.3",
"function": "GOVERN",
"subcategory": "1.3",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Replace 'Processes and procedures' with 'Processes, procedures, and practices'.",
"rationale": "Core uses the three-term enumeration consistently across GOVERN 1.x; Playbook uses two terms here.",
"core_text": "Processes, procedures, and practices are in place to determine the needed level of risk management activities based on the organization's risk tolerance."
},
{
"control_id": "ai-rmf-gv-1.5",
"function": "GOVERN",
"subcategory": "1.5",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Replace ', organizational roles and responsibilities are clearly defined,' with ' and organizational roles and responsibilities clearly defined,'.",
"rationale": "Core uses 'and' to coordinate two clauses; Playbook uses comma + finite verb.",
"core_text": "Ongoing monitoring and periodic review of the risk management process and its outcomes are planned and organizational roles and responsibilities clearly defined, including determining the frequency of periodic review."
},
{
"control_id": "ai-rmf-gv-1.7",
"function": "GOVERN",
"subcategory": "1.7",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Remove the word 'of' between 'phasing out' and 'AI systems'.",
"rationale": "Core: 'phasing out AI systems'; Playbook: 'phasing out of AI systems'.",
"core_text": "Processes and procedures are in place for decommissioning and phasing out AI systems safely and in a manner that does not increase risks or decrease the organization’s trustworthiness."
},
{
"control_id": "ai-rmf-gv-3.1",
"function": "GOVERN",
"subcategory": "3.1",
"type": "typo",
"severity": 2,
"recommendation": "adopt-core",
"patch": "Replace 'Decision-makings' with 'Decision-making'.",
"rationale": "Singular 'Decision-making' is the canonical AI RMF Core form and is grammatically standard in English. Playbook 'Decision-makings' is a clear typographical error.",
"core_text": "Decision-making related to mapping, measuring, and managing AI risks throughout the lifecycle is informed by a diverse team (e.g., diversity of demographics, disciplines, experience, expertise, and backgrounds)."
},
{
"control_id": "ai-rmf-gv-4.1",
"function": "GOVERN",
"subcategory": "4.1",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Remove the comma between 'policies' and 'and practices'. Insert 'potential ' before 'negative impacts'.",
"rationale": "Core: 'Organizational policies and practices ... minimize potential negative impacts.' Playbook adds a stray comma and drops 'potential'.",
"core_text": "Organizational policies and practices are in place to foster a critical thinking and safety-first mindset in the design, development, deployment, and uses of AI systems to minimize potential negative impacts."
},
{
"control_id": "ai-rmf-gv-4.2",
"function": "GOVERN",
"subcategory": "4.2",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Insert comma between 'evaluate' and 'and use'. Replace 'and communicate' with 'and they communicate'.",
"rationale": "Core uses the Oxford comma in the verb list and supplies the explicit pronoun subject 'they' in the second coordinated clause for clarity.",
"core_text": "Organizational teams document the risks and potential impacts of the AI technology they design, develop, deploy, evaluate, and use, and they communicate about the impacts more broadly."
},
{
"control_id": "ai-rmf-gv-5.2",
"function": "GOVERN",
"subcategory": "5.2",
"type": "semantic",
"severity": 3,
"recommendation": "adopt-core",
"patch": "Replace the FIRST occurrence of 'AI actors' with 'the team that developed or deployed AI systems'. The second occurrence ('from relevant AI actors' later in the sentence) is unchanged in Core and must be preserved — a global find-replace would corrupt it.",
"rationale": "Substantive divergence. Core narrows the obligated party to the team that developed or deployed AI systems; Playbook generalises to all 'AI actors' (which in AI RMF terminology includes users, regulators, and impacted communities). The two sets are not interchangeable. Compliance work that cites Playbook would assign the obligation to the wrong actors.",
"core_text": "Mechanisms are established to enable the team that developed or deployed AI systems to regularly incorporate adjudicated feedback from relevant AI actors into system design and implementation."
},
{
"control_id": "ai-rmf-gv-6.1",
"function": "GOVERN",
"subcategory": "6.1",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core-with-caveat",
"patch": "Replace 'third party' with 'third-party' (hyphenated).",
"rationale": "Core text at GOVERN 6.1 uses hyphenated 'third-party's', while Core text at MAP 4.1 uses unhyphenated 'third party's'. The Core itself is internally inconsistent; this proposal recommends Playbook align with whichever form Core selects after Core-side standardisation. See systemic finding S-2.",
"core_text": "Policies and procedures are in place that address AI risks associated with third-party entities, including risks of infringement of a third-party’s intellectual property or other rights."
},
{
"control_id": "ai-rmf-mg-1.1",
"function": "MANAGE",
"subcategory": "1.1",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Replace 'intended purpose' with 'intended purposes' (plural).",
"rationale": "Core uses plural. Same pattern as MAP 1.1.",
"core_text": "A determination is made as to whether the AI system achieves its intended purposes and stated objectives and whether its development or deployment should proceed."
},
{
"control_id": "ai-rmf-mg-1.2",
"function": "MANAGE",
"subcategory": "1.2",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Replace 'or available resources or methods' with 'and available resources or methods'.",
"rationale": "'and' vs 'or' changes the scope: Core lists impact, likelihood, AND available resources as joint inputs; Playbook reads as alternative inputs.",
"core_text": "Treatment of documented AI risks is prioritized based on impact, likelihood, and available resources or methods."
},
{
"control_id": "ai-rmf-mg-1.3",
"function": "MANAGE",
"subcategory": "1.3",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Insert comma after 'high priority'. Replace 'Map function' with 'map function'.",
"rationale": "Punctuation and function-name casing. See systemic finding S-1.",
"core_text": "Responses to the AI risks deemed high priority, as identified by the map function, are developed, planned, and documented. Risk response options can include mitigating, transferring, avoiding, or accepting."
},
{
"control_id": "ai-rmf-mg-2.1",
"function": "MANAGE",
"subcategory": "2.1",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Replace ', along with viable non-AI alternative systems, approaches, or methods,' with ' – along with viable non-AI alternative systems, approaches, or methods –'.",
"rationale": "Core uses en-dash bracketing; Playbook uses commas.",
"core_text": "Resources required to manage AI risks are taken into account – along with viable non-AI alternative systems, approaches, or methods – to reduce the magnitude or likelihood of potential impacts."
},
{
"control_id": "ai-rmf-mg-2.4",
"function": "MANAGE",
"subcategory": "2.4",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Replace 'Mechanisms are in place and applied, responsibilities are assigned and understood to' with 'Mechanisms are in place and applied, and responsibilities are assigned and understood, to'.",
"rationale": "Adds connective 'and' and bracketing comma.",
"core_text": "Mechanisms are in place and applied, and responsibilities are assigned and understood, to supersede, disengage, or deactivate AI systems that demonstrate performance or outcomes inconsistent with intended use."
},
{
"control_id": "ai-rmf-mg-3.2",
"function": "MANAGE",
"subcategory": "3.2",
"type": "whitespace",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Replace double space between 'regular' and 'monitoring' with single space.",
"rationale": "Pure whitespace.",
"core_text": "Pre-trained models which are used for development are monitored as part of AI system regular monitoring and maintenance."
},
{
"control_id": "ai-rmf-mg-4.3",
"function": "MANAGE",
"subcategory": "4.3",
"type": "whitespace",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Insert comma after 'AI actors' (before 'including affected communities').",
"rationale": "Core uses non-restrictive comma.",
"core_text": "Incidents and errors are communicated to relevant AI actors, including affected communities. Processes for tracking, responding to, and recovering from incidents and errors are followed and documented."
},
{
"control_id": "ai-rmf-mp-1.1",
"function": "MAP",
"subcategory": "1.1",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Replace 'Intended purpose' with 'Intended purposes'. Insert 'the' before 'specific set or types of users'. Replace 'about AI system purposes; uses and risks' with 'about AI system purposes, uses, and risks'. Replace 'TEVV and system metrics' with 'related TEVV and system metrics'.",
"rationale": "Multiple wording differences across one long sentence. Core text uses plural 'purposes', restructures the second list with an Oxford comma, and prefixes 'related' to the metrics phrase.",
"core_text": "Intended purposes, potentially beneficial uses, context-specific laws, norms and expectations, and prospective settings in which the AI system will be deployed are understood and documented. Considerations include: the specific set or types of users along with their expectations; potential positive and negative impacts of system uses to individuals, communities, organizations, society, and the planet; assumptions and related limitations about AI system purposes, uses, and risks across the development or product AI lifecycle; and related TEVV and system metrics."
},
{
"control_id": "ai-rmf-mp-1.2",
"function": "MAP",
"subcategory": "1.2",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Replace 'Inter-disciplinary' with 'Interdisciplinary' (no hyphen). Insert comma after 'skills'.",
"rationale": "Spelling and punctuation alignment.",
"core_text": "Interdisciplinary AI actors, competencies, skills, and capacities for establishing context reflect demographic diversity and broad domain and user experience expertise, and their participation is documented. Opportunities for interdisciplinary collaboration are prioritized."
},
{
"control_id": "ai-rmf-mp-1.3",
"function": "MAP",
"subcategory": "1.3",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Replace 'the AI technology' with 'AI technology' (drop definite article).",
"rationale": "Core uses bare 'AI technology'.",
"core_text": "The organization’s mission and relevant goals for AI technology are understood and documented."
},
{
"control_id": "ai-rmf-mp-1.6",
"function": "MAP",
"subcategory": "1.6",
"type": "whitespace",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Replace double space between 'AI actors.' and 'Design decisions' with a single space.",
"rationale": "Pure typographical: extra space character in Playbook.",
"core_text": "System requirements (e.g., “the system shall respect the privacy of its users”) are elicited from and understood by relevant AI actors. Design decisions take socio-technical implications into account to address AI risks."
},
{
"control_id": "ai-rmf-mp-2.1",
"function": "MAP",
"subcategory": "2.1",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Replace 'specific task, and methods used to implement the task, that the AI system will support is' with 'specific tasks and methods used to implement the tasks that the AI system will support are'.",
"rationale": "Singular vs plural and removal of comma-bounded apposition.",
"core_text": "The specific tasks and methods used to implement the tasks that the AI system will support are defined (e.g., classifiers, generative models, recommenders)."
},
{
"control_id": "ai-rmf-mp-2.2",
"function": "MAP",
"subcategory": "2.2",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Remove the word 'informed' before 'decisions'.",
"rationale": "Core: 'when making decisions'; Playbook: 'when making informed decisions'.",
"core_text": "Information about the AI system’s knowledge limits and how system output may be utilized and overseen by humans is documented. Documentation provides sufficient information to assist relevant AI actors when making decisions and taking subsequent actions."
},
{
"control_id": "ai-rmf-mp-3.2",
"function": "MAP",
"subcategory": "3.2",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Replace ASCII hyphen-minus '-' bracketing 'as connected to organizational risk tolerance' with en dashes '–'.",
"rationale": "Typographic dash. Core uses en dashes; Playbook uses hyphen-minus.",
"core_text": "Potential costs, including non-monetary costs, which result from expected or realized AI errors or system functionality and trustworthiness – as connected to organizational risk tolerance – are examined and documented."
},
{
"control_id": "ai-rmf-mp-3.4",
"function": "MAP",
"subcategory": "3.4",
"type": "whitespace",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Insert Oxford comma between 'assessed' and 'and documented'.",
"rationale": "Core uses the Oxford comma; Playbook drops it.",
"core_text": "Processes for operator and practitioner proficiency with AI system performance and trustworthiness – and relevant technical standards and certifications – are defined, assessed, and documented."
},
{
"control_id": "ai-rmf-mp-3.5",
"function": "MAP",
"subcategory": "3.5",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Replace 'GOVERN function' with 'the govern function' (lowercase, with article).",
"rationale": "Function-name casing. Core uses lowercase 'govern function' with the definite article. See systemic finding S-1 — same pattern as the function-name casing instances in MEASURE and MANAGE controls (12 controls touched in total).",
"core_text": "Processes for human oversight are defined, assessed, and documented in accordance with organizational policies from the govern function."
},
{
"control_id": "ai-rmf-mp-4.1",
"function": "MAP",
"subcategory": "4.1",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core-with-caveat",
"patch": "Replace 'third-party' (hyphenated) with 'third party' (open).",
"rationale": "Internally inconsistent within Core. Core MAP 4.1 uses 'third party' open; Core GOVERN 6.1 uses 'third-party' hyphenated. Recommend Core editorial team standardise. See systemic finding S-2.",
"core_text": "Approaches for mapping AI technology and legal risks of its components – including the use of third-party data or software – are in place, followed, and documented, as are risks of infringement of a third party’s intellectual property or other rights."
},
{
"control_id": "ai-rmf-mp-4.2",
"function": "MAP",
"subcategory": "4.2",
"type": "whitespace",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Insert commas around 'including third-party AI technologies'.",
"rationale": "Core punctuates as a non-restrictive parenthetical with bracketing commas.",
"core_text": "Internal risk controls for components of the AI system, including third-party AI technologies, are identified and documented."
},
{
"control_id": "ai-rmf-ms-1.1",
"function": "MEASURE",
"subcategory": "1.1",
"type": "capitalisation",
"severity": 2,
"recommendation": "adopt-core",
"patch": "Replace 'the Map function' (capital M) with 'the map function' (lowercase).",
"rationale": "Function-name casing. See systemic finding S-1.",
"core_text": "Approaches and metrics for measurement of AI risks enumerated during the map function are selected for implementation starting with the most significant AI risks. The risks or trustworthiness characteristics that will not – or cannot – be measured are properly documented."
},
{
"control_id": "ai-rmf-ms-1.2",
"function": "MEASURE",
"subcategory": "1.2",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Replace 'is regularly assessed' with 'are regularly assessed'. Insert comma after 'updated'. Insert 'potential ' before 'impacts on affected communities'.",
"rationale": "Subject-verb agreement, comma, and 'potential' prefix.",
"core_text": "Appropriateness of AI metrics and effectiveness of existing controls are regularly assessed and updated, including reports of errors and potential impacts on affected communities."
},
{
"control_id": "ai-rmf-ms-2.1",
"function": "MEASURE",
"subcategory": "2.1",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Replace 'used during test, evaluation, validation, and verification (TEVV)' with 'used during TEVV'.",
"rationale": "Core uses the abbreviation; Playbook expands it inline.",
"core_text": "Test sets, metrics, and details about the tools used during TEVV are documented."
},
{
"control_id": "ai-rmf-ms-2.10",
"function": "MEASURE",
"subcategory": "2.10",
"type": "capitalisation",
"severity": 2,
"recommendation": "adopt-core",
"patch": "Replace 'MAP function' with 'map function'.",
"rationale": "Function-name casing. See systemic finding S-1.",
"core_text": "Privacy risk of the AI system – as identified in the map function – is examined and documented."
},
{
"control_id": "ai-rmf-ms-2.11",
"function": "MEASURE",
"subcategory": "2.11",
"type": "capitalisation",
"severity": 2,
"recommendation": "adopt-core",
"patch": "Replace 'MAP function' with 'map function'.",
"rationale": "Function-name casing. See systemic finding S-1.",
"core_text": "Fairness and bias – as identified in the map function – are evaluated and results are documented."
},
{
"control_id": "ai-rmf-ms-2.12",
"function": "MEASURE",
"subcategory": "2.12",
"type": "capitalisation",
"severity": 2,
"recommendation": "adopt-core",
"patch": "Replace 'MAP function' with 'map function'.",
"rationale": "Function-name casing. See systemic finding S-1.",
"core_text": "Environmental impact and sustainability of AI model training and management activities – as identified in the map function – are assessed and documented."
},
{
"control_id": "ai-rmf-ms-2.13",
"function": "MEASURE",
"subcategory": "2.13",
"type": "capitalisation",
"severity": 2,
"recommendation": "adopt-core",
"patch": "Replace 'MEASURE function' with 'measure function'.",
"rationale": "Function-name casing. See systemic finding S-1 (note: this one is the MEASURE function, not MAP).",
"core_text": "Effectiveness of the employed TEVV metrics and processes in the measure function are evaluated and documented."
},
{
"control_id": "ai-rmf-ms-2.4",
"function": "MEASURE",
"subcategory": "2.4",
"type": "capitalisation",
"severity": 2,
"recommendation": "adopt-core",
"patch": "Replace 'MAP function' with 'map function'.",
"rationale": "Function-name casing. See systemic finding S-1.",
"core_text": "The functionality and behavior of the AI system and its components – as identified in the map function – are monitored when in production."
},
{
"control_id": "ai-rmf-ms-2.6",
"function": "MEASURE",
"subcategory": "2.6",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Insert 'The ' at the start of the first sentence. Replace 'MAP function' with 'map function'. Replace 'and can fail safely' with 'and it can fail safely'. Replace 'Safety metrics implicate' with 'Safety metrics reflect'.",
"rationale": "Multiple changes; word choice 'reflect' vs 'implicate' is more substantive but still arguably stylistic — 'reflect' is the clearer reading.",
"core_text": "The AI system is evaluated regularly for safety risks – as identified in the map function. The AI system to be deployed is demonstrated to be safe, its residual negative risk does not exceed the risk tolerance, and it can fail safely, particularly if made to operate beyond its knowledge limits. Safety metrics reflect system reliability and robustness, real-time monitoring, and response times for AI system failures."
},
{
"control_id": "ai-rmf-ms-2.7",
"function": "MEASURE",
"subcategory": "2.7",
"type": "capitalisation",
"severity": 2,
"recommendation": "adopt-core",
"patch": "Replace 'MAP function' with 'map function'.",
"rationale": "Function-name casing. See systemic finding S-1.",
"core_text": "AI system security and resilience – as identified in the map function – are evaluated and documented."
},
{
"control_id": "ai-rmf-ms-2.8",
"function": "MEASURE",
"subcategory": "2.8",
"type": "capitalisation",
"severity": 2,
"recommendation": "adopt-core",
"patch": "Replace 'MAP function' with 'map function'.",
"rationale": "Function-name casing. See systemic finding S-1.",
"core_text": "Risks associated with transparency and accountability – as identified in the map function – are examined and documented."
},
{
"control_id": "ai-rmf-ms-2.9",
"function": "MEASURE",
"subcategory": "2.9",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Remove double space between 'and' and 'AI system output'. Replace 'MAP function' with 'map function'. Remove the word 'and' before 'to inform' (Core reads: 'as identified in the map function – to inform responsible use').",
"rationale": "Whitespace, function-name casing, and a small clause restructure (Core drops the connective 'and', producing a tighter dash-bracketed parenthetical).",
"core_text": "The AI model is explained, validated, and documented, and AI system output is interpreted within its context – as identified in the map function – to inform responsible use and governance."
},
{
"control_id": "ai-rmf-ms-4.2",
"function": "MEASURE",
"subcategory": "4.2",
"type": "wording",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Replace 'across AI lifecycle' with 'across the AI lifecycle'. Replace 'and other relevant AI actors' with 'and relevant AI actors'.",
"rationale": "Article addition and removal of 'other'.",
"core_text": "Measurement results regarding AI system trustworthiness in deployment context(s) and across the AI lifecycle are informed by input from domain experts and relevant AI actors to validate whether the system is performing consistently as intended. Results are documented."
},
{
"control_id": "ai-rmf-ms-4.3",
"function": "MEASURE",
"subcategory": "4.3",
"type": "whitespace",
"severity": 1,
"recommendation": "adopt-core",
"patch": "Insert comma after 'AI actors'. Move comma from 'characteristics, are identified' to before 'are identified' (Core: '...trustworthiness characteristics are identified').",
"rationale": "Comma placement.",
"core_text": "Measurable performance improvements or declines based on consultations with relevant AI actors, including affected communities, and field data about context-relevant risks and trustworthiness characteristics are identified and documented."
}
]
}