Skip to content
DocumentationArchitectureModel and provider governance
ArchitectureCurrent contractVersion DOCS-2.0

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.

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.