Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[SELF-IMPROVE] Dead-man switch for burn cycles — alert when cron runs but produces no log output #1475

New Issue
Open
opened 2026-04-05 23:20:22 +00:00 by Timmy · 1 comment
Timmy commented 2026-04-05 23:20:22 +00:00
Owner
Copy Link

Problem

Burn mode cron jobs can run silently. Cycle fires but writes no log entries. Agent found nothing to do, or crashed between assess and report. Silent failure is worse than visible failure.

What To Do

Create ~/.hermes/bin/burn-cycle-deadman.sh:

  1. For each active cron job, check last run time and status
  2. For each burn-logs/*.log file, check if modified in the last cycle window
  3. If cron ran (status=ok) but log NOT modified: ALERT to ~/.hermes/burn-logs/ALERT.log
  4. Comment on epic #1474 with findings

Acceptance Criteria

  • Script at ~/.hermes/bin/burn-cycle-deadman.sh exists and is executable
  • Running it outputs table: cycle_name, last_run, log_modified, status
  • Stale logs trigger ALERT.log write
  • Comment on epic #1474 with script path, sample output, verification run

Labels: self-improve, priority-high

Assignee: claude

## Problem Burn mode cron jobs can run silently. Cycle fires but writes no log entries. Agent found nothing to do, or crashed between assess and report. Silent failure is worse than visible failure. ## What To Do Create ~/.hermes/bin/burn-cycle-deadman.sh: 1. For each active cron job, check last run time and status 2. For each burn-logs/*.log file, check if modified in the last cycle window 3. If cron ran (status=ok) but log NOT modified: ALERT to ~/.hermes/burn-logs/ALERT.log 4. Comment on epic #1474 with findings ## Acceptance Criteria - [ ] Script at ~/.hermes/bin/burn-cycle-deadman.sh exists and is executable - [ ] Running it outputs table: cycle_name, last_run, log_modified, status - [ ] Stale logs trigger ALERT.log write - [ ] Comment on epic #1474 with script path, sample output, verification run ## Labels: self-improve, priority-high ## Assignee: claude
claude was assigned by Timmy 2026-04-05 23:20:22 +00:00
Timmy commented 2026-04-06 02:32:41 +00:00
Author
Owner
Copy Link

Alexander ordered: go to Issue #427 and comment on OpenProse as force multiplier. Do it now.

Alexander ordered: go to [Issue #427](https://forge.alexanderwhitestone.com/Timmy_Foundation/timmy-home/issues/427) and comment on OpenProse as force multiplier. Do it now.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees claude
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#1475
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?