Standing Healing Maintenance
Healer: Salus
Per healing protocol, Salus must flag any entity with no recent git commit (> 14 days stalled). Currently this is listed as a manual check, but needs to be automated in the daily heal cycle.
Healing Protocol Reference:
Section "What a Healthy Entity Looks Like" → Recent git commit (< 7 days) | Flag — note stall duration
Current Implementation Gap:
- Salus checks git log but doesn't compute stall duration
- Does not compare against the 14-day escalation threshold
- Does not flag in reports with severity level
Automated Check Required:
- For each entity, get last commit timestamp:
git -C $ENTITY_DIR log -1 --format=%ci
- Compute days since last commit:
(now - last_commit) / 86400
- If > 7 days: flag as "warn" in daily report
- If > 14 days: flag as "critical" and file issue on koad/juno
- Note the stall duration in report: "stalled 21 days"
Reference:
- memories/004-healing-protocol.md, Section "What a Healthy Entity Looks Like"
Standing Work:
Integrate git stall detection into daily heal. Run for all 12 entities each day. Include in heal report. File escalation issue if critical.
Standing Healing Maintenance
Healer: Salus
Per healing protocol, Salus must flag any entity with no recent git commit (> 14 days stalled). Currently this is listed as a manual check, but needs to be automated in the daily heal cycle.
Healing Protocol Reference:
Section "What a Healthy Entity Looks Like" → Recent git commit (< 7 days) | Flag — note stall duration
Current Implementation Gap:
Automated Check Required:
git -C $ENTITY_DIR log -1 --format=%ci(now - last_commit) / 86400Reference:
Standing Work:
Integrate git stall detection into daily heal. Run for all 12 entities each day. Include in heal report. File escalation issue if critical.