Unified Memory Substrate with CLAUDE.md Transparency

Determine whether and how a single memory substrate can simultaneously support a user’s personal instruction hierarchy and a shared organizational context while preserving CLAUDE.md-style file-based transparency.

Background

The authors emphasize file-based, user-editable memory as a key value. They ask whether a unified substrate can encode both personal and organizational knowledge without sacrificing the transparency and auditability of CLAUDE.md. This has implications for version control, governance, and user trust.

A successful answer would define how to merge individualized and shared contexts in a transparent, inspectable way that scales across teams and projects.

References

Whether a single substrate can carry both a user's personal instruction hierarchy and a shared organisational context while preserving the file-based transparency of CLAUDE.md that \Cref{sec:context} documents is an open architectural question.

— Dive into Claude Code: The Design Space of Today's and Future AI Agent Systems  (2604.14228 - Liu et al., 14 Apr 2026) in Section 12.2 (Persistence: Memory and Longitudinal Colleague Relationships)