# memU - 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: `NevaMind-AI/memU` - capability: From workspace to agent memory - expected_user_outcome: From workspace to agent memory ## 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. - **System Overview & Architecture**: importance `high` - source_paths: README.md, src/memu/app/service.py, src/memu/app/settings.py, src/memu/workflow/pipeline.py, src/memu/workflow/runner.py - **Storage Backends & Data Model**: importance `high` - source_paths: src/memu/database/factory.py, src/memu/database/interfaces.py, src/memu/database/models.py, src/memu/database/state.py, src/memu/database/inmemory/repo.py - **LLM, Embedding & VLM Providers and Routing**: importance `high` - source_paths: src/memu/llm/gateway.py, src/memu/llm/wrapper.py, src/memu/llm/openai_client.py, src/memu/llm/anthropic_client.py, src/memu/llm/lazyllm_client.py - **Memorize & Retrieve Workflows, Preprocessing and Prompts**: importance `high` - source_paths: src/memu/app/memorize.py, src/memu/app/retrieve.py, src/memu/app/crud.py, src/memu/preprocess/base.py, src/memu/preprocess/conversation.py ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `6824b541be4274bf856b2f80e960163273d62227` - inspected_files: `README.md`, `pyproject.toml`, `uv.lock`, `docs/HACKATHON_ISSUE_DRAFT.md`, `docs/HACKATHON_MAD_COMBOS.md`, `docs/adr/0001-workflow-pipeline-architecture.md`, `docs/adr/0002-pluggable-storage-and-vector-strategy.md`, `docs/adr/0003-user-scope-in-data-model.md`, `docs/adr/0004-workspace-memorize-and-memory-file-system.md`, `docs/adr/README.md`, `docs/architecture.md`, `docs/integrations/grok.md`, `docs/langgraph_integration.md`, `docs/providers/grok.md`, `docs/sealos-devbox-guide.md`, `docs/sealos_use_case.md`, `docs/sqlite.md`, `docs/tutorials/getting_started.md`, `examples/example_1_conversation_memory.py`, `examples/example_2_skill_extraction.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: 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/NevaMind-AI/memU/issues/428 - 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/NevaMind-AI/memU/issues/354 - 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/NevaMind-AI/memU/issues/382 - 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: capability.host_targets | https://github.com/NevaMind-AI/memU - 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/NevaMind-AI/memU - 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: 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/NevaMind-AI/memU - 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: downstream_validation.risk_items | https://github.com/NevaMind-AI/memU - 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: risks.scoring_risks | https://github.com/NevaMind-AI/memU - 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/NevaMind-AI/memU - 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/NevaMind-AI/memU - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.