Aims Audit
Aims Audit: Review an AI management system against its stated controls. Review the AI system inventory, policies, owners, risk records, and evidence and produce an AI management audit matrix.
--- name: compliance-os-aims-audit description: Use for aims audit when asked to review an AI management system against its stated controls; produce an AI management audit matrix. license: MIT metadata: author: Thrive category: compliance-os --- # Aims Audit ## When to use Use this skill for aims audit when you need to review an AI management system against its stated controls. The expected result is an AI management audit matrix. ## Boundaries Work within the requested task and its stated acceptance criteria. Drafting an artifact does not authorize publishing it, spending funds, changing a live system, or contacting another person. Identify any such action separately before taking it. ## Inputs Inspect the AI system inventory, policies, owners, risk records, and evidence. Resolve missing information that would change the method; state lesser assumptions in the result. ## Method 1. **Diagnose.** Identify the current framework version, scoped systems, data flows, control owners, and existing evidence. 2. **Decide.** Map management requirements to operating evidence and open gaps. 3. **Produce.** Build an AI management audit matrix from the inspected material; keep assumptions distinguishable from observed facts. ## Decision rules - Separate policy language from operational control performance. Prioritize gaps with no owner or no evidence. - When sources or constraints conflict, record the conflict and choose the path supported by the user's goal and the strongest available evidence. If neither path can be supported, identify the missing decision before changing the artifact. ## Domain rules - Map each requirement to a control, owner, evidence item, and gap. - Check the current authoritative requirement and reserve final interpretation for qualified review. ## Verification Check current ISO 42001 text and distinguish missing evidence from missing control. Compare the result with the user's acceptance criteria and record any unverified boundary. Return a control matrix with exact evidence request, affected scope, remediation owner, and review date. ## Evidence and stop conditions - Verify current authoritative sources for rules, prices, clinical claims, or obligations that can change. Distinguish fact, interpretation, and assumption. - Stop before an external action or regulated judgment without the required authorization or qualified reviewer. - When evidence is materially missing or conflicting, state the uncertainty and the exact source or decision needed to proceed. ## Stop conditions If a material input, required authorization, or a safe way to verify the result is absent, stop the affected action. Return the specific blocker and the smallest fact or decision needed to continue. Do not report an unrun check as passed. ## Output Provide an AI management audit matrix. Include the decisive evidence and actual verification result. Name any artifact location and unresolved issue that affects its use. <!-- MIT License Copyright (c) 2026 Thrive Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. -->