# Memori - 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: `MemoriLabs/Memori` - capability: Memori is agent-native memory infrastructure. A LLM-agnostic layer that turns agent execution and conversation into structured, persistent state for production systems. - expected_user_outcome: Memori is agent-native memory infrastructure. A LLM-agnostic layer that turns agent execution and conversation into structured, persistent state for production systems. ## 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. - **Memori Overview, Installation, and Quickstart**: importance `high` - source_paths: README.md, memori/__init__.py, memori/_config.py, memori/__main__.py, memori-ts/src/index.ts - **System Architecture: Python, TypeScript, and the Rust Core**: importance `high` - source_paths: core/src/lib.rs, core/Cargo.toml, core/docs/architecture.md, core/bindings/python/src/lib.rs, core/bindings/node/src/lib.rs - **LLM Provider Adapters, Framework Integrations, and Advanced Augmentation**: importance `high` - source_paths: memori/llm/__init__.py, memori/llm/_base.py, memori/llm/_providers.py, memori/llm/_registry.py, memori/llm/_utils.py - **BYODB Storage Layer, CLI, and Operations**: importance `high` - source_paths: memori/storage/__init__.py, memori/storage/_base.py, memori/storage/_builder.py, memori/storage/_connection.py, memori/storage/_manager.py ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `56600c525ba3046354c17a7663dca06a813a0bb5` - inspected_files: `Dockerfile`, `README.md`, `docker-compose.yml`, `pyproject.toml`, `uv.lock`, `docs/memori-byodb/concepts/advanced-augmentation.mdx`, `docs/memori-byodb/concepts/agent-trace-execution.mdx`, `docs/memori-byodb/concepts/architecture.mdx`, `docs/memori-byodb/concepts/async-patterns.mdx`, `docs/memori-byodb/concepts/cli-quickstart.mdx`, `docs/memori-byodb/concepts/how-memory-works.mdx`, `docs/memori-byodb/concepts/knowledge-graph.mdx`, `docs/memori-byodb/concepts/multi-user-support.mdx`, `docs/memori-byodb/contribute/development-setup.mdx`, `docs/memori-byodb/contribute/overview.mdx`, `docs/memori-byodb/dashboard/api-keys.mdx`, `docs/memori-byodb/databases/cockroachdb.mdx`, `docs/memori-byodb/databases/mongodb.mdx`, `docs/memori-byodb/databases/mysql.mdx`, `docs/memori-byodb/databases/oracle.mdx` 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/MemoriLabs/Memori - 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/MemoriLabs/Memori - 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/MemoriLabs/Memori - 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/MemoriLabs/Memori - 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: 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/MemoriLabs/Memori/issues/590 - 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: 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/MemoriLabs/Memori - 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: 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/MemoriLabs/Memori - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.