Model policy is the administrator view of models available through Tindre. It controls organizational availability; builders choose among the permitted models from the Agent editor.
Platform catalog
Models Tindre can serve.
Organization policy
Allowed, restricted, or exception-controlled choices.
Agent selection
A builder chooses a permitted model.
Lifecycle
Deprecation and replacement require attention.
Allow by capability and risk
Consider data handling, provider, cost tier, latency, and required capabilities. A model being technically present does not mean it is appropriate for every organization.
Keep selection with the builder
Administration sets the boundary. The Agent editor selects the model that fits the job within that boundary. A policy cap restricts and never widens, and it applies to an administrator's own choices too.
Respond to lifecycle signals
When a selected model is deprecated or approaches sunset, identify affected Agents and choose a supported replacement. Test critical behavior because a successor can differ in latency, reasoning, and tool use.
Use exceptions explicitly
If the organization permits exceptions, make them reviewable and tied to a clear decision.