# zep - 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: `getzep/zep` - capability: Zep | Examples, Integrations, & More - expected_user_outcome: Zep | Examples, Integrations, & More ## 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. - **Repository Overview & Examples Catalog**: importance `high` - source_paths: README.md, CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md, .env.example - **Agent Framework Integrations**: importance `high` - source_paths: integrations/README.md, integrations/CLAUDE.md, integrations/crewai/python/CHANGELOG.md, integrations/crewai/python/src/zep_crewai/memory.py, integrations/crewai/python/src/zep_crewai/graph_storage.py - **Zep MCP Server & Claude/Cursor Plugin**: importance `high` - source_paths: mcp/zep-mcp-server/README.md, mcp/zep-mcp-server/cmd/server/main.go, mcp/zep-mcp-server/internal/server/server.go, mcp/zep-mcp-server/internal/server/tools.go, mcp/zep-mcp-server/internal/handlers/search.go - **Evaluation Harness & Ontology**: importance `medium` - source_paths: zep-eval-harness/README.md, zep-eval-harness/zep_evaluate.py, zep-eval-harness/zep_chunk_documents.py, zep-eval-harness/zep_ingest_documents.py, zep-eval-harness/zep_ingest_users.py ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `9b3545ee3d6f375f90972edc599db922094acfa5` - inspected_files: `README.md`, `pyproject.toml`, `examples/go/chunking-example/README.md`, `examples/python/advanced.py`, `examples/python/agent-memory-full-example/README.md`, `examples/python/agent-memory-full-example/agents.py`, `examples/python/agent-memory-full-example/pre-populate-memories/conversations.json`, `examples/python/agent-memory-full-example/pre-populate-memories/populate-memories.py`, `examples/python/agent-memory-full-example/pre-populate-memories/user_data.json`, `examples/python/agent-memory-full-example/ui.py`, `examples/python/chat_history/chat_history_shoe_purchase.py`, `examples/python/chat_history/memory.py`, `examples/python/chunking-example/README.md`, `examples/python/chunking-example/chunk_and_ingest.py`, `examples/python/claude-prompt-caching-example/README.md`, `examples/python/claude-prompt-caching-example/agent.py`, `examples/python/claude-prompt-caching-example/benchmark.py`, `examples/python/claude-prompt-caching-example/chat.py`, `examples/python/claude-prompt-caching-example/ingest.py`, `examples/python/claude-prompt-caching-example/pricing.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: 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/getzep/zep - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: 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: evidence.maintainer_signals | https://github.com/getzep/zep - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: Security or permission risk requires verification - Trigger: no_demo - 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: downstream_validation.risk_items | https://github.com/getzep/zep - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Security or permission risk requires verification - Trigger: no_demo - 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: risks.scoring_risks | https://github.com/getzep/zep - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: Maintenance risk requires verification - Trigger: issue_or_pr_quality=unknown。 - 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: evidence.maintainer_signals | https://github.com/getzep/zep - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: Maintenance risk requires verification - Trigger: release_recency=unknown。 - 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: evidence.maintainer_signals | https://github.com/getzep/zep - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.