Why it matters
Foundation-model dependencies concentrate risk, complicate assurance, and create information asymmetry between model developers and downstream deployers.
What this looks like in practice
- 01Record model version, provider, terms, evaluations, limitations, and downstream dependencies.
- 02Evaluate the complete system in its use context rather than relying only on upstream benchmarks.
- 03Plan for model updates, withdrawal, access changes, and inherited incidents.