AAK-ADMT-003: Developer documentation names no known limitations
- Severity
- MEDIUM
- Category
- Legal Compliance (
legal-compliance) - Scanner
agent_audit_kit/scanners/admt_documentation.py- Auto-fixable
- No.
- SARIF name
AdmtNoKnownLimitations
What it detects
Developer documentation exists for a declared covered-domain decision surface but names no known limitations. C.R.S. 6-1-1702(1)(c) requires known limitations including known risks and the circumstances in which the covered technology should not be used. Evidence toward the duty, not a determination that it applies.
How to fix
Add a known-limitations section covering the risks and, specifically, the circumstances in which the system should not be used. C.R.S. 6-1-1702(1)(c) names the non-use circumstances explicitly, so a list of accuracy caveats alone does not answer it.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-ADMT-003
Limitations
Passes as soon as the documentation contains limitation, limitations, known risk, should not be used, out-of-scope or failure mode, wherever it occurs: a license footer ending permissions and limitations under the License satisfies it.
References
No external references are recorded for this rule.
All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-ADMT-003.md: the page then shows that text, with the registry reference appended under it.