Skip to content

AAK-ADMT-001: No developer documentation for a declared covered-domain decision surface

Severity
MEDIUM
Category
Legal Compliance (legal-compliance)
Scanner
agent_audit_kit/scanners/admt_documentation.py
Auto-fixable
No.
SARIF name
AdmtNoDeveloperDocumentation

What it detects

The project declares a tool, MCP server or docstring that both performs an inference and names a Colorado SB 26-189 covered domain (education, employment, residential real estate, financial or lending services, insurance, health care, or essential government services and public benefits), and the repository carries no developer documentation at all: no model card, no system card, and no page naming intended uses. Where the technology is one C.R.S. 6-1-1702 covers, subsection (1) requires that documentation to be available to each deployer from 2027-01-01. This is evidence toward that duty, not a determination that the duty applies.

How to fix

Add a model or system card naming the intended uses and known harmful or inappropriate uses (C.R.S. 6-1-1702(1)(a)), the categories of training data (1)(b), known limitations (1)(c), and instructions for appropriate use, monitoring and meaningful human review (1)(d). Retain it: 6-1-1702(4) requires records demonstrating compliance to be kept for not less than three years, including system version identifiers and changelogs.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-ADMT-001

Limitations

A covered-domain decision is declared only by the name and docstring of a Python function whose decorator name contains the word tool, or by the names and descriptions in an MCP config. An HTTP route (@app.post("/score")) or a TypeScript server.tool(...) that scores loan applicants declares nothing, and no ADMT rule reports for 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-001.md: the page then shows that text, with the registry reference appended under it.