command-center/agent/memories/sharpshooter/wt-20261010-164545-6d1fc1f-1mfj0dsoc238q/product.md

Service Naming Convention (ACTIVE)

Three-tier fleet naming — the LLM fleet uses a consistent three-part alias scheme across all user-facing interfaces (models.yml, config.yml, homepage cards, OpenWebUI grants, Hermes routing):

• frank-archon — primary inference endpoint (radiance runtime, frank-primary host)
• frank-dragoon — large model endpoint (halogen-flash-server, frank-large host)
• frank-zealot — secondary model endpoint (llama.cpp, frank-secondary host)

Internal/external bifurcation — infrastructure components (systemd units, compose files, scripts, env files) use the internal names (frank-primary, frank-large, frank-secondary); the wire-facing and operator-facing interfaces use the alias names (frank-archon, frank-dragoon, frank-zealot).

Resolution rules — the default model resolves as a defaultProvider + defaultModel pair (the provider must serve the model); a subagent override uses a bare model id, which resolves only when unique across providers. Two ports on one host need two providers — the file cannot express "same host, different port".

When renaming — update the provider block, model id, contextWindow, maxTokens, input in models.yml, then fix every modelRoles entry that named the old endpoint — a role pointing at a provider the file does not define fails at call time.

Model id alignment — as of 2026-10-09 the StarCraft unit names are the official model ids and also the ids on the wire. Verify a rename on /v1/models, never on a chat response: radiance echoes the requested model name, so a 200 proves nothing about the served id (llama.cpp and halogen ignore it).