ODS architecture — from click to model
In the minimum pilot, the web UI receives the request, Docker services route it, and the native macOS llama-server performs inference. Extensions add capabilities and also processes, data, and ports.
Complete Simple + Technical
In the minimum pilot, the web UI receives the request, Docker services route it, and the native macOS llama-server performs inference. Extensions add capabilities and also processes, data, and ports.
Bounded analogy: The UI is the counter, LiteLLM is routing control, and llama-server is the runway. Unlike an airport, each service can fail and retain state independently.
Under the hood
On macOS, documentation describes host Metal and containers reaching host.docker.internal:8080. Compose combines base, Apple overlay, and extensions. Local, cloud, and hybrid modes change routing and egress.
Boundary: installation, runtime, and Docker/Compose were not executed.
14 semantic microdiagrams
Each figure teaches one relationship; the sequence is a decision map, not a health dashboard.
Command and proof boundary
rg -n 'host.docker.internal|8080|local|hybrid' work/ods-latest/ARCHITECTURE.md
Allows claiming
| check | reading |
|---|---|
| local | exercised contract |
| upstream | declared capability |
Remains open
| runtime | gate |
|---|---|
| health/chat/UI | live pilot |
| lifecycle | backup/restore/uninstall |
Local sources
outputs/ods-adoption-dossier.md:39-60work/ods-latest/ARCHITECTURE.md:114-151work/ods-latest/ods/docs/MACOS-QUICKSTART.md:49-71outputs/ods-check-receipt.md:131-182
Includes dossier, receipt, and official source by path:line.
Practice with feedback
1 · Prediction
2 · Stepper
1. classify the need
2. locate the proof
3. decide without overclaiming
3 · Scenarios
4 · Checklist
6 · Quiz
Which route preserves the minimum pilot?