Files
agent-estate-wiki/index.md
T
Tony0410 deb6a8eec2 stocktake 2026-10-14: SECOND Proxmox host m93p (100.104.51.98, PVE 9.2.0, unclustered, IDs collide) discovered — gitea/ntfy/freshrss/openweb were never on pve; tailnet inventory rebuilt 30 -> 45 nodes (15 missing); VM 282 running; Camofox recovered to 29.9M
skills-index 346 skills / 70 cats; freshness 48 stale / 38 fresh / 7 no-date of 93 pages

- infra/proxmox.md: two-host rewrite, m93p LXC+QEMU inventory, 4-entry correction table, VM 282 stopped->running, storage via pvesm (ssd0 88.17%/63GiB free)
- infra/tailscale.md: 45-node inventory rebuilt from live status; 23 funnel-ingress-node IPv6 peers noted+excluded; CT460 serve routes re-verified exactly (13 routes + :8443 Funnel + :9443)
- infra/network-map.md, current-state.md, index.md, log.md updated
- Open: 3 incidents (unverified pages left stale, not rewritten); omniroute/hosts/model-providers/docker-services still single-host in framing — m93p runs its own omniroute CT101, needs a dedicated pass
2026-10-14 03:13:04 +08:00

8.7 KiB

Anthony's Systems Wiki

Operational knowledge for Anthony's agents, infrastructure, model routing and automation. Last updated: 2026-10-14

⚠ Two Proxmox hosts exist — always qualify a guest with its host. A second unclustered hypervisor, m93p (100.104.51.98, PVE 9.2.0), was discovered during the 2026-10-14 stocktake. Guest IDs collide between the two hosts.

Start here

Systems

Core

Integrations

  • systems/messaging-integrations — Telegram, Discord, email, Slack, etc.
  • systems/scheduled-tasks — 29 cron jobs (26 enabled, 3 disabled); 4 carry a non-clean last_status as of 2026-10-14 00:15. The clean streak broke on 2026-10-13: 167 completed / 1 failed, after 10-12 finalised 175 / 0 (10-11 172 / 0, 10-10 175 / 0) — 1a8e90ea2271 (wiki-stocktake-maintenance, 03:00) hit HTTP 404: No active credentials for provider: opencode, its third failure in six days, so open incidents rose 2 → 3. Two rows cleared: fad5a86979d4 (10-12 03:05), dca8482e4f76 (10-13 07:02). The DHL monitor 62619aa6bcb3 was retired on 2026-10-10. ⚠ A green cron row is not proof of delivery: GitHub Trending Radar's Telegram token is revoked (getMe → 401) while the row stays green — it next runs Mon 09:00. See incidents/2026-10-09-cron-provider-timeout-storm
  • systems/skills-index — Installed skills inventory (346 skills / 70 categories; regenerated daily by the 03:00 stocktake job). Note: 347 SKILL.md files exist on disk — the generator de-dups one nested duplicate, see systems/scheduled-tasks. ⚠ The 2026-10-13 regeneration wrote the file but the stocktake job died before committing, so the artifact sat stranded until the 2026-10-14 audit committed it (date-only change: updated/verified_on 10-12 → 10-13).

Incidents

  • incidents/2026-10-09-cron-provider-timeout-storm — Fleet-wide provider timeout storm: 15 failed executions across 10 jobs on 2026-10-09, all RuntimeError: Request timed out. on the aliases behind custom:omni-101, 00:00 → 15:00 AWST; 11 of its 12 incidents are now closed (five on 2026-10-10, the last hold-out dca848_23fcd2b18aaa on 2026-10-12 07:33:41). 1 remains alerted — 1b23c042e17d, the weekly Friday job, which cannot clear before its next slot (Fri 2026-10-16 08:00)
  • incidents/2026-10-09-memory-recall-relevance — Recall relevance: a stale conversational episode outranked current-state facts on an open question; capture and vectorisation verified healthy, the ranking fix was never persisted in config (unresolved)
  • incidents/2026-10-05-dead-model-pin-repin — Seven cron jobs on dead model pins (cliprox/terra, qwen3.5:397b, deepseek-v4-flash, gpt-5.6-terra) repinned to routing aliases on custom:omni-101; failing set 7 → 0 (resolved 2026-10-05)
  • incidents/2026-10-03-mnemosyne-vector-recall-fts-only — Mnemosyne recall had been scoring keyword-only (fastembed missing from the managed runtimes); repaired 2026-10-03, coverage re-verified at 96.5% working / 99.4% episodic
  • incidents/2026-10-03-ct450-hermes-update — Chaos instance CT450 updated v0.19.0 → v0.21.5 (resolved); access path and pre-flight checks documented
  • incidents/2026-10-01-cliproxy-connection-auth-expired — OmniRoute cliprox/terra connection credential expired (all 3 jobs on the pin failed, settled 2026-10-04); closed 2026-10-05 when all three were repinned off the pin
  • incidents/2026-08-26-work-outlook-basic-auth-disabled — Work Outlook mailbox unreachable: tenant allows only XOAuth2, himalaya configured for password (open since 2026-08-26)
  • incidents/2026-09-28-hermes-managed-runtime-deps — Managed-runtime venvs missing dotenv/mnemosyne broke every cron worker (resolved 2026-09-30); dependency guard now runs every 15 min. Recurred 2026-10-10 inside the gateway runtime env — mnemosyne and elevenlabs missing from the committed uv env the gateway loads; both repaired and verified the same evening
  • incidents/2026-08-18-mnemosyne-capture-pipeline — Mnemosyne capture pipeline broken (Aug 2026, superseded): capture verified healthy 2026-10-12 — 786 working rows, +2 that day, 98.3 % embedded
  • incidents/2026-08-15-skills-index-drift — Skills index 4x undercount (66 vs 330 installed); fixed via auto-regeneration

Monitoring & Dashboards

Reports

Infrastructure

Services

Networking

  • infrastructure/proxmox — PVE hosts (two: pve 8.x + m93p 9.2.0, unclustered, IDs collide), VMs, LXC containers, storage (/mnt/ssd0 88.17 % / ~63 GiB free, 2026-10-14)
  • infrastructure/tailscale — Tailscale serve routes (CT460 verified exactly) and the 45-node tailnet inventory (2026-10-14)
  • systems/cloudflare-tunnel — ct207-hosted tunnel serving Hermes publicly

Concepts

Decisions

Comparisons

Runbooks

Raw