# agent-memory - Doramagic AI Context Pack > Purpose: pre-work context for the user's host AI. This pack does not prove that the project has been installed, run, or validated. ## Project - canonical_name: `neo4j-labs/agent-memory` - capability: A graph-native memory system for AI agents and context graphs. Store conversations, build knowledge graphs, and let your agents learn from their own reasoning\u2009—\u2009all backed by Neo4j. - expected_user_outcome: A graph-native memory system for AI agents and context graphs. Store conversations, build knowledge graphs, and let your agents learn from their own reasoning\u2009—\u2009all backed by Neo4j. ## Operating Boundaries - Do not claim that the project has been installed, run, called through an API, or used on local files unless separate evidence proves it. - Project facts must come from repo evidence, Claim Graph, or explicit source references. - When a capability is not verified, mark it as unverified instead of completing it as fact. - publish_status: `publishable` - blocking_gaps: none --- ## Doramagic Context Augmentation The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints. ## Human Manual Outline Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph. Host AI hard rules: - Do not treat page titles, section order, summaries, or importance values as factual project evidence. - When explaining the Human Manual outline, state that it is only a reading route or salience signal. - Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph. - **Overview and System Architecture**: importance `high` - source_paths: README.md, src/neo4j_agent_memory/__init__.py, src/neo4j_agent_memory/config/settings.py, src/neo4j_agent_memory/core/memory.py, src/neo4j_agent_memory/core/protocols.py - **SDK Usage and Memory Operations**: importance `high` - source_paths: src/neo4j_agent_memory/__init__.py, src/neo4j_agent_memory/config/settings.py, src/neo4j_agent_memory/memory/short_term.py, src/neo4j_agent_memory/memory/long_term.py, src/neo4j_agent_memory/memory/reasoning.py - **Extraction, Enrichment, and Entity Resolution**: importance `high` - source_paths: src/neo4j_agent_memory/extraction/base.py, src/neo4j_agent_memory/extraction/factory.py, src/neo4j_agent_memory/extraction/pipeline.py, src/neo4j_agent_memory/extraction/llm_extractor.py, src/neo4j_agent_memory/extraction/gliner_extractor.py - **MCP Server, Framework Integrations, CLI, and Deployment**: importance `high` - source_paths: src/neo4j_agent_memory/mcp/server.py, src/neo4j_agent_memory/mcp/_tools.py, src/neo4j_agent_memory/mcp/_resources.py, src/neo4j_agent_memory/mcp/_prompts.py, src/neo4j_agent_memory/mcp/_preference_detector.py ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `f29ae8dd86221bd5ace94d6c39711c38b0a6cdde` - inspected_files: `uv.lock`, `pyproject.toml`, `README.md`, `docs/vercel.json`, `docs/antora-playbook.yml`, `docs/antora.yml`, `docs/package-lock.json`, `docs/package.json`, `docs/assets/images/diagrams/diagram-descriptions.md`, `examples/basic_usage.py`, `examples/entity_resolution.py`, `examples/langchain_agent.py`, `examples/enrichment_example.py`, `examples/README.md`, `examples/pydantic_ai_agent.py`, `examples/domain-schemas/podcast_transcripts.py`, `examples/domain-schemas/news_articles.py`, `examples/domain-schemas/business_reports.py`, `examples/domain-schemas/legal_documents.py`, `examples/domain-schemas/scientific_papers.py` Host AI hard rules: - Without repo_clone_verified=true, do not claim that the source code has been read. - Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts. - Without quick_start_verified=true, do not claim that the Quick Start path has run successfully. ## Doramagic Pitfall Constraints These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes. ### Constraint 1: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/neo4j-labs/agent-memory/issues/138 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/neo4j-labs/agent-memory/issues/42 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: Maintenance risk requires verification - Trigger: Project evidence flags a maintenance risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/neo4j-labs/agent-memory/issues/137 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/neo4j-labs/agent-memory/issues/131 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: Configuration risk requires verification - Trigger: Project evidence flags a configuration risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: capability.host_targets | https://github.com/neo4j-labs/agent-memory - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: Configuration risk requires verification - Trigger: Project evidence flags a configuration risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/neo4j-labs/agent-memory/issues/129 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: Configuration risk requires verification - Trigger: Project evidence flags a configuration risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/neo4j-labs/agent-memory/issues/141 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 8: Configuration risk requires verification - Trigger: Project evidence flags a configuration risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/neo4j-labs/agent-memory/issues/140 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 9: Capability evidence risk requires verification - Trigger: README/documentation is current enough for a first validation pass. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: capability.assumptions | https://github.com/neo4j-labs/agent-memory - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 10: Maintenance risk requires verification - Trigger: Project evidence flags a maintenance risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/neo4j-labs/agent-memory/issues/128 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.