Why it matters
The classification triggers provider duties around technical documentation, downstream information, copyright policy, and training-content summaries, with additional obligations for models with systemic risk.
What this looks like in practice
- 01Separate model-level obligations from system-level obligations.
- 02Assess generality, task range, integration patterns, and market placement.
- 03Maintain a dependency map linking the model to downstream systems and their owners.