Compatibility policies

Turn product requirements into explicit constraints before comparing price or selecting a deployment.

Write a policy

Start with requirements that would break your workflow if absent. Keep preferences such as provider or price separate so they can rank compatible candidates instead of incorrectly excluding them.

{
  "name": "support-agent-production",
  "requires": {
    "tool_calling": "supported",
    "structured_output": "supported",
    "streaming": "supported"
  },
  "constraints": {
    "regions": ["eu", "global"],
    "minimum_context_tokens": 128000,
    "deployment_status": ["available"]
  },
  "on_unknown": "reject"
}

Evaluation

1. Resolve each deployment against the pinned catalog release.
2. Evaluate hard capability and region constraints.
3. Reject unknown or stale evidence according to policy.
4. Calculate price only for remaining candidates.
5. Persist the decision and its release ID.

Conditional support

Request conditional only if your application knows how to satisfy and validate the returned conditions. A requirement of supported excludes conditional assertions.

Rollout pattern