# Durable project memory Persistent, attributable project knowledge that carries decisions, outcomes, requirements, failures, and operating state across agent sessions without assuming that every stored item remains true or safe. core-concept · Context & knowledge · emerging · Reviewed 2026-08-09 ## Definition Persistent, attributable project knowledge that carries decisions, outcomes, requirements, failures, and operating state across agent sessions without assuming that every stored item remains true or safe. What survives a context reset becomes institutional infrastructure—and a new integrity boundary. Useful patterns exist; no settled enterprise memory architecture has emerged. ## Why it matters What survives a context reset becomes institutional infrastructure—and a new integrity boundary. The operating shift is from “Chat history as memory” to “Governed institutional state.” ## System anatomy - **Practice 1:** Store decisions and progress as reviewable artifacts - **Practice 2:** Attach provenance, permissions, and freshness rules - **Practice 3:** Validate memory before it re-enters context ## Important distinctions - **Chat history as memory:** This concept moves the engineering system toward governed institutional state. ## Implementation signals - Store decisions and progress as reviewable artifacts - Attach provenance, permissions, and freshness rules - Validate memory before it re-enters context ## Failure modes - Memory poisoning that persists across sessions - Stale summaries becoming invisible policy ## Related knowledge - [Context engineering](https://aisdlc.ai/agentic-engineering/context-engineering) — The deliberate selection and maintenance of instructions, knowledge, tools, state, examples, and artifacts within a finite model attention budget. - [Agent execution substrate](https://aisdlc.ai/agentic-engineering/execution-substrate) — The isolated, stateful environment in which agents observe and act, including compute, filesystem, browser, network, credentials, resource limits, and session lifecycle. - [Evidence engineering](https://aisdlc.ai/agentic-engineering/evidence-engineering) — The design of versioned, queryable evidence linking requirements, decisions, implementations, tests, evaluations, approvals, deployments, runtime signals, and lifecycle actions. ## Sources and further study - [Anthropic — Effective context engineering for AI agents](https://www.anthropic.com/engineering/effective-context-engineering-for-ai-agents) — A working model for treating model-visible context as a finite resource that must be selected and maintained. **Use:** First-party case study. **Limitation:** This first-party account documents one organization, product, or implementation context and should not be generalized without local evidence. - [Anthropic — Scaling Managed Agents: Decoupling the brain from the hands](https://www.anthropic.com/engineering/managed-agents) — An architecture separating durable sessions and environment state from changing models and harnesses. **Use:** First-party case study. **Limitation:** This first-party account documents one organization, product, or implementation context and should not be generalized without local evidence. - [OWASP GenAI Security Project — Memory Is a Feature. It Is Also an Attack Surface](https://genai.owasp.org/2026/05/13/memory-is-a-feature-it-is-also-an-attack-surface/) — A focused account of why persistent agent memory requires integrity, provenance, and poisoning defenses. **Use:** First-party case study. **Limitation:** This first-party account documents one organization, product, or implementation context and should not be generalized without local evidence. --- This library synthesizes cited research, standards, official documentation, and clearly attributed practitioner perspectives. Maturity describes the state of a concept—not vendor endorsement, production readiness, or permission to deploy. Benchmarks and demonstrations do not replace use-case evaluation, governed controls, independent verification, or named human release authority.