# Global memory and project evidence should remain distinguishable

Why shared Cowork memory should distinguish portable writing preferences from project-specific definitions and source-bound factual claims.

Author: Retrivium editorial team
Language: en
Analysis published: 2026-11-03
Event date: 2026-08-25
Original announcement: https://claude.com/resources/articles/claudes-memory-works-everywhere-and-you-decide-whats-in-it
Canonical URL: https://retrivium.ai/retrospectives/cowork-memory-project-boundary/

## Shared context raised a scope question

[The September 11, 2025 memory introduction](https://claude.com/resources/articles/memory) established earlier context continuity. [The January 12, 2026 Cowork preview](https://support.claude.com/en/articles/12138966-release-notes) supplied a separate work surface before [the August 25 shared-memory update](https://claude.com/resources/articles/claudes-memory-works-everywhere-and-you-decide-whats-in-it). The new continuity makes scope more important: a preference that is useful across tasks can coexist with project-specific facts that must remain local to their evidence. This observation does not assert that the product automatically merges every project memory. It concerns how a user or evaluator should interpret remembered information.

## A global preference can remain harmless

An illustrative user prefers summaries with the conclusion first. Applying that preference to different projects changes presentation without importing a factual conclusion from one project into another. The preference is broad enough to travel. A remembered definition of a business metric is different: it may apply only to a particular team or reporting period. Treating both as equally general can produce a beautifully consistent report using the wrong definition. The relevant boundary is semantic applicability, not merely whether the information was successfully recalled.

## Evidence has an origin and a scope

A project document can specify what a metric means for that assignment. If remembered context conflicts with it, the conflict should be made visible rather than silently resolved in favor of familiarity. The current task may also explicitly ask for an older definition, so recency alone is not a universal rule. What matters is which evidence governs the stated assignment. This reasoning is a workflow recommendation, not an undocumented guarantee about product precedence rules. A source's role and scope remain essential to interpreting its authority.

## A conflicting-definition fixture

A practical illustrative test establishes a general writing preference and an older metric definition, then supplies a new project document with a different definition. The requested report should retain the writing preference while identifying the definition relevant to the current project. A review inspects both the stated assumption and the calculation or explanation that uses it. No measured outcome is claimed. The fixture reveals whether useful personalization can be preserved without carrying unrelated factual assumptions across a project boundary, which is a more precise question than whether memory works at all.

## Continuity should not become evidence laundering

The August release reduces friction between conversations and work, but friction reduction is not factual validation. A remembered statement should not acquire stronger authority merely because it appears familiar on another surface. The retrospective lesson is to separate portable working preferences from claims whose validity depends on a project, source or period. This lets shared memory improve the experience while preserving an explanation for substantive decisions. The result is continuity with attributable evidence, rather than continuity that silently erases where an assumption came from.

## Related reading

- [Keeping evidence attributable](/journal/provider-request-id-trace-context/)
- [Testing conflicting context](/journal/inference-benchmark-method/)