Stage 2 · Lesson 6 of 6
Building the inventory into engineering
Engineers can make the inventory stay true instead of going stale. Store inventory entries as structured files ( or JSON) next to the code, or in a catalogue, and check in CI (continuous integration, the automatic checks on every change) that every service calling an AI has one.
Scan repositories for AI SDK imports and API keys to spot new uses. Register models through the training pipeline so a version cannot reach production without its card, evaluation and approval. Tag cloud resources such as model endpoints with an owner and a system ID. The result is an inventory generated from what is actually deployed.
Common trapbuilding a clever scanner and never deciding who reviews what it finds.
A question to check yourself, an AI practice session and 3 cheat sheet entries come with the full roadmap. Unlock
Resources for this stage
Start with· follow one of these
- GuideFreeNIST AI Risk Management Framework (AI RMF)
National Institute of Standards and Technology (NIST) · Intermediate
The Map function is the reasoning behind every inventory entry: context, purpose and who is affected
- GuideFreeEU AI Act: regulatory framework for AI (European Commission)
European Commission · Beginner
Provider, deployer and the risk tiers, the two labels every inventory entry needs