Repository navigation
docs: document routing table, cost cap, and provider fallback - #45
Merged
Merged
Conversation
Captures the user-facing surface of #4 (PR #40) that landed in the code without a README update. - New "Routing, Cost Caps, and Fallbacks" section: explains ROUTES_JSON shape, per-key max_cost_usd enforcement, single-hop fallback on retryable failures, and streaming fallback's pre-first-frame boundary. - Configuration table gains ROUTES_JSON. - Repository structure updated: providers/anthropic.py (stub), mojo_bridge/{stream,db,ratelimit,routing}.py, tests/test_cost_cap.py, tests/test_provider_fallback.py. - Roadmap corrected to match reality: Anthropic stub in-tree but not a real adapter; Postgres-backed virtual keys, Prometheus metrics, Redis rate limiting, in-binary TLS, and calver release-please are all shipped (was marked [ ]). - Philosophy test count bumped 23 → 56. Co-authored-by: Claude <noreply@anthropic.com>
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.
Summary
README update that captures the user-facing surface of #4 (PR #40) which shipped in the code without a README counterpart.
Changes
Why
The behaviour shipped in #40 (cost caps, fallback, routing table) but the README still described a pre-#4 gateway. New operators reading the README would not learn the routing controls exist. This brings the docs back in sync with the code.
Testing
Docs-only change, safe to merge once CI is green.