# cognee - 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: `topoteretes/cognee` - capability: Cognee is the open-source AI memory platform for agents. Give your AI agents persistent long-term memory across sessions with a self-hosted knowledge graph engine. - expected_user_outcome: Cognee is the open-source AI memory platform for agents. Give your AI agents persistent long-term memory across sessions with a self-hosted knowledge graph engine. ## 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, Core Operations, and System Architecture**: importance `high` - source_paths: cognee/__init__.py, cognee/__main__.py, cognee/api/v1/remember/remember.py, cognee/api/v1/recall/recall.py, cognee/api/v1/forget/forget.py - **Multi-User Access Control, Tenants, and Datasets**: importance `high` - source_paths: cognee/modules/users/models/ACL.py, cognee/modules/users/models/Permission.py, cognee/modules/users/models/Tenant.py, cognee/modules/users/models/Role.py, cognee/modules/users/models/User.py - **Retrieval System, Search Modes, and Evaluation**: importance `high` - source_paths: cognee/api/v1/search/search.py, cognee/modules/search/types/SearchType.py, cognee/modules/search/methods/search.py, cognee/modules/search/operations/select_search_type.py, cognee/modules/search/models/Query.py - **Deployment, LLM and Database Configuration, and Extensibility**: importance `high` - source_paths: cognee/api/v1/config/config.py, cognee/api/v1/serve/serve.py, cognee/api/v1/serve/management_api.py, cognee/infrastructure/llm/config.py, cognee/infrastructure/llm/structured_output_framework/litellm_instructor/llm/get_llm_client.py ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `dcf9f4eed7dac9cace60bdc75b36ed33213176d2` - inspected_files: `Dockerfile`, `README.md`, `docker-compose.yml`, `pyproject.toml`, `uv.lock`, `examples/README.md`, `examples/configurations/database_examples/ladybug_graph_database_configuration.py`, `examples/configurations/database_examples/neo4j_graph_database_configuration.py`, `examples/configurations/database_examples/neptune_analytics_aws_database_configuration.py`, `examples/configurations/database_examples/pgvector_postgres_vector_database_configuration.py`, `examples/configurations/permissions_example/data_access_control_example.py`, `examples/configurations/permissions_example/tenant_role_constraints_example.py`, `examples/configurations/permissions_example/tenant_role_setup_example.py`, `examples/configurations/permissions_example/user_permissions_and_access_control_example.py`, `examples/custom_pipelines/agentic_reasoning_procurement_example.py`, `examples/custom_pipelines/custom_cognify_pipeline_example.py`, `examples/custom_pipelines/dynamic_steps_resume_analysis_hr_example.py`, `examples/custom_pipelines/memify_coding_agent_rule_extraction_example.py`, `examples/custom_pipelines/organizational_hierarchy/data/companies.json`, `examples/custom_pipelines/organizational_hierarchy/data/people.json` 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/topoteretes/cognee/issues/2913 - 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/topoteretes/cognee/issues/3079 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: 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/topoteretes/cognee/issues/3154 - 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: Developers should check this security_permissions risk before relying on the project: cognee.add silently creates a new owner-scoped dataset when non-owner uses an existing dataset name - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: cognee.add silently creates a new owner-scoped dataset when non-owner uses an existing dataset name. Context: Observed when using python - Why it matters: Developers may expose sensitive permissions or credentials: cognee.add silently creates a new owner-scoped dataset when non-owner uses an existing dataset name - Evidence: failure_mode_cluster:github_issue | https://github.com/topoteretes/cognee/issues/2846 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: Security or permission risk requires verification - Trigger: Developers should check this security_permissions risk before relying on the project: cognee.search ignores ACL when resolving dataset by name for non-owners - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: cognee.search ignores ACL when resolving dataset by name for non-owners. Context: Observed when using python - Why it matters: Developers may expose sensitive permissions or credentials: cognee.search ignores ACL when resolving dataset by name for non-owners - Evidence: failure_mode_cluster:github_issue | https://github.com/topoteretes/cognee/issues/2845 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: Security or permission risk requires verification - Trigger: Developers should check this security_permissions risk before relying on the project: cognify pipeline silently skips data added by non-owner users - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: cognify pipeline silently skips data added by non-owner users. Context: Observed when using node, python - Why it matters: Developers may expose sensitive permissions or credentials: cognify pipeline silently skips data added by non-owner users - Evidence: failure_mode_cluster:github_issue | https://github.com/topoteretes/cognee/issues/2847 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: Security or permission risk requires verification - Trigger: Project evidence flags a security or permission 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/topoteretes/cognee/issues/3004 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 8: Security or permission risk requires verification - Trigger: Project evidence flags a security or permission 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/topoteretes/cognee/issues/2846 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 9: Security or permission risk requires verification - Trigger: Project evidence flags a security or permission 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/topoteretes/cognee/issues/2845 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 10: Security or permission risk requires verification - Trigger: Project evidence flags a security or permission 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/topoteretes/cognee/issues/2847 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.