@mrciphersmith/keryx 0.3.26 → 0.3.28

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -757,6 +757,24 @@ credential:
757
757
  - `keryx memory reflect --narrate` — a narrative summary of project memory
758
758
  - `keryx health explain <target> --narrate` — a readable explanation of a health result
759
759
  - `keryx wiki enrich` — model-written wiki pages (skips pages without a credential)
760
+ - the model-tier fallback — when discovered model names alone cannot say which model
761
+ is bigger, one short call on the light tier of your own provider orders the
762
+ candidate models (see below)
763
+
764
+ **Model tiers follow the session model and its generation.** `light`, `standard`
765
+ and `deep` are anchored on the model your session runs: `standard` is that model,
766
+ `deep` is the next size step above it, `light` the next size step below it (an Opus
767
+ session with Sonnet and Haiku discovered gets Sonnet for light, Haiku only when
768
+ nothing sits between). Within one family a newer version outranks an older one, and
769
+ an older-generation model that costs more than the session model is never picked as
770
+ `deep`. When the size words and versions cannot settle a tier (the ranking is refused,
771
+ or the only larger candidate is an older generation), keryx asks a small fallback
772
+ agent to order the candidates. It sees only the discovered model ids and the prices
773
+ in your model profiles, never a task, a diff or your text. Its answer is validated
774
+ (ids it was not given are dropped), cached by a hash of the catalogue, and recorded as
775
+ `tier_resolution: agent-ranked`; a failure, timeout or malformed answer keeps the
776
+ session model. `keryx review tier` prints the resolution, and the shell's tier row
777
+ shows tier, source and reason for every dispatch.
760
778
 
761
779
  Semantic embeddings and ML security classifiers are not bundled in the current
762
780
  release. Memory search uses lexical retrieval, and security scanning uses