MP-2.2 Information about the AI system's knowledge limits and how system output may be utilized and overseen by humans is documented
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 inform
4
artefacts
2
held by a system
0
at each review
easy
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Guidance on permitted use and interpretation of system output · Document repository
- The human oversight expected over the output, and by whom · Document repository
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Documented knowledge limits, including the conditions the system was not built for · Document repository
- Evidence this documentation reaches downstream deployers and operators · Document repository
First move
Automate the pull from your Document repository. Version-controlled document with owner, approval and review date as metadata.
Common gaps auditors find
- Limits known to the build team and absent from anything a deployer receives
- Output guidance written for the ideal case, silent on out-of-distribution input
- Documentation exists but is not delivered with the system
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetMP-2.1 The specific task, and methods used to implement the task, that the AI system will support is defined · MP-2.3 Scientific integrity and TEVV considerations are identified and documented, including those related to experimental design, data collection and selection, system trustworthiness, and construct validation