Skip to content

docs: gateway routing and fallback boundaries (issues #82, #84) - #89

Open
SebConejo wants to merge 4 commits into
mainfrom
fix/issue-82-gateway
Open

docs: gateway routing and fallback boundaries (issues #82, #84)#89
SebConejo wants to merge 4 commits into
mainfrom
fix/issue-82-gateway

Conversation

@SebConejo

@SebConejo SebConejo commented Aug 20, 2026

Copy link
Copy Markdown
Member

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

@SebConejo SebConejo changed the title docs: gateway routing and fallback boundaries (issue #82) docs: gateway routing and fallback boundaries (issues #82, #84) Aug 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docs audit — 2026-08-19 (PRs #2734–#2738) Docs audit — llm gateway (routing, tiers, fallbacks) — 2026-08-19

1 participant