bytelyst/bytelyst-devops-tools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify remaining Hermes fallback verification

Browse Source
This commit is contained in:
root 2026-05-27 18:46:32 +00:00
parent 8fbb535d90
commit 08f32a79e8
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/hermes-setup-upgrade-roadmap.md
View File

@ -210,20 +210,22 @@ A healthy ByteLyst Hermes setup should be:
- [x] Add at least one fallback provider for resilience: - [x] Add at least one fallback provider for resilience:
- vijay: configured a shared local Ollama fallback chain for both Hermes instances and kept routing disabled on the primary path. - vijay: configured a shared local Ollama fallback chain for both Hermes instances and kept routing disabled on the primary path.
- bheem: same shared local Ollama fallback chain configured for Uma. - bheem: same shared local Ollama fallback chain configured for Uma.
- local/Ollama is now the active fallback path for low-risk offline tasks. - local/Ollama fallback is configured and verified with direct model smoke tests.
- [x] Configure provider credentials through Hermes auth/config flows; do not commit keys. - [x] Configure provider credentials through Hermes auth/config flows; do not commit keys.
- vijay: documented the command path; provider additions requiring new credentials remain pending. - vijay: documented the command path; provider additions requiring new credentials remain pending.
- [x] Define model routing tiers: - [x] Define model routing tiers:
- vijay: fast/cheap = `qwen2.5:0.5b` or `llama3.2:1b`, strong coding = `qwen2.5-coder:7b`, general/long-context = `llama3.1:8b`, vision-capable = `llama3.2-vision`. - vijay: fast/cheap = `qwen2.5:0.5b` or `llama3.2:1b`, strong coding = `qwen2.5-coder:7b`, general/long-context = `llama3.1:8b`, vision-capable = `llama3.2-vision`.
- bheem: same local tier map applies to Uma. - bheem: same local tier map applies to Uma.
- routing remains disabled until a separate routed path is proven safe. - routing remains disabled until a separate routed path is proven safe.
- [x] Test fallback behavior by switching models in a new session. - [ ] Test fallback behavior by switching models in a new Hermes session.
- vijay: verified the fallback chain is configured and the local models can be pulled and invoked on demand; `gemma4` was rejected by the installed Ollama runtime and was replaced with `llama3.2-vision`. - vijay: direct Ollama smoke tests passed for `qwen2.5-coder:7b`, `llama3.1:8b`, and `llama3.2-vision`; live Hermes session-switch verification still needs to be done.
- bheem: verified the same shared host fallback path is available to Uma. - bheem: same live Hermes session-switch verification still needs to be done for Uma.
- [x] Document the preferred default model and fallback order. - [x] Document the preferred default model and fallback order.
- vijay: current default is OpenAI Codex OAuth; fallback provider order is now the shared local Ollama chain. - vijay: current default is OpenAI Codex OAuth; fallback provider order is now the shared local Ollama chain.
- vijay: preferred default is explicitly `gpt-5.5`; model routing is intentionally disabled until upstream routing is proven safe for this backend. - vijay: preferred default is explicitly `gpt-5.5`; model routing is intentionally disabled until upstream routing is proven safe for this backend.
- [ ] Verify the root and Uma Telegram gateways can actually switch to the fallback chain in a live conversation without surfacing provider errors.
### Phase 5 — Tooling Capability Upgrade ### Phase 5 — Tooling Capability Upgrade
- [ ] Enable/configure at least one reliable web search/extract backend: - [ ] Enable/configure at least one reliable web search/extract backend: