# AI system record

NoArt Systems · instrument A8 · https://noart.io/instruments/ai-system-record/ · CC BY 4.0

One record per system, kept in the system's repository and revised with it. Every claim points at an artifact; a claim with nothing behind it goes in field 12 as an open question. The owner in field 11 has read and signed it.

System: · Version: · Record date: · Owner:

| # | Field | Entry |
|---|---|---|
| 01 | Purpose and boundary | What decision or task it supports, for whom, and what it is explicitly not for. |
| 02 | Where it sits | Systems it reads from, systems it writes to, the human step before any consequence. Diagram with write paths marked; system of record named. |
| 03 | Permissions | What it may read, write, send, and never do. For an agent: the tools it holds and the approval each needs. |
| 04 | Data | Run-time data and, if applicable, training or tuning data: sources, where each lives, who can see it, retention, personal data and lawful basis. |
| 05 | Models and components | Models or services depended on: vendor, version, region, fallback behaviour, date last reviewed. |
| 06 | Evaluation | Test against the real task: evaluation set origin and size, metrics, last result, release-stopping threshold, re-run cadence. |
| 07 | Guardrails | Validators, caps, filters, refusals; each with the test that pins it. |
| 08 | Human oversight | Who reviews output, before or after effect, with what capacity; what they can override; what happens when output outruns them. |
| 09 | Traceability and logging | What is recorded per action, retention, who can read it, the query that answers "why did it do that". |
| 10 | Known limits and failure modes | Where it is weak, what it does when uncertain, incidents so far. |
| 11 | Ownership and change | Owner, who may change it, review path, trigger for revising this record. |
| 12 | Open questions | What could not be answered, who is finding out, by when. |

Reading order for a reviewer: 01, 03, 08 first; then 06 against 07; then the rest.