docs: gateway routing and fallback boundaries (issues #82, #84) - #89
Open
SebConejo wants to merge 4 commits into
Open
docs: gateway routing and fallback boundaries (issues #82, #84)#89SebConejo wants to merge 4 commits into
SebConejo wants to merge 4 commits into
Conversation
…ck boundary, upstream-429 cooldown (issue #82)
…ith no header and no provider error (issue #84)
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
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.
Processes finding 1 of #82 and, reduced to its two useful facts, finding 1 of #84. Findings 2 and 4 of #82 were rejected on review.
Issue #82, finding 1 (option 1) — the page promised twice that naming a model skips routing, while the Custom tiers section states the header wins. Both promises now carry the exception: the Routing step gets one sentence, and Route a specific model states that a matching custom tier header runs the request on the tier's model and the tier's fallbacks.
Issue #84, finding 1 (trimmed) — one sentence under the status table: a tier also falls back when its pinned model leaves your model list, and a tier with no fallback left returns M101.
The 429-pause and streaming-boundary paragraphs were dropped on review: no fact the reader acts on.
Coherence GREEN.
Closes #82
Closes #84