Files
agent-estate-wiki/experiments/index.md
T
Hermes 341dda95dd stocktake 2026-11-11: 36 stale pages re-verified (0 stale); fallback chain rewritten 4/6 slots; CT333 'clawtest' naming claim corrected; nous 404 credits signature replaces refresh-token 401; estate shrank (VM 310 + CT601 gone)
- freshness: 36 stale / 93 fresh / 3 no-date -> 0 stale / 129 fresh / 3 no-date of 132 (same-day report regenerated after the corrections, per pattern 13)
- skills: 299 skills / 67 categories (count unchanged; generator arithmetic re-verified by hand against the live tree: 300 SKILL.md files - 1 nested duplicate = 299)
- runbooks/test-openrouter: live fallback chain rewritten (primary back to smart-route/custom:omni-101; mimo-v2.5, stepfun, qwen3.5/ollama-cloud out; guacano + kilo-reflection-beam-free in); ollama.com dropped from the URL test list; guacano/litellm noted as internal + key-gated
- comparisons/hermes-vs-nanobot: the 2026-10-20 'CT333 is zeroclaw in Proxmox naming' claim was itself wrong - pct list and hostname both return clawtest
- incidents/2026-10-22-nous: refresh-token failure gone from logs; new signature 404 insufficient_credits_for_paid_model from auxiliary.pulse_memory (ninth slot, back on nous, paid model) - open item revised
- incidents/2026-08-29-gmail: email crons now ok but root cause unfixed 74 days (himalaya message read still in fetch_newsletters.py; goimapnotify back up PID 441; monitor still paused)
- 30 further pages re-verified live and de-flagged with dated probe notes (ct207 ingress, CT205 guanaco v0.8.15, CT270 nextcloud 33.0.2.2, headless stack, hermes-ui both hosts, systemd units + cgroup limits, terminal/tool_search/mnemosyne/custom_providers config blocks, ops profile still deleted, hosts/pve guest lists)
- log.md addendum + index.md date bump; no page deleted, no secrets written
2026-11-11 03:52:48 +08:00

62 lines
2.8 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
title: Experiments
type: collection
status: active
created: 2026-07-22
updated: 2026-11-11
verified_on: 2026-11-11
confidence: medium
tags: [experiments]
---
# Experiments
Non-canonical tests, tuning passes, and change attempts.
## Known experiments
- `pre-vision-fix-20260718-195712` config snapshot — **no longer found by that name**
- `pre-model-fix` config snapshot — **no longer found by that name**
- `pre-camofox-tuning` config snapshot — **no longer found by that name**
> **Re-verified 2026-10-20 — the three named snapshots this page listed are GONE.**
> `find ~/.hermes/backups -name "*pre-*"` returns only:
> - `config.yaml.pre-cua-durable-20260730` (the one that `pre-camofox-tuning` appears to have
> been renamed to — it is dated 2026-07-30, matching the CUA durable-persistence change)
> - `incident-20260727-mattermost-removal/config.yaml.pre-mattermost-off`
>
> The other two (`pre-vision-fix-20260718-195712`, `pre-model-fix`) have **no surviving file under
> that name** in `~/.hermes/backups/`. The backups directory now holds 15 entries including
> `config/` (a rolling series of `config.yaml.bak.*`, `.corrupt.*`, `.good.*` and
> `config.yaml.premnemo.20260928-174645`) plus nine dated incident directories:
> `dashboard-regression-20260811`, `incident-20260727-mattermost-removal`,
> `legacy-memory-slim-20260801_180702`, `mnemosyne-capture-fix-20260801_180249`,
> `phantom-default-profile-20260730-1250`, `resource-hardening-20260725`,
> `session-repair-20260815-205936`.
>
> The `config/` series is worth knowing about operationally: it includes **four `config.yaml.corrupt.*`
> files** (2026-09-28 ×2, 2026-09-30, 2026-10-01) — evidence of the `hermes config set` stringifying
> lists/dicts problem — alongside `config.yaml.good.*` snapshots from 2026-10-09, 10-11 and 10-16.
> See [[incidents/2026-09-28-hermes-managed-runtime-deps]] and the runtime-deps notes in
> [[systems/hermes-agent]].
> **Backups tree re-listed 2026-11-11 — no change to report.** `~/.hermes/backups/` still holds the
> same dated incident directories named on 2026-10-20 (including
> `mnemosyne-capture-fix-20260801_180249/` and `legacy-memory-slim-20260801_180702/`, both verified
> present again during this pass), plus the rolling `config/` series. The three experiment
> snapshots this page originally listed (`pre-vision-fix-20260718-195712`, `pre-model-fix`,
> `pre-camofox-tuning`) are still gone.
## Outcomes
- **Verified:** Backups exist with the above names
- **Unknown:** Whether each experiment succeeded, failed, or was reverted
- **Excluded:** No secrets, tokens, or full config dumps are stored here
## History
- **Verified:** Three named pre-change backups present as of 2026-07-22
- **Inferred:** Backups were taken before optional config changes and left intact
## Related
- [[runbooks/update-hermes-safely]]
- [[current-state]]