I do not mind a product assistant being wrong because the docs are unclear. I do mind it being wrong because it silently used the wrong model source. That was the real problem I hit in my local AI gateway project, CliGate . The assistant inside the dashboard had a clear job: answer product-usage questions stay grounded in the manual avoid rewriting settings unless the user explicitly asks But the runtime path behind that assistant was still too fuzzy. In practice, it could depend on whichever account or API key the broader system happened to resolve first. That is fine for generic chat. It is not fine for a product assistant that is supposed to be predictable. The failure mode was subtle I already had routing. I already had accounts, API keys, and model mapping. I already had a settings surface.…