Lab 02: compare routing decisions
Prerequisites: Lab 01, both configured models downloaded, and routing enabled. Artifact: a three-row routing comparison.
Exercise
Section titled “Exercise”- Follow Choose the answering model to preview a coding request.
- Preview a general explanation request by changing the URL-encoded
queryparameter. - Send both requests to
/api/v1/querywithout a model override. - Send the coding request with an explicit
qwen2.5-coder:3boverride. - Record preview model, actual model, reasoning, and whether the selected model was available.
| Request | Preview | Actual model | Explanation |
|---|---|---|---|
| Coding, automatic | Fill from response | Fill from response | Record evidence |
| Explanation, automatic | Fill from response | Fill from response | Record evidence |
| Coding, explicit model | Not applicable | Fill from response | Check availability |
Acceptance criteria
Section titled “Acceptance criteria”You can distinguish rule scoring from runtime availability checks. You inspect the actual response rather than assuming that explicit selection always succeeds. A routing difference is an observation to investigate, not an automatic test pass.
If results differ
Section titled “If results differ”Refresh the registry after pulling models. If routing is disabled, restart the backend with the intended setting. The preview and actual route use different inputs, so document differences before diagnosing a regression.
Next: Lab 03: retrieval.