AI routing policies
Which provider and model each capability is routed to, and how a routing change is released.
Note: This screen has no data behind it in this build
The address is specified and the console is ready for it. What is missing is the server side: the reads below are declared by the contract and are not registered in this deployment, so they answer “not implemented” rather than returning anything. Nothing on this page is a placeholder for data — there is no data to place.
What this screen is for
The routing policy per capability — primary provider, fallbacks, the conditions that move traffic between them — as a versioned record with validate, publish and roll back, so a routing change is auditable and reversible rather than a configuration edit.
What has to exist first
- Reads
- staffAiRoutingPoliciesList
- Actions
- staffAiRoutingPolicyCreate
- staffAiRoutingPolicyValidate
- staffAiRoutingPolicyPublish
- staffAiRoutingPolicyRollback
Each of those is an operation id in the frozen contract. Registering one is a server change, not a permission you can be granted — no group and no scope makes this screen return data today.