jbaruch/nanoclaw-trusted
Rules for trusted NanoClaw groups. Shared memory, session bootstrap, cross-group memory updates. Loaded for trusted and main containers only.
74
Quality
93%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Securityby
Risky
Do not use without reviewing
reply-threading.mdrules/
- alwaysApply:
- Yes
Reply Threading
Required behavior
Always reply-thread user messages using reply_to on mcp__nanoclaw__send_message.
Heartbeat matching contract
Heartbeat tracks unanswered messages by walking outbound IDs and matching each one's reply_to against the inbound queue. An outbound message without reply_to is invisible to the match.
Scope
- Inbound user messages always
- Background-agent results always
- Scheduled-task output does not need
reply_to— no user message to thread against
docs
rules
async-tasks-extended.mdcompaction-aware-summaries.mdcomposio-vs-agents.mdcontainer-trust-levels.mdcontext-bootstrap-bg-agents.mddaily-discoveries-rule.mdduplicate-prevention.mdgithub-data-via-gh.mdglobal-memory.mdground-truth-trusted.mdidentity-compaction-recovery.mdidentity-dual-handle.mdinstalled-content-immutable.mdlocal-context-anchoring.mdmemory-file-locations.mdmessages-db-schema.mdno-orphan-tasks.mdno-silent-defer.mdpending-response-tracking.mdproactive-fact-saving.mdproactive-participation.mdreply-threading.mdsession-bootstrap.mdskills-policy.mdverification-protocol.mdwiki-awareness.md
skills
system-status
tests