Repository navigation
docs: correct shared catalog behavior after review fixes - #183
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The shared-catalog README still says rolling aliases may select newer models, contradicting the final behavior merged in #181 and shipped in v3.47.0. Document that existing Franklin aliases keep their targets, remote policy can add aliases, and live price estimates can still change for the same model.
Also describe the curated picker with +more, parallel policy/gateway refresh, independent gateway refresh during a policy-host outage, offline fallback, and background CLI startup. This changes documentation only.
Validation:
git diff --checkpassed. Reverified current Franklin (npm test: 766 passed) and its pinned Model Core revision (npm run check: 21 passed). Injected policy-host failures against real Base and Solana model-list endpoints: both cold-start and warm-cache cases retained live gateway rows. No paid inference calls were made.