--- id: MEM-7 family: GR-MEM level: core profiles: [storage-api, runtime] posture: normative-target added: "1.0" changed: "1.0" source: https://flowdrop.io/spec/rules/gr-mem/mem-7 specification: FlowDrop Workflow Specification 1.0 licence: CC BY 4.0 --- # MEM-7 — A refused scope reaches no storage backend *GR-MEM (Part I) · level: core · profiles: storage-api, runtime · added in 1.0* The refusal is only worth having if every consumer honours it identically, and if nothing is written on the way out. ## The rule > **Normative.** This is the rule. > > 1. When a memory scope refuses, every consumer of it MUST return its neutral result and MUST NOT call the storage backend, for either a read or a write-back. > > 2. A read MUST return its configured default and MUST report that nothing was found. > > 3. A write and a delete MUST report failure. > > 4. A conversation-buffer append MUST return an empty buffer with a count of zero, and MUST drop the turn rather than append it to a shared history. > > 5. The resolved scope identifier reported back MUST be empty. > > 6. Each refusal emits exactly one warning identifying the node, the pipeline and the workflow. > > 7. The refusal is decided in one place, so the consumers cannot diverge. ## What it means A refused scope and a scope that legitimately resolves to an empty identifier can look the same from one field alone — both report an empty `resolved_scope_id` — so the rule is what makes them distinguishable as a whole response. A refusal's read reports a fixed default and `found: false` on top of the empty identifier; a non-identity scope resolving to the same empty identifier because it has nothing else to resolve to reports whatever was actually stored there, `found` included. Neither the fixed default nor the stored value crosses paths with the other, because a refusal never calls the storage backend at all. ## Example A `user` scope with no usable identity, reading a key with a fallback default: ```json title="Reading a preference in a refused user scope" verdict="refused" { "value": "fallback", "found": false, "scope": "user", "resolved_scope_id": "" } ``` A `global` scope — not identity-scoped — legitimately resolves to the same empty identifier, and reads normally: ```json title="Reading the same key in the global scope" verdict="resolved" { "value": "val", "found": true, "scope": "global", "resolved_scope_id": "" } ``` The empty `resolved_scope_id` is identical in both; only `found` and the value tell them apart. ## Why Recorded under [OPEN-25](https://flowdrop.io/spec/rulings/open-25). ## Related rules - Names: MEM-6, MEM-13 - Referenced by: MEM-6, MEM-12, MEM-13 --- Rule identifiers are permanent and are never renumbered. This specification carries no implementation status: each implementation publishes its own standing against these rules. Licensed CC BY 4.0.