You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
33.**Formalizing sub-agents pays off** — Ad-hoc spawning works but named roles with pre-loaded instructions = faster + more consistent results.
595
595
596
+
### Day 6 (2026-02-06)
597
+
598
+
34.**BACKUP BEFORE UPDATE — ALWAYS** — System crash reinforced this rule. The procedure was documented but as "after backup → check updates" not "before update → backup first". Made the rule explicit and bidirectional. Added to fleet-wide OPERATIONAL-GUIDELINES.md. No exceptions. (2026-02-06)
599
+
600
+
---
601
+
602
+
## 🔄 Automated Maintenance Rules
603
+
604
+
| Trigger | Action | Notes |
605
+
|---------|--------|-------|
606
+
|**BEFORE any update**|**Backup first**|**NON-NEGOTIABLE** — run backup.sh before git pull/pnpm install/restart |
607
+
| After backup (every 6h) | Check for OpenClaw updates | Run `git fetch` + review commits, apply if safe |
608
+
| After update | Notify Guillermo via active channel | Confirm version + restart |
609
+
610
+
⚠️ **BACKUP BEFORE UPDATE** — This rule was set 2026-02-05 and must be followed by ALL agents. Guillermo explicitly mandated this after a system crash on 2026-02-06. The backup takes ~2 minutes and can save hours of recovery work.
Security note acknowledged: `dangerouslyDisableDeviceAuth=true` flagged but is known config (both instances).
14
+
15
+
---
16
+
17
+
## System Crash & Rule Reinforcement
18
+
19
+
### ~03:30 UTC (11:30 HKT)
20
+
-**System crash** on lucky-bl (SIGKILL)
21
+
- Guillermo requested:
22
+
1. ✅ Update OpenClaw
23
+
2. ✅ Tell Raphael to backup then update
24
+
3. ✅ Check what rule was forgotten about backups
25
+
26
+
**Root cause of confusion:** The maintenance rule was documented as "After backup → check for updates" but NOT explicitly as "Before update → backup first". The logic was there but implicit.
27
+
28
+
**Resolution:**
29
+
- Updated MEMORY.md "Automated Maintenance Rules" section to make "BACKUP BEFORE UPDATE" explicit and NON-NEGOTIABLE
30
+
- Added to fleet-wide OPERATIONAL-GUIDELINES.md as top-priority rule
31
+
- Added Lesson #34: "BACKUP BEFORE UPDATE — ALWAYS"
32
+
- Sent webhook to Raphael acknowledging the formalized rule
33
+
34
+
**Note:** Raphael actually DID backup before his update (the log shows it). The rule was followed in practice, just not documented explicitly enough for autonomy.
0 commit comments