# mnemo - 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: `arttttt/mnemo` - capability: Local, on-demand memory for AI coding agents (MCP). Strictly offline; built for 10+ agents on a 16GB machine. - expected_user_outcome: Local, on-demand memory for AI coding agents (MCP). Strictly offline; built for 10+ agents on a 16GB machine. ## 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, Principles & System Architecture**: importance `high` - source_paths: README.md, docs/01-overview.md, docs/03-architecture.md, src/mnemo/domain/memory.py, src/mnemo/infrastructure/composition.py - **Memory Domain Model & MCP Tool Surface**: importance `high` - source_paths: src/mnemo/domain/memory.py, src/mnemo/domain/memory_type.py, src/mnemo/domain/scope.py, src/mnemo/domain/project.py, src/mnemo/domain/constants.py - **Recall Pipeline, Embedders & LLM Kit Integration**: importance `high` - source_paths: src/mnemo/application/recall/builder.py, src/mnemo/application/recall/bundle.py, src/mnemo/application/recall/gather_stage.py, src/mnemo/application/recall/rerank_stage.py, src/mnemo/application/recall/assemble_stage.py - **Deployment, Configuration, Storage & Client Wiring**: importance `medium` - source_paths: src/mnemo/infrastructure/config.py, src/mnemo/infrastructure/logging_config.py, src/mnemo/adapters/mcp/launcher.py, src/mnemo/adapters/mcp/service.py, src/mnemo/adapters/mcp/idle_monitor.py ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `6a336e93a436bdf66f7f70e1f099bfcb75658d18` - inspected_files: `README.md`, `pyproject.toml`, `uv.lock`, `docs/01-overview.md`, `docs/02-requirements.md`, `docs/03-architecture.md`, `docs/04-data-model.md`, `docs/05-mcp-api.md`, `docs/06-models.md`, `docs/07-lifecycle-and-ram.md`, `docs/08-consolidation.md`, `docs/09-tech-stack.md`, `docs/10-roadmap.md`, `docs/11-alternatives-research.md`, `docs/12-testing.md`, `docs/13-usage.md`, `docs/adr/0001-storage-engine.md`, `docs/research/embedder-benchmark.md`, `docs/research/generator-benchmark.md`, `docs/roadmap/phase-0-skeleton.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: 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/arttttt/mnemo - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: 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/arttttt/mnemo - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: 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/arttttt/mnemo - 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: downstream_validation.risk_items | https://github.com/arttttt/mnemo - 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: 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/arttttt/mnemo - 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/arttttt/mnemo - 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/arttttt/mnemo - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.