In our method, an AI inventory holds fourteen kinds of record. That is our working model, not a standard. Most organisations already track a few of them somewhere. Few link them.
1. Use case or business process. The business activity the AI supports, tied to your process list or BIA. It carries how critical the process is, and what happens if the AI is wrong or unavailable.
2. AI system or application. The deployed thing that contains or calls AI: your own application, a SaaS product, or a feature inside a platform.
3. Model. A specific model, at a specific version, in a specific deployment. The version matters: providers retire models and can update the model behind an alias without notice; a pinned version does not change. If you keep a model inventory for credit or risk models, this row belongs there; check that it reaches generative and vendor models.
4. Endpoint. The network address through which the model or AI service is called: what a firewall rule allows and a log records.
5. Credential. The API key, service account or token used to reach the AI service. The inventory records its name, store, owner and scope. The key itself stays in the secrets store; the service account belongs in the access review.
6. Agent. Software that plans and then acts by calling tools. Its risk is set by what it is allowed to do, not by which model it uses.
7. Agent tool grant. One tool an agent may call, with what it is allowed to do. Read-only document search and the power to create payment orders are separate rows, because their risk is very different.
8. Data flow. A category of data moving between two records, such as customer data from the CRM to a model endpoint. It links the inventory to the record of processing activities, and to the data processing agreement that says where the data is processed and whether the provider may train on it.
9. Retrieval source. An index or document collection the AI reads to ground its answers. When it goes stale, answers get worse without any error.
10. Platform or hosting location. The cloud account, tenancy, region or on-premise cluster where something runs, and where data location and all-region outage questions are answered.
11. Vendor and contract. The supplier as a legal entity, with the contract that governs it: data use, data location, change notice, exit. One vendor often sits behind several systems, some only through another vendor.
12. Dependency link. A directed link between any two records: this process uses this system, this system calls this model, this model runs in this region. Without links, the other thirteen are just lists.
13. Owner. A named role holder for each record. An unowned row is a row nobody will update, review or switch off.
14. Evidence. One observation, from one source, that supports a record. It shows an auditor, and you, why the row can be trusted.
For what an AI platform should record about its own decisions, see You Say Your AI Is Governed. Six Months Later, Can You Show It?.