# MemOS - 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: `MemTensor/MemOS` - capability: Self-evolving memory OS for LLM & AI Agents: ultra-persistent memory, hybrid-retrieval, and cross-task skill reuse, with 35.24% token savings - expected_user_outcome: Self-evolving memory OS for LLM & AI Agents: ultra-persistent memory, hybrid-retrieval, and cross-task skill reuse, with 35.24% token savings ## 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. - **MemOS Overview and Architecture**: importance `high` - source_paths: README.md, src/memos/mem_os/main.py, src/memos/mem_os/core.py, src/memos/mem_cube/base.py, docs/en/open_source/home/overview.md - **Core Memory System: MemCube, Textual/Activation/Parametric Memory, Scheduler and Retrieval**: importance `high` - source_paths: src/memos/mem_cube/general.py, src/memos/memories/textual/base.py, src/memos/memories/textual/tree.py, src/memos/memories/textual/preference.py, src/memos/memories/activation/kv.py - **Local Plugins: memos-local-plugin and memos-local-openclaw for Hermes/OpenClaw**: importance `high` - source_paths: apps/memos-local-plugin/README.md, apps/memos-local-plugin/ARCHITECTURE.md, apps/memos-local-plugin/core/index.ts, apps/memos-local-plugin/core/pipeline/memory-core.ts, apps/memos-local-plugin/core/memory/l2/l2.ts - **Deployment, Configuration, Evaluation, and Operations**: importance `medium` - source_paths: docker/docker-compose.yml, docker/Dockerfile, docker/.env.example, docker/.env.example-full, src/memos/api/config.py ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `a4f1b5be94b3ed1b78438375176320b04fa3cc44` - inspected_files: `Dockerfile`, `README.md`, `pyproject.toml`, `uv.lock`, `docs/cn/open_source/best_practice/common_errors_solutions.md`, `docs/cn/open_source/best_practice/mcp_for_cozespace_and_tools.md`, `docs/cn/open_source/best_practice/memory_structure_design.md`, `docs/cn/open_source/best_practice/network_workarounds.md`, `docs/cn/open_source/best_practice/performance_tuning.md`, `docs/cn/open_source/contribution/commit_guidelines.md`, `docs/cn/open_source/contribution/development_workflow.md`, `docs/cn/open_source/contribution/overview.md`, `docs/cn/open_source/contribution/setting_up.md`, `docs/cn/open_source/contribution/writing_docs.md`, `docs/cn/open_source/contribution/writing_tests.md`, `docs/cn/open_source/evaluation/openai_memory_locomo_eval_guide.md`, `docs/cn/open_source/evaluation/overview.md`, `docs/cn/open_source/getting_started/examples.md`, `docs/cn/open_source/getting_started/installation.md`, `docs/cn/open_source/getting_started/rest_api_server.md` 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/MemTensor/MemOS/issues/1950 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: 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/MemTensor/MemOS - 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/MemTensor/MemOS/issues/1966 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: 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/MemTensor/MemOS - 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: 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/MemTensor/MemOS - 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: 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/MemTensor/MemOS - 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: 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/MemTensor/MemOS - 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/MemTensor/MemOS/issues/1961 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 9: 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/MemTensor/MemOS - 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: 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/MemTensor/MemOS - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.