Practical self-hosting · intermediate
23 · Give each channel a job
Route tasks by required capability and explicit policy.
What you can take away
- Design a model-routing table with bounded escalation.
- Make a table for six synthetic tasks
Your trail through this idea
Checking saved progress…
Ian wanted shared inference across several applications while keeping the experience simple. Routing is where convenience becomes policy: which tasks may use which model, data, tools, and fallback?
Prerequisite: complete the preceding lesson or bring its worksheet.
Understand the system
A channel should describe a job, such as short radio copy, document retrieval, or code review. Define the required capabilities and privacy boundary before selecting a model. The model passport from lesson 20 supplies the tested identity; the contract tests from lesson 22 supply behavioral evidence. A name containing 'reasoning' or 'coder' is not an evaluation result.
Ollama’s running-model endpoint provides a way to inspect loaded model state. That is operational evidence about what is running, not proof that a model is authorized or suitable for a task. Admission and routing belong in your service policy.
Work through the case
Original routing example: routine radio announcements use a small tested model with no external tools. A failed generation falls back to approved prerecorded copy. A private document question stays within a separately authorized retrieval path. Neither task silently escalates to a remote provider merely because the local model is busy.
Make something useful
Try this
Original exercise
Make a table for six synthetic tasks. Columns: channel, required capability, permitted data, model manifest, timeout, fallback, and forbidden escalation. Include one task that must be rejected. Then swap two model labels and check whether the policy still makes sense. If labels alone determine access, the policy needs stronger capability checks.
Check your reasoning
A quick check · for your own learning
What should determine a channel's permissions?
A self-study prompt. You can retry; this is not an exam.
Keep the result and follow the sources
Success is a routing decision another operator can explain without knowing model marketing names. Keep current model choice separate from the enduring channel contract.
Sources and scope
- Primary documentation or archival source, reviewed 14 November 2026. Additional direct links appear beside the claims they support.
- Editorial basis: Ian's historical self-hosting questions and current repository inspection informed the case selection. Historical requests do not establish current deployment. Private chat records, credentials and host details are excluded.
- Examples and exercises are original educational synthesis. External sources support the stated technical or historical context, not every hypothetical scenario.