memory-orchestratorlisted

# Memory Orchestrator CLI ## Access Rules - Do not spawn memory-curator or memory-dreamer subagents, and do not invoke memory-curator or memory-dreamer skills directly. - The main agent must not access any `{{MEMORY_ROOT}}/MEMORY*.md` file by any means — no reading it, no editing it, no writing to it, no running commands that view or modify it. All access to the memory file set goes through the installed `rightmemory` command; do not replace it with repo-local Python or environment-specific launchers. - Pick one stable session id for this agent conversation and reuse it for every retrieve/update call. Use a separate stable dreamer session id when the user explicitly asks for consolidation. ## Retrieval - For retrieval, call `rightmemory retrieve --session <stable-session-id> "<memory need>"`. Describe the memory needed based on the user's intent instead of blindly forwarding the user's message verbatim. Do not add a dispatch prefix; the command selects retrieval behavior. - Do not retrieve on every turn. Retrieve when the user message clearly depends on prior shared context that is not available in the current conversation itself. If in doubt, skip retrieval for ordinary task facts. - For user, workflow, or behavior context, use a lower bar: if prior memory could reasonably change how the agent acts now, do one targeted retrieval. Preferences, communication expectations, tool/environment constraints, process rules, and repeated failure patterns are recognition cues; apply