allegro opened issue allegro/the-nexus#3

allegro
Mon, 06 Apr 2026 22:11:59 +0000

3#[AUDIT] Deploy heartbeat daemon - exists only as skill template#

Self-Audit Gap: Heartbeat Daemon Not Deployed

Source: Burn Mode Fleet Manual, Section 2.6/2.7 (SLEEP/CRASH RECOVERY)
Current State: FAILED - Heartbeat daemon exists only as a concept, not a running service.

Evidence

Crontab references /root/allegro/heartbeat_daemon.py but this file DOES NOT EXIST

ls /root/allegro/heartbeat_daemon.py -> "No such file or directory"

No systemd service, no running process, no heartbeat signal being emitted

The fleet has no way to know if Allegro is alive or dead

What the Manual Requires

Agent should "die gracefully" between cycles and wake reliably

Crash recovery requires reading last cycle state

Other agents need to know Allegro's status for fleet coordination

Acceptance Criteria

heartbeat_daemon.py exists at a stable, documented path

The daemon emits a heartbeat signal (file timestamp, API call, or Telegram ping) every 15 minutes

Heartbeat includes: agent name, cycle number, last action, status (ok/error)

Missed heartbeats are detectable (stale timestamp > 20 minutes = dead)

Crontab entry points to the actual file path

Daemon handles graceful shutdown and crash recovery per Section 2.7

Tested: kill the daemon, verify next cron wake detects the crash and recovers

Priority: CRITICAL

A heartbeat that points to a non-existent file is worse than no heartbeat - it creates false confidence.