# memanto - 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: `moorcheh-ai/memanto`
- capability: Memory that AI Agents Love!
- expected_user_outcome: Memory that AI Agents Love!

## 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 & System Architecture**: importance `high`
  - source_paths: README.md, memanto/app/clients/backend.py, memanto/app/clients/onprem.py, memanto/app/core.py, memanto/app/constants.py
- **CLI Commands, TypeScript SDK & Agent Integrations**: importance `high`
  - source_paths: memanto/cli/main.py, memanto/cli/commands/core.py, memanto/cli/commands/memory.py, memanto/cli/commands/memory_mgmt.py, memanto/cli/commands/connect.py
- **Memory Model, Backend Services & REST API (v2)**: importance `high`
  - source_paths: memanto/app/main.py, memanto/app/routes/sessions.py, memanto/app/routes/memory.py, memanto/app/models/session.py, memanto/app/services/agent_service.py
- **Deployment, Configuration & Operations**: importance `medium`
  - source_paths: memanto/app/config.py, memanto/cli/config/manager.py, memanto/cli/commands/config_cmd.py, memanto/cli/commands/schedule.py, memanto/cli/migrate/runner.py

## Repo Inspection Evidence

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `61c7656cf5bd06a2c617cc2c7532f80c87e2f220`
- inspected_files: `Dockerfile`, `README.md`, `docker-compose.yml`, `pyproject.toml`, `docs/AGENT_INTEGRATION_GUIDE.md`, `docs/AGENT_MEMORY_BEST_PRACTICES.md`, `docs/CLI_INSTALLATION.md`, `docs/CLI_USER_GUIDE.md`, `docs/DEPLOYMENT_GUIDE.md`, `docs/GETTING_STARTED.md`, `docs/HYBRID_TIMELINE_GUIDE.md`, `docs/SESSION_ARCHITECTURE.md`, `docs/TIMELINE_VISUALIZATION_EXAMPLES.md`, `docs/V2_QUICK_START.md`, `examples/claudecode-skills-memanto/lifecycle-hooks/.claude-plugin/plugin.json`, `examples/claudecode-skills-memanto/lifecycle-hooks/README.md`, `examples/claudecode-skills-memanto/lifecycle-hooks/demo_session_1.py`, `examples/claudecode-skills-memanto/lifecycle-hooks/demo_session_2.py`, `examples/claudecode-skills-memanto/lifecycle-hooks/demo_session_3.py`, `examples/claudecode-skills-memanto/lifecycle-hooks/hooks/__init__.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: 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/moorcheh-ai/memanto/issues/639
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 2: 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/moorcheh-ai/memanto/issues/770
- 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: capability.host_targets | https://github.com/moorcheh-ai/memanto
- 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/moorcheh-ai/memanto
- 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/moorcheh-ai/memanto
- 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/moorcheh-ai/memanto
- 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/moorcheh-ai/memanto
- 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/moorcheh-ai/memanto/issues/1329
- 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/moorcheh-ai/memanto
- 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/moorcheh-ai/memanto
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.