AI Model Registry & Routing (W11-T07)
A new model is never allowlisted at registration; a real DB trigger already rejects routing to any model that isn't allowlisted and ACTIVE.
| Model Key | Provider | Capabilities | Modality | Status | Actions |
|---|---|---|---|---|---|
| No models registered. | |||||
Capability Routing & Fallback Chains
| Capability | Primary Model | Fallbacks | Kill Switch | Actions |
|---|---|---|---|---|
| No capability routing found. | ||||
No DPS-approval sign-off UI for allowlisting exists separately from this single SUPER_ADMIN/CONFIG_ADMIN toggle -- the schema's own comment treats DPS approval as a process note, not a second enforced approver column (unlike pricing's proposer/approver split).