Model and provider governance
How models are enabled, associated with capabilities, used in methodologies and treated as mutable dependencies of the experiment.
How to interpret this document
This content describes technical and methodological behavior that is implemented or explicitly planned in the product. When a control depends on configuration, a provider, a secret, a contract or legal approval, that dependency must remain visible.
Model catalog
ModelConfig records which models are enabled and which capabilities or methodologies they support. A model being available from a provider does not automatically make it eligible for every measurement.
Version change
Providers can change behavior, availability and models without preserving the same response distribution. Model-set composition therefore belongs to the comparable-series signature.
Grounded search
Methodologies that rely on web evidence require compatible grounded/search capabilities. The application should reject combinations that cannot satisfy the methodology contract.
Data sent
Execution sends the controlled prompt and strictly necessary context to the provider. Each provider's privacy, retention and training terms should be contractually assessed during Enterprise deployment.
Failures
Timeouts, rate limits, outages and provider rejections remain visible in jobs and completeness. The platform should not silently substitute one model for another inside a comparable series.