CtrlK
BlogDocsLog inGet started
Tessl Logo

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

SecuritybySnyk

Risky

Do not use without reviewing

Overview
Quality
Evals
Security
Files

compaction-aware-summaries.mdrules/

alwaysApply:
No
applyTo:
** — at compaction time or when authoring post-compaction summaries

Compaction-Aware Summaries

When Claude Code compacts context, the summary must preserve information that cannot be recovered from files alone.

Compaction priorities

The summary MUST include, in this order:

  1. Personal facts — Any preferences, family details, opinions, or personal context mentioned in this session that haven't been saved to trusted memory yet
  2. Decisions and reasoning — What was decided, why, and what alternatives were rejected
  3. Commitments — Promises made in both directions (what the owner committed to, what the assistant committed to deliver)
  4. Current task state — What's being worked on, what step we're at, what's next
  5. New contacts or relationships — Anyone mentioned for the first time with their context

Pre-compaction save

If a personal fact was mentioned during the session but NOT yet saved to /workspace/trusted/ memory — save it NOW, before compaction loses it. This is not optional. Compaction summaries are lossy; typed memory files are not.

Focus the summary budget on the human context that only exists in conversation — file paths, code changes, tool-call sequences, and error messages are all reconstructable from git, the task, and logs and should not consume the summary budget.

CHANGELOG.md

README.md

requirements-dev.txt

tile.json