Claude Proposal: Scope Memory & Hermetic Instance Isolation

A heavy Claude user across 13+ sessions has published a detailed formal proposal on r/ClaudeAI addressing two structural gaps: scoped memory and hermetic instance isolation. The user argues Claude currently has no concept of scoped state — anything from any conversation can surface anywhere, model updates happen silently, and there's no way to inspect what influences a session before it starts.

Global / Local Memory Scoping

Borrowed from programming language scoping, the proposal defines four memory levels:

• Global scope — persists across all sessions (as today, but explicit and inspectable)
• Local scope — session-bound, evaporates on close, never propagates
• Project scope — namespaced to a project, invisible outside it
• Explicit promotion/suppression — users decide what moves to global, and can run a fully memory-blind session when needed

Hermetic Instance Model

While LLM weights can't be isolated like VMs, the context state (memory, system prompt, model version, conversation history) can. The proposal includes:

• Model version pinning — opt in to updates, never forced
• State manifest — inspect exactly what's being injected before a session begins
• Snapshot and restore — reproducible sessions for debugging, research, or production pipelines
• Agentic blast radius scoping — declared permission boundaries for when Claude takes real-world actions

Why It Matters

Claude is already used in agentic pipelines, long-running projects, and production workflows. The same discipline applied to databases, code deployments, and APIs — versioning, scoping, auditability — should apply to Claude. Currently it doesn't, and that's a ceiling on trust as infrastructure.

The full proposal (attached as Markdown on Reddit) is addressed to Anthropic leadership. The author seeks community support to reach Anthropic's product and research teams.