mirror of
https://github.com/dtzp555-max/memory-continuity.git
synced 2026-07-21 21:15:07 +00:00
Clarify execution-agent-dispatch scope and harden gateway rules
This commit is contained in:
@@ -0,0 +1,5 @@
|
||||
# 2026-03-12
|
||||
|
||||
- Tao explicitly reinforced a hard rule after gateway disruption: on Tao's machine, do not run `openclaw gateway stop`, and do not assume `openclaw gateway restart` is safe. Treat restart-style lifecycle control as disruptive and approval-required.
|
||||
- Durable lesson: before any gateway intervention, first run `openclaw gateway status`, report findings, prefer non-disruptive diagnosis, and get Tao approval for the exact lifecycle command if one is still necessary.
|
||||
- Trigger for this rule: attempted gateway restart led to service becoming unavailable and Tao needing to manually reinstall/restore gateway service again. This is a high-friction failure and must not be repeated.
|
||||
Reference in New Issue
Block a user