wiki: publish pending edits (2026-10-20)
This commit is contained in:
@@ -3,8 +3,9 @@ title: Keep OpenRouter as fallback
|
||||
type: decision
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-07-22
|
||||
review_after: 2026-08-22 # was 0001-01-01 (bug), fixed during 2026-07-22 audit; real trigger is conditional, see Revisit when
|
||||
updated: 2026-10-20
|
||||
review_after: 2026-10-20 # was 0001-01-01 (bug), fixed during 2026-07-22 audit; real trigger is conditional, see Revisit when
|
||||
verified_on: 2026-10-20
|
||||
confidence: high
|
||||
tags: [routing, provider, decision]
|
||||
sources: []
|
||||
@@ -28,6 +29,27 @@ OpenRouter must remain available as a fallback provider, even if a self-hosted r
|
||||
## Revisit when
|
||||
A self-hosted router has operated reliably for at least 30 days.
|
||||
|
||||
> **Revisit trigger MET (verified 2026-10-20).** OmniRoute has been the primary router for well over
|
||||
> 30 days — `custom:omni-101` is the pin on effectively every model-calling cron job, and
|
||||
> `Omniroute:20128` is a second live OmniRoute endpoint. The estate has **no standalone OpenRouter
|
||||
> provider**: `custom_providers` in `~/.hermes/config.yaml` holds only `litellm`, `guacano`,
|
||||
> `Omniroute:20128`, `command-code` and `omni-101` (see [[systems/openrouter]]).
|
||||
>
|
||||
> **But the fallback is now provided *through* OmniRoute rather than alongside it** — OpenRouter-style
|
||||
> slugs (`openrouter/auto`, `freeapi/openrouterfree`, `or-openrouter-fusion`, …) are present in the
|
||||
> OmniRoute catalog, so OpenRouter capacity remains reachable without a separate Hermes provider.
|
||||
>
|
||||
> **Status: decision still `active`, but the mechanism it protects has changed.** The intent
|
||||
> (OpenRouter capacity must remain reachable as a fallback) is satisfied via the OmniRoute catalog.
|
||||
> The literal reading — a standalone OpenRouter provider in `custom_providers` — is **not** satisfied
|
||||
> and has not been since at least 2026-07-22. This needs a re-affirmation or a rewrite of the
|
||||
> decision text; it should not simply be left to drift on a 30-day timer.
|
||||
>
|
||||
> Related context: OmniRoute has also been the source of repeated fleet-wide failures —
|
||||
> the 2026-10-14 connection-refused storm, the 2026-10-16/17 and 2026-10-19 resource-pressure 503
|
||||
> bursts, and the 2026-10-18 degenerate-stream delivery. A single-node fallback posture carries
|
||||
> that concentration risk with it.
|
||||
|
||||
## Related
|
||||
- [[model-routing]]
|
||||
- [[systems/omniroute]]
|
||||
|
||||
Reference in New Issue
Block a user