The script
The script of this episode as of 9 November 2026, ahead of the video. The wording may change slightly when it is recorded. Numbers are written as digits. Sources are listed below the script.
0:00AI-BOM: what sits inside?
Welcome! Which models are inside your product? Prove it. AI Governance Chain has an AI-BOM generator that turns declared models and dependencies into a machine-readable inventory.
0:22The buyer's model inventory
Picture an enterprise buyer sending a supplier questionnaire on Friday. One question asks for every AI model and dataset in your product. The product team opens a spreadsheet. One model entry is old, and nobody knows what else changed. The buyer needs a list they can review, not a guess assembled at the last minute.
0:45What an AI-BOM records
An AI-BOM is a machine-readable inventory of the models, datasets and dependencies inside an AI system. In plain words, it is a structured parts list for the AI in a product. The generator reads declared models from AI_GOVERNANCE.md and the project dependencies. On the chain, this connects CONTROL to EVIDENCE: what the team declares becomes a record others can inspect. It extends a software bill of materials to AI.
1:13Create a CycloneDX or SPDX file
Step 1: open the models section of AI_GOVERNANCE.md and declare the system models. Step 2: include the project dependencies. Step 3: run aigovchain aibom to create the inventory. Since v0.2, released on 9 November 2026, the generator writes 2 formats: CycloneDX 1.6 and SPDX 3.0.1 with its AI and Dataset profiles. CycloneDX's machine-learning BOM support arrived in version 1.5 in June 2023. Ecma International publishes CycloneDX as the standard ECMA-424. SPDX 3.0, released in April 2024, includes AI and Dataset profiles.
1:49Who uses the AI-BOM?
Procurement teams can send the inventory with a supplier response. Developers can compare declared models with project dependencies. Risk teams can review the components recorded for a use case. Product owners can make the model list visible during a change review.
2:06Limits of a model inventory
The generator lists declared components. It cannot prove a model was actually used or that a dataset is authorised. Missing entries stay missing, and old entries can become stale. This is an inventory, not an audit, and it is governance guidance, not legal advice in any jurisdiction. Keep the models section current and check the source files. A machine-readable file can sit beside the product records used in a supplier review.
2:33Generate your AI-BOM
Your one action: generate an AI-BOM from your models section with aigovchain aibom, linked below.
You can list what's inside. Can you prove nobody edited the evidence afterwards?
Thank you for watching!
