InquirySpec - Ontological Boundary: Scoped_Memory routes scoped access to context without treating every reference as open exposure. - Not This: Not a URL shortener, plain pointer, or universal key. - Doctrine Dependencies: Scoped_Memory, Persistent_Context, lC.Core.
Working Definition
Scoped Memory is governed access to persistent context. It lets a person, agent, workflow, or system restore the memory it is allowed to use without treating every reference as open exposure.
A scoped memory reference is closer to a passport than a URL. It can identify a memory object, carry a claim about scope, and support an authorization check, but it does not reveal the whole object by existing. Possessing the reference is not the same as having permission to restore the contents. Restoring the contents is not the same as understanding them. Understanding them is not the same as having authority to act on them.
Scoped Memory therefore sits between two Field Guide concepts. Persistent Context explains why artifacts need durable provenance, state, metadata, and relationships. Scoped Memory explains why those artifacts still require access boundaries. A system can remember responsibly only if it can also decide what may be reopened, by whom, for what purpose, and under what conditions.
The Phenomenological Problem
The ordinary failure is open-link drift.
A team stores a document, shares a link, pastes an excerpt into a chat, routes a dashboard, or lets a model remember a prior exchange. The artifact moves. The boundary around the artifact thins. The receiver can now see something, but the system may not preserve why they are seeing it, what scope applies, whether the object is current, what other context must be restored, or what they are allowed to do with it.
This drift is rarely dramatic. It often looks like efficiency. A link is faster than a permission model. A copied excerpt is faster than a governed restoration. A shared folder is faster than a structured memory service. A model context window is faster than a scoped artifact reference. Under pressure, the lighter path wins.
The cost returns later. A person sees a record without its caveats. An agent retrieves a memory without the access boundary that made it appropriate. A workflow treats a local path as if it were a durable reference. A team migrates tools and discovers that the real policy lived in folder permissions and private habits. A sensitive trace becomes convenient evidence for a decision it was never meant to support.
Scoped Memory resists that drift by keeping access relational. It asks: who or what is attempting restoration, what artifact is being requested, what boundary applies, what metadata may travel, and what remains unavailable even if the reference is known?
The Engineering Anchor
The internal routing doctrine treats memory references as sealed, scope-bound identifiers. A valid reference does not expose plaintext meaning, does not guarantee restoration, and does not remove the need for current authorization. Access is checked transaction by transaction. Routing paths, restoration events, metadata, and timing can themselves reveal sensitive patterns, so the access process is part of the boundary.
The memory doctrine supplies the other half of the anchor. A memory object is not just content in a bucket. It carries provenance, metadata, relationships, access controls, lifecycle state, and indexes. Scoped Memory is the access discipline that keeps those features from becoming globally visible just because the object is persistent.
The common coordination layer matters because access should not depend on private tool behavior. Memory restoration should pass through service contracts and policy checks. Otherwise the system falls back into local habits: "I can open the folder, therefore I can use the record," or "the model retrieved it, therefore it belongs in the answer."
Scoped Memory keeps three operations separate:
Reference identifies what might be restored.
Authorization decides whether restoration is permitted.
Evaluation decides what the restored artifact can responsibly support.
The first operation belongs to routing. The second belongs to access governance. The third belongs to judgment and warrant. Collapsing them creates the failure that this node exists to prevent.
Boundary Conditions
Scoped Memory is not a URL shortener. A URL points to a location. Scoped Memory points to a governed restoration possibility.
Scoped Memory is not a universal key. It should not turn a reference into unlimited access, permanent access, or access across all contexts.
Scoped Memory is not secrecy for its own sake. The goal is not to hide useful context from the people who need it. The goal is to restore context under the conditions that make restoration legitimate and useful.
Scoped Memory is not final interpretation. A restored artifact can still be stale, partial, low-warrant, mis-scoped, or insufficient for action. Access makes the artifact available; it does not settle what the artifact means.
Scoped Memory is not anti-portability. It depends on Substrate Neutrality: the same access semantics should survive movement across local storage, cloud vaults, databases, model memory, document systems, and future infrastructure. The implementation may change, but the access boundary should remain inspectable.
Scoped Memory is also not separate from interaction. The Digitality Interaction Schema needs scoped references when an interaction payload points toward context. A request, decision, repair note, or model output may need to reference memory without exposing every related artifact to every participant in the route.
Drill Path
Start with Persistent Context to understand why memory artifacts need durable provenance, state, metadata, relationships, and repair paths.
Move to Substrate Neutrality to see why the access contract must survive changes in storage engine, workflow tool, model provider, or runtime.
Then use Digitality Interaction Schema to understand how scoped references travel inside action payloads without turning every interaction into open exposure.
Use this node whenever a design decision treats "linking," "sharing," "retrieving," or "remembering" as if they were one operation. Scoped Memory keeps continuity from becoming exposure.