# memobase - 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: `memodb-io/memobase` - capability: User Profile-Based Long-Term Memory for AI Chatbot Applications. - expected_user_outcome: User Profile-Based Long-Term Memory for AI Chatbot Applications. ## 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. - **Memobase Overview and System Architecture**: importance `high` - source_paths: readme.md, src/server/api/readme.md, src/server/api/DEVELOPMENT.md, src/server/readme.md, ROADMAP.md - **Backend Server: FastAPI, Controllers, and Data Models**: importance `high` - source_paths: src/server/api/api.py, src/server/api/memobase_server/api_layer/user.py, src/server/api/memobase_server/api_layer/blob.py, src/server/api/memobase_server/api_layer/buffer.py, src/server/api/memobase_server/api_layer/profile.py - **Client SDKs: Python, TypeScript, and Go**: importance `high` - source_paths: src/client/memobase/__init__.py, src/client/memobase/core/entry.py, src/client/memobase/core/async_entry.py, src/client/memobase/core/user.py, src/client/memobase/core/blob.py - **MCP Server, Deployment, and Customization**: importance `medium` - source_paths: src/mcp/README.md, src/mcp/src/main.py, src/mcp/Dockerfile, src/mcp/pyproject.toml, src/server/docker-compose.yml ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `358c16bbc6d687937d79bc2f984a11c3be8da901` - inspected_files: `readme.md`, `requirements.txt`, `docs/experiments/900-chats/readme.md`, `docs/experiments/900-chats/run.py`, `docs/experiments/900-chats/run_mem0.py`, `docs/experiments/900-chats/sharegpt_test_7uOhOjo.json`, `docs/experiments/chat_sessions/chats/mock_user/1.json`, `docs/experiments/chat_sessions/chats/mock_user/2.json`, `docs/experiments/chat_sessions/extract.py`, `docs/experiments/chat_sessions/readme.md`, `docs/experiments/locomo-benchmark/README.md`, `docs/experiments/locomo-benchmark/compute_p95_latency.py`, `docs/experiments/locomo-benchmark/evals.py`, `docs/experiments/locomo-benchmark/fixture/memobase/memobase_eval_0503_3000.json`, `docs/experiments/locomo-benchmark/fixture/memobase/memobase_eval_0710_3000.json`, `docs/experiments/locomo-benchmark/fixture/memobase/results_0503_3000.json`, `docs/experiments/locomo-benchmark/fixture/memobase/results_0710_3000.json`, `docs/experiments/locomo-benchmark/generate_scores.py`, `docs/experiments/locomo-benchmark/metrics/llm_judge.py`, `docs/experiments/locomo-benchmark/metrics/utils.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/memodb-io/memobase/issues/155 - 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/memodb-io/memobase/issues/158 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: 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/memodb-io/memobase/issues/76 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: 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/memodb-io/memobase/issues/159 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: 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/memodb-io/memobase - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: Runtime risk requires verification - Trigger: Project evidence flags a runtime 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/memodb-io/memobase/issues/137 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: 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/memodb-io/memobase - 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: 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/memodb-io/memobase - 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: 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/memodb-io/memobase - 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/memodb-io/memobase/issues/153 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.