Model governance
Model availability rules restrict which models can be selected for Tasks and agents. Rules can apply to one project or to every project in an organization.
Rule scopes
An organization rule is inherited by every project in that organization. A project cannot override it.
A project rule applies only to that project. The effective policy is the union of its project rules and inherited organization rules.
Use organization rules for controls that must be consistent across teams. Use project rules for workload-specific restrictions.
Selectors
Rules support three selectors:
Provider and vendor rules also apply to models added later that match the selector. Each rule can carry an audit reason.
Rightbrain rejects a rule that would leave an affected project without at least one active model.
Organization endpoints
Organization rule operations require organization edit access. The list response is a plain array.
Project endpoints
Project rule operations require project edit access. Project-owned rule lists are plain arrays.
The effective response separates organization_rules from project_rules and reports excluded and available counts across active models.
Model IDs
Model-specific rules use the UUID returned by GET .../model. Task and agent configuration also uses a model UUID in llm_model_id; a display name is not a substitute for this identifier.