# AI System Inventory / Application Register
Executive Summary
This inventory makes AI ownership visible. It lists AI-enabled systems, owners, model routes, data classes, retrieval sources, tools, approvals, logging, risk tiers, and evidence state.
The result is not a spreadsheet for its own sake. It is the foundation for governance, launch readiness, enterprise review, and product security decisions.
Public sample notice
Inventory decision
Use the inventory as the starting point for AI security governance. Any AI system without an owner, risk tier, model route, evidence state, and change-review path should be treated as incomplete.
Inventory Snapshot
You cannot govern what you cannot name
Inventory register
AI System Inventory
The inventory captures AI-enabled systems, risk tier, deployment state, owners, model routes, retrieval, tool access, approvals, trace logging, and evidence state.
Portfolio overview
AI portfolio overview
| System | Status | Risk tier | RAG | Tools | Evidence state |
|---|---|---|---|---|---|
| Northstar Support Cloud / Customer Support Copilot | production pilot | Tier 4 | yes | yes | partial |
| Sales Email Assistant | design | Tier 2 | no | yes | draft |
| Internal Policy Summarizer | production | Tier 1 | yes | no | implemented |
Required inventory fields
Required inventory fields
| Field | Required | Why it matters |
|---|---|---|
| System owner | yes | unowned AI systems create remediation and buyer-response gaps |
| Risk tier | yes | controls should map to actual behavior and blast radius |
| Model route | yes | provider, retention, training-use, and data routing claims depend on route |
| Retrieval sources | conditional | RAG creates authorization, source trust, chunking, and prompt-assembly risk |
| Tool access | conditional | tools convert generation risk into authority and operational blast radius |
| Trace logging | yes | auditability and incident response depend on traces |
Portfolio findings
Portfolio Findings
Critical AI systems still have partial evidence
The Northstar Support Cloud / Customer Support Copilot is a Tier 4 system with retrieval and tools, but its evidence state is still partial. That should drive assessment and remediation priority.
Tool-enabled systems need a tool BOM
The inventory shows multiple systems with tool access. These systems need a tool inventory, action classes, approval requirements, and audit requirements.
Provider boundary claims need route-specific evidence
Customer-facing provider claims depend on the exact model route, provider terms, retention behavior, and data minimization controls.
Inventory operating rules
Inventory operating rules
Portfolio review decision
Use the inventory to decide assessment sequence. Start with Tier 4 systems that combine RAG, tools, customer impact, and partial evidence.
Recommended next artifacts
Related artifact: AI Security Operating Model Blueprint
The operating model defines how this inventory becomes a repeatable governance workflow.
Related artifact: Agent Tool Inventory
The tool inventory expands the tool-enabled rows into tool-specific owners, action classes, approvals, and audit requirements.
Related artifact: Enterprise AI Security Evidence Pack
The evidence pack turns inventory facts into buyer-ready proof.