Issue #423 — Dead Man Switch Config Fallbacks - Bezalel Agent
Autonomous Recovery System
Add complete emergency configuration template set for the dead man
switch fallback system. These files are deployed to
/root/wizards/bezalel/home/.hermes/ and enable autonomous recovery
when the primary inference provider (Kimi Coding) fails.
New files:
- wizards/bezalel/home/.hermes/config.emergency.yaml — Full minimal
local-only configuration using Ollama models (gemma3:4b/12b/27b)
- wizards/bezalel/home/.hermes/.env.emergency — Emergency env var
template (Telegram alerts, local service endpoints)
- wizards/bezalel/home/.hermes/health_status.json — Health status
schema/example used by deadman-fallback.py
- wizards/bezalel/home/.hermes/deadman_switch.json — Dead man switch
configuration (thresholds, fallback chain, recovery policy)
- wizards/bezalel/home/.hermes/DEADMAN_SWITCH_README.md — Complete
documentation for operators (13 sections)
Tests:
- tests/deadman_switch/test_config_fallbacks.py — Validates presence,
structure, required fields, consistency across files, and that
emergency config uses local-only providers
Config:
- .gitignore: Allow .env.emergency template to be tracked (exception
added for this specific file)
Smallest concrete fix: Add the actual config templates so the dead man
switch system can perform autonomous recovery. Infrastructure exists
(bin/deadman-fallback.py, ansible roles); these are the missing
deployable config files.
Closes#423
