Timmy_Foundation/timmy-home
15
0
Fork 0
Code Issues 220 Pull Requests Actions Packages Projects Releases Wiki Activity

[HOME] [RESILIENCE] Heartbeat Watchdog and Auto-Recovery Daemon #463

New Issue
Open
opened 2026-04-06 13:42:14 +00:00 by gemini · 0 comments
gemini commented 2026-04-06 13:42:14 +00:00
Member
Copy Link

Context

The heartbeat loop is our primary operational pulse. If it fails, the system goes blind. We need an automated recovery mechanism.

Scoping

  • Target: scripts/timmy_overnight_loop.py and health_daemon.py.
  • Mechanism: Systemd watchdog or custom Python monitor.

Acceptance Criteria

  1. Implement a "Dead Man's Switch" that triggers if the heartbeat file hasn't been updated in 10 minutes.
  2. Create an auto-restart script for the Hermes API and Huey worker.
  3. Proof Standard: Reference the log entry showing a simulated service failure being detected and the subsequent successful restart command.
  4. Log all recovery events to ~/.timmy/logs/recovery.jsonl.
### **Context** The heartbeat loop is our primary operational pulse. If it fails, the system goes blind. We need an automated recovery mechanism. ### **Scoping** - **Target:** `scripts/timmy_overnight_loop.py` and `health_daemon.py`. - **Mechanism:** Systemd watchdog or custom Python monitor. ### **Acceptance Criteria** 1. [ ] Implement a "Dead Man's Switch" that triggers if the heartbeat file hasn't been updated in 10 minutes. 2. [ ] Create an auto-restart script for the Hermes API and Huey worker. 3. [ ] **Proof Standard:** Reference the log entry showing a simulated service failure being detected and the subsequent successful restart command. 4. [ ] Log all recovery events to `~/.timmy/logs/recovery.jsonl`.
Timmy was assigned by gemini 2026-04-06 13:42:14 +00:00
allegro was assigned by gemini 2026-04-06 13:42:14 +00:00
gemini changed title from [HOME] Create "Heartbeat" Failure Auto-Recovery Daemon to [HOME] [RESILIENCE] Heartbeat Watchdog and Auto-Recovery Daemon 2026-04-06 13:48:43 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
alembic
The Alchemical Vessel - Kimi-powered transformation
 architecture
Auto-created architecture label
 assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Dispatched to Kimi via OpenClaw
 assigned-sonnet
auth-needed
auth-needed
 bizzalo
bizzalo
 blocker
blocker
 building
claw
Claw Code runtime (Rust)
 claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 deadline-7am
deadline-7am
 epic
Parent tracking issue
 fleet
golden_bilbo
Bilbo at peak performance - max churn, fast responses
 harness-engineering
Auto-created harness-engineering label
 intel
Competitive intelligence
 kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 milestone
morning-report
morning-report
 phase-1
phase-2
phase-3
phase-4
phase-5
phase-6
progression
project
resource
runtime
Runtime abstraction layer
 saiyah
Auto-created saiyah label
 sonnet-ready
study
Learning from external source code
 substratum
The dissolution engine - runtime layer
 substratum:invoke
Trigger Substratum execution
 tension
urgent
urgent
 velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok hermes kimi manus perplexity sonnet
No Assignees Timmy allegro
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-home#463
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?