ModulesSAI-200
SAI-200 table of contents
Internal Artifact Supply Chains and Offline Builds
Control the import, verification, approval, storage, promotion, and offline build of AI software and model artifacts.
Learning outcomes
What you should be able to do
- Design an approved import workflow
- Use checksums, signing, SBOMs, registries, and wheelhouses
- Plan repeatable disconnected builds and updates
Curriculum
Work through 5 sections in order.
The chapters are individually addressable documentation pages. You can link directly to a concept from another program, architecture decision, or implementation guide.
Supply-chain foundations
Understand controlled artifact lifecycles and the assets and boundaries they cross.
Introduction to internal artifact supply chains
Treat every imported package, container, model, dataset, and configuration as a controlled lifecycle object.
AI assets and attack surfaces
Inventory the data, models, prompts, artifacts, identities, tools, interfaces, infrastructure, and evidence that require protection.
Trust boundaries and data flows
Map where trust changes and where data, artifacts, requests, identities, tools, and evidence cross a boundary.
Import, identity, and trust
Establish verifiable identity and an approved route into authoritative internal sources.
Artifact identity and provenance
Identify software, models, data, prompts, policy, and configuration with verifiable origin and lineage.
Import, approval, and promotion
Design quarantine, verification, review, approval, transfer, and promotion stages with separation of duties.
Internal repositories and model stores
Define authoritative internal sources for containers, packages, models, metadata, and dependency resolution.
Disconnected lifecycle
Build, update, roll back, and recover without uncontrolled external dependencies.
Offline build, update, and recovery
Make disconnected builds repeatable and design controlled updates, rollback, rebuild, backup, and recovery.
Controlled change and versioning
Version complete AI behavior, assess change impact, approve promotion, support rollback, and retire superseded assets.
Architecture decision records
Record context, options, control consequences, evidence, dependencies, limitations, and reversal triggers for material decisions.
Controls and assurance
Define control objectives and collect evidence at each promotion boundary.
Write effective control objectives
Translate sovereignty goals into testable statements of what must be allowed, prevented, approved, observed, retained, and recovered.
Evidence by design
Design evidence alongside controls so important decisions, releases, configurations, and operating events can be verified.
Apply and assess
Produce a supply-chain design and validate its completeness.
Practical completion package
- Artifact and dependency inventory
- Import-zone and promotion design
- Provenance and approval record
- Internal repository architecture
- Offline build, update, rollback, and recovery runbook
Current release boundary
This public curriculum is vendor-neutral and does not authorize imports into a production environment. Product-specific commands, supported versions, signing systems, malware scanners, and transfer mechanisms must be declared and tested in separately versioned adapters.