Session continuity
Carry useful project context forward so an agent does not have to rediscover the same ground each time.
Give coding agents such as Claude Code and Codex continuity without turning every observation into universal truth. ProofMEM makes retained context a product boundary that can be reviewed and governed.
A Blue Note Logic product · Founding access open
Choose ProofMEM when an agent repeatedly loses project context between sessions, yet the answer cannot be an unrestricted shared notebook.
Carry useful project context forward so an agent does not have to rediscover the same ground each time.
Keep retained context attached to the work, namespace, and authority it belongs to.
Treat durable context as something that can be inspected and corrected rather than silently accumulated.
Useful memory is selective. ProofMEM separates durable context from the temporary conversation that produced it.
Store the context the workflow is allowed to carry forward, not an indiscriminate transcript.
Memory is retrieved for the active scope instead of being treated as global truth.
Teams can inspect the retained context and govern what should continue to influence future work.
Through Caveau Harness, approved intent and current repository evidence can enter the same task as separate, clearly labelled authorities.
ProofGit supplies current repository explanations, exact source lines, paths, trust status, and commit-pinned evidence URLs.
ProofMEM supplies approved objectives, constraints, decisions, and lessons. It may retain source pointers after explicit acceptance, never copied source lines or full evidence bundles.
ProofMEM is the independent product for agents that need durable context across sessions.
caveauMEM stays inside caveauAI as that platform’s governed memory layer.
See the caveauAI summaryWe will map the source material, responsible person, and approval boundary before recommending a product.