Files
zeekay de557e024b decisions: each Kai version in KAI_URLS is answered by its own deployment
KAI_URLS is comma-separated id=url pairs
(kai-1.4=http://kai-1-4.hanzo.svc:8080). A decision asking for one of
those ids goes to that url, asked there for kai, the one Kai that
deployment runs, and its answer names the id asked. Kai's provider is
reused with only the address moved: the same client and timeouts,
KAI_API_KEY, X-Org-Id, X-Org-Capabilities, capture and billing. kai and
every other id stay on KAI_URL; blank or unset, nothing changes.

- A Kai version is kai-<12 hex>, kai-<major>.<minor> or
  kai-<major>.<minor>.<patch>, each part digits with no leading zero.
  One no route names is priced, gated and filed as kai: the balance
  gate reads a decision's model through DecisionAs, so the plan is
  asked about kai in class ours, not about an id it holds no rule for.
- The decision cache keys on the id the answer names, not the id the
  service is asked for, so a version asked as kai at its own service
  never shares an answer with kai.
- /v1/models lists each pair's id as kai's row under that id: owned by
  hanzo, at kai's price, class and family, slug hanzo/<id>.
- A malformed pair refuses the boot and names it: no '=', an id that is
  no Kai version or is kai, an id named twice, or an address that is not
  http(s) with a host or carries a credential.
2026-10-16 07:13:30 -07:00
..