Models, Providers, and Projects
Feeds categories D1 (provider abstraction) and G1 (admin surface).
Starting state from the fast track: providers and models from the onboarding wizard already exist; 9.1 is partially carried over.
Grade each scenario Pass (2 points), Pass with gaps (1), or Fail (0) against the grading rubric, and carry the subtotal into the summary scorecard.
Scoresheet document
For your convenience, this page can be downloaded as PDF or printed directly. Site navigation is omitted, the scoring table keeps its rows intact with the header repeated on every page, and the Grade and Notes columns leave room for handwriting.
| ID | Scenario | Guide | Grade | Notes |
|---|---|---|---|---|
| 9.1 | Add a provider and enable or disable models from the catalog. Verify: an enabled model becomes callable and a disabled one returns a clear error. (Partially carried over from fast-track D0.1; the disabled-model error still needs verification.) | Managing models and providers | ||
| 9.2 | (optional) Provision AWS Bedrock models. Verify: a Bedrock model answers through the gateway. | Provisioning AWS Bedrock models | ||
| 9.3 | (optional) Connect provider subscriptions across clouds. Verify: the same logical model resolves to different provider subscriptions as configured. | Connect provider subscriptions across clouds | ||
| 9.4 | (optional) Provision a custom or self-hosted model behind an OpenAI-compatible endpoint. Verify: the custom model is callable through the gateway. | Provision custom and self-hosted models | ||
| 9.5 | Create a project as the isolation boundary for a team. Verify: the project owns its own models, keys, and members. | Create a project | ||
| 9.6 | Provision a gateway for the project. Verify: the project receives its own inference URL. | Provision a gateway | ||
| 9.7 | Manage project members and roles. Verify: a member sees only their project after the switcher re-scopes. | Manage project members | ||
| 9.8 | Issue a project API key and test isolation. Verify: the key works on its own project's gateway and is rejected (403) on another project's. | Issue a project API key | ||
| 9.9 | (optional, self-hosted) Deploy an additional data plane. Verify: the new data plane registers and can host gateways. | Deploy a data plane | ||
| 9.10 | (optional) Manage gateways on a data plane. Verify: gateway lifecycle actions complete without dropping other projects' traffic. | Manage gateways on a data plane | ||
| 9.11 | (optional) Migrate a gateway between data planes. Verify: the project URL is unchanged and in-flight requests survive. | Migrate a gateway | ||
| Subtotal | /22 |