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
When you learn something new and operationally important — a workflow, where something lives, how something works, a tool to use for a specific task — immediately record it via the skills/trusted-memory/scripts/append-daily-discovery.py script:
python3 <resolved-path>/append-daily-discovery.py \
--what "<one-line description of what you learned>" \
--context "<how you found out / what prompted this>" \
--promote-to "<RUNBOOK.md | typed memory file + MEMORY.md index | unsure>"Resolve <resolved-path> to the tile's installed location in your container (the trusted-memory skill's runbook gives the exact directory; inside the running container it is /home/node/.claude/skills/tessl__trusted-memory/scripts/).
The script appends a block in this canonical shape to /workspace/trusted/memory/daily_discoveries.md:
What: [one-line description of what you learned] Context: [how you found out / what prompted this] Promote to: [RUNBOOK.md / typed memory file + MEMORY.md index / unsure]
Script behavior:
fcntl.LOCK_EX on a sibling <file>.lock for the entire read-modify-write cycle.os.replace.{path, appended, dropped_duplicate, created, timestamp}.--discoveries-file or NANOCLAW_DISCOVERIES_FILE env var.Do this immediately when learned, not at end of session. This ensures the knowledge survives context compaction.
rules
skills
system-status