slm-scope

# slm-scope — Memory Scope and Sharing Model SuperLocalMemory is profile-isolated by default. Every profile is a fully independent memory namespace. The scope model adds controlled, opt-in sharing between profiles on the same machine — it is never active unless you explicitly set it. --- ## The Three Scopes | Scope | Visibility | When to use | |-------|-----------|-------------| | `personal` | Active profile only | Default — all facts. Never set explicitly. | | `shared` | Active profile + `shared_with` profiles | Team handoffs, shared project context | | `global` | Every profile on this machine | Machine-wide conventions, org-wide rules | **The default is always `personal`.** A fact stored without a `scope` argument is private to the profile that stored it. Recall without scope flags returns only personal facts. This is identical to single-profile SLM. --- ## Opt-in is mandatory Never set `scope="shared"` or `scope="global"` (or the recall equivalents `include_shared`, `include_global`) unless the user explicitly asks you to share or read across profiles. This is a hard rule — scope expansion is an action with team-wide or machine-wide impact, and it must always be user-initiated. --- ## Writing a shared or global fact ### share with specific profiles ``` remember( content="API gateway rate limit is 1000 req/min per client", tags="api,limits,ops", project="platform", importance=8, session_id="<sid>", scope="shared", shared_with="devops-profile,backen...