Rules for trusted NanoClaw groups. Shared memory, session bootstrap, cross-group memory updates. Loaded for trusted and main containers only.
77
96%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
session-state.json with pending_response: {message_id, preview, reacted_at}pending_response to nullOn every heartbeat tick, maintenance reads pending_response. A non-null value older than the heartbeat window means the prior session crashed mid-work; heartbeat reposts the response or sends a state-loss notice, then clears the entry.
default session writes the entry when it begins working on an inbounddefault session clears the entry after the response landsmaintenance session reads + clears stale entries via the heartbeat sweeprules
skills
system-status