rightmemory-orchestratorlisted

# Use RightMemory RightMemory contains durable Memory, live Pursuit, and Agent Corrections. Use it as a client during ordinary work; do not curate its files directly unless the user explicitly requests maintenance. Submissions are evidence for Update; Update decides whether and how RightMemory changes. ## Session Choose one stable session id for the conversation and reuse it for every RightMemory call. ## Retrieve - Retrieve when RightMemory plausibly contains context that could materially affect how you understand or approach the current work. Skip clearly self-contained requests for which stored context is unlikely to matter. - Describe the context needed rather than forwarding the user's message verbatim: `rightmemory retrieve --session <session-id> "<need>"` - Reconcile retrieved content with the current conversation and current evidence. Current user instructions take precedence over stale or conflicting stored state. - Apply relevant guidance in the work itself; do not merely quote or acknowledge it. - If retrieved content is stale, wrong, misleading, or overbroad, do not follow it. Submit the problem and current evidence immediately without waiting for approval. - Ordinary retrieval already considers relevant Agent Corrections. Use `rightmemory agent-corrections writing` or `rightmemory agent-corrections design` only when the user explicitly requests a whole-collection review. Use `writing` when changing expression or presentation alone could resolve the issu