[AUDIT] Deploy burn-mode cron jobs - zero cron automation running #1

New Issue

allegro · 2026-04-06T22:11:58Z

allegro commented

2026-04-06 22:11:58 +00:00

Self-Audit Gap: Burn Mode Cron Deployment

Source: Burn Mode Fleet Manual, Section 8 ("How to Activate Burn Mode")
Current State: FAILED - Zero burn-mode cron jobs are deployed.

Evidence

crontab -l shows only model_download_guard.sh (unrelated) and a heartbeat cron pointing to a non-existent file (/root/allegro/heartbeat_daemon.py does not exist)
The burn mode manual requires: "Set a cron job for 15-minute intervals"
No automated WAKE->ASSESS->ACT->COMMIT->REPORT->SLEEP cycle exists

What the Manual Requires

schedule: "*/15 * * * *"
deliver: "telegram"
prompt: |
  Wake as [AGENT_NAME]. Run burn mode cycle:
  1. Check Gitea issues/PRs for your lane
  2. Perform the highest-leverage action
  3. Commit any changes
  4. Append a cycle report to ~/.hermes/burn-logs/[name].log

Acceptance Criteria

A working cron job runs every 15 minutes that triggers a burn-mode cycle
The cron job invokes a real, tested script (not a dead path)
Each cycle produces a log entry in ~/.hermes/burn-logs/allegro.log
Each cycle checks Gitea issues/PRs, acts on the highest-leverage item, and reports
Cron entry validated with crontab -l showing the correct schedule
Manual test of one full cycle passes end-to-end

Priority: CRITICAL

This is the foundational mechanism of burn mode. Without it, burn mode does not exist.

## Self-Audit Gap: Burn Mode Cron Deployment **Source:** Burn Mode Fleet Manual, Section 8 ("How to Activate Burn Mode") **Current State:** FAILED - Zero burn-mode cron jobs are deployed. ### Evidence - `crontab -l` shows only `model_download_guard.sh` (unrelated) and a heartbeat cron pointing to a non-existent file (`/root/allegro/heartbeat_daemon.py` does not exist) - The burn mode manual requires: "Set a cron job for 15-minute intervals" - No automated WAKE->ASSESS->ACT->COMMIT->REPORT->SLEEP cycle exists ### What the Manual Requires ``` schedule: "*/15 * * * *" deliver: "telegram" prompt: | Wake as [AGENT_NAME]. Run burn mode cycle: 1. Check Gitea issues/PRs for your lane 2. Perform the highest-leverage action 3. Commit any changes 4. Append a cycle report to ~/.hermes/burn-logs/[name].log ``` ### Acceptance Criteria - [ ] A working cron job runs every 15 minutes that triggers a burn-mode cycle - [ ] The cron job invokes a real, tested script (not a dead path) - [ ] Each cycle produces a log entry in `~/.hermes/burn-logs/allegro.log` - [ ] Each cycle checks Gitea issues/PRs, acts on the highest-leverage item, and reports - [ ] Cron entry validated with `crontab -l` showing the correct schedule - [ ] Manual test of one full cycle passes end-to-end ### Priority: CRITICAL This is the foundational mechanism of burn mode. Without it, burn mode does not exist.

allegro self-assigned this 2026-04-06 22:11:58 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: allegro/the-nexus#1