# local-memory-mcp - Doramagic AI Context Pack

> Positioning: a pre-install experience and judgment asset. It helps the host AI get off to a good start, but it does not mean the project has already been installed, run, or validated.

## Sufficiency Principle

- **Sufficiency over compression**: The AI Context Pack should be sufficient for the host AI to understand the project's value, capability boundaries, entrypoints, risks, and evidence sources before starting work; it may be layered, but it does not aim for the shortest possible summary.
- **Compression policy**: Compress only noise and duplication, never context that affects judgment or the quality of the work.

## How the Host AI Should Use This

You are reading the AI Context Pack that Doramagic compiled for local-memory-mcp. Treat it as pre-work context: help the user understand who it fits, what it can do, how to start, what must be verified after install, and where the risks are. Do not claim that you have already installed, run, or executed the target project.

## Claim Consumption Rules

- **Fact source**: Repo Evidence + Claim/Evidence Graph; the Human Wiki only supplies salience, terminology, and narrative structure.
- **Minimum status for a fact**: `supported`
- `supported`: May be used as a project fact, but the answer must cite the claim_id and evidence path.
- `weak`: Usable only as a low-confidence lead; the user must be asked to keep verifying.
- `inferred`: Usable only for risk notes or open questions; must not be packaged as a project fact.
- `unverified`: Must not be used as fact; state clearly that evidence is insufficient.
- `contradicted`: Must show the conflicting sources and must not force a single version on the user's behalf.

## Who It Fits Best

- **Developers already using host AIs such as Claude/Codex/Cursor/Gemini**: The README or plugin config mentions multiple host AIs. Evidence: `README.md` Claim: `clm_0002` supported 0.86

## What It Can Do

- **Command-Line Startup or Install Flow** (Verify after install): The project documentation contains runnable commands; real use requires running them in a local or host environment. Evidence: `README.md` Claim: `clm_0001` supported 0.86

## How to Start

- `npm install -g @vheins/local-memory-mcp` Evidence: `README.md` Claim: `clm_0003` supported 0.86

## Continue-or-Stop Decision Card

- **Current recommendation**: Trial role matching first
- **Why**: This project is more of a role library; the core risk is picking the wrong role or treating role copy as execution capability. Trial role matching with Prompt Preview first, then decide whether to sandbox-import it.

### 30-Second Read

- **What to do now**: Trial role matching first
- **Minimum safe next step**: Trial role matching with Prompt Preview first; import in isolation only once satisfied
- **Do not trust yet**: Role quality and task fit cannot be trusted directly.
- **Continuing will touch**: Role selection bias, Command execution, Host AI configuration

### What You Can Trust Now

- **Target-audience signal: Developers already using host AIs such as Claude/Codex/Cursor/Gemini** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `README.md` Claim: `clm_0002` supported 0.86
- **Capability exists: Command-Line Startup or Install Flow** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `README.md` Claim: `clm_0001` supported 0.86
- **There are Quick Start / install-command signals** (supported): You can trust that the docs mention a startup or install entrypoint; do not run it directly in your primary environment because of that. Evidence: `README.md` Claim: `clm_0003` supported 0.86

### What You Cannot Trust Yet

- **Role quality and task fit cannot be trusted directly.** (unverified): A role library proves there are many roles; it does not prove each one fits your specific task or that a role produces high-quality results.
- **Do not treat role copy as real execution capability.** (unverified): Before install you can only judge whether the role description and task profile match; you cannot prove it can complete the task inside the host AI.
- **Real output quality cannot be trusted before install.** (unverified): Prompt Preview can only show how it guides you; it cannot prove result quality in the real project.
- **Host AI version compatibility cannot be trusted before install.** (unverified): Host loading rules and version differences across Claude, Cursor, Codex, Gemini, and others must be verified in a real environment.
- **That it will not pollute your existing host AI's behavior cannot be trusted directly.** (inferred): Skill, plugin, and AGENTS/CLAUDE/GEMINI instructions may change the host AI's default behavior. Evidence: `GEMINI.md`
- **Safe rollback cannot be assumed by default.** (unverified): Unless the project clearly provides uninstall and recovery instructions, verify in an isolated environment first.
- **After a real install, is it compatible with the user's current host AI version?** (unverified): Compatibility can only be verified in the actual host environment.
- **Does the project's output quality meet the user's specific task?** (unverified): The pre-install preview can only show flow and boundaries; it cannot replace real evaluation.

### What Continuing Will Touch

- **Role selection bias**: The user's judgment about which expert role should handle the task. Why: Picking the wrong role makes the AI answer from the wrong expert perspective, wasting time or misleading decisions.
- **Command execution**: Package managers, network downloads, the local plugin directory, project config, or the user's home directory. Why: Running the very first command can already change your environment; decide whether it is worth running first. Evidence: `README.md`
- **Host AI configuration**: The plugin, Skill, or rule-loading config of hosts like Claude/Codex/Cursor/Gemini/OpenCode. Why: Host configuration changes how the AI works afterward and may conflict with the user's existing rules. Evidence: `GEMINI.md`
- **Local environment or project files**: Install results, plugin caches, project config, or local dependency directories. Why: The write scope and rollback path cannot be proven before install and need isolated verification. Evidence: `README.md`
- **Host AI context**: The AI Context Pack, Prompt Preview, Skill routing, risk rules, and project facts. Why: Importing context affects the host AI's later judgment, so avoid packaging unverified items as facts.

### Minimum Safe Next Steps

- **Run Prompt Preview first**: Use an interactive trial to verify the task profile and role match first; do not import the whole role library up front. (applies when: Applies to any project, especially when output quality is unknown.)
- **Trial-install only in an isolated directory or a test account**: Avoid letting install commands pollute your primary host AI, real projects, or home directory. (applies when: When there are signals of command execution, plugin config, or local writes.)
- **Back up your host AI configuration first**: Skill, plugin, and rule files may change the default behavior of Claude/Cursor/Codex. (applies when: When there is a plugin manifest, a Skill, or a host rule entrypoint.)
- **After install, verify just one minimal task**: Verify loading, compatibility, output quality, and rollback first, then decide whether to use it deeply. (applies when: When moving from a trial into a real workflow.)

### Exit Plan

- **Preserve the pre-install state**: Record the original host config and project state so you can later judge whether it is recoverable.
- **Be ready to remove the host plugin / Skill / rule entrypoint**: If behavior is off after the trial install, you can restore the host AI to its pre-trial state.
- **Keep a record of the original role selection**: If output goes off-topic, you can return to the task-profiling stage and reselect a role instead of pushing on with the wrong one.
- **Record the install commands and written paths**: Without clear uninstall instructions, you at least need to know which directories or configs to clean up manually.
- **If there is no rollback path, do not enter your primary environment**: No rollback is a blocker before continuing; do not proceed on trust or luck.

## What Can Only Be Previewed

- Explain who the project fits and what it can do
- Demonstrate a typical conversation flow based on project docs
- Help the user decide whether it is worth installing or researching further

## What Must Be Verified After Install

- Actually installing the Skill, plugin, or CLI
- Running scripts, modifying local files, or accessing external services
- Verifying real output quality, performance, and compatibility

## Boundary & Risk Decision Card

- **Mistaking the pre-install preview for a real run**: The user may overestimate how much configuration, permission, and compatibility verification the project has already done. Mitigation: Clearly separate prompt_preview_can_do from runtime_required. Claim: `clm_0004` inferred 0.45
- **Command execution will modify the local environment**: Install commands may write to the user's home directory, the host plugin directory, or project configuration. Mitigation: Run in an isolated environment or a test account first. Evidence: `README.md` Claim: `clm_0005` supported 0.86
- **To confirm**: After a real install, is it compatible with the user's current host AI version?. Why: Compatibility can only be verified in the actual host environment.
- **To confirm**: Does the project's output quality meet the user's specific task?. Why: The pre-install preview can only show flow and boundaries; it cannot replace real evaluation.
- **To confirm**: Do the install commands require network access, permissions, or global writes?. Why: This affects install risk in both enterprise and personal environments.

## Pre-Work Working Context

### Loading Order

- First read how_to_use.host_ai_instruction to establish the boundaries of this pre-install judgment asset.
- Read claim_graph_summary to confirm facts come from the Claim/Evidence Graph, not the Human Wiki narrative.
- Then read intended_users, capabilities, and quick_start_candidates to judge whether the user is a match.
- When you need to carry out a concrete task, check role_skill_index first, then evidence_index.
- For real install, file modification, network access, performance, or compatibility questions, turn to risk_card and boundaries.runtime_required.

### Task Routes

- **Command-Line Startup or Install Flow**: State that this is an after-install capability first, then give a pre-install checklist. Boundary: Must be verified after a real install or run. Evidence: `README.md` Claim: `clm_0001` supported 0.86

### Context Scale

- Total files: 440
- Important-file coverage: 40/440
- Evidence index entries: 73
- Role / Skill entries: 35

### Handling Insufficient Evidence

- **missing_evidence**: State that evidence is insufficient and ask the user for the target file, a README section, or after-install verification records; do not fill in facts.
- **out_of_scope_request**: State that the task is beyond the current AI Context Pack's evidence scope and suggest the user check the Human Manual or verify after a real install.
- **runtime_request**: Provide a pre-install checklist and command sources, but do not run commands for the user or claim they have been run.
- **source_conflict**: Show the conflicting sources side by side, mark them as unverified, and do not force a single version.

## Prompt Recipes

### Fit assessment

- Goal: Judge whether this project fits the user's current task.
- Expected output: A fit conclusion, key reasons, evidence citations, what can be previewed before install, what must be verified after install, and a next-step recommendation.

```text
Based on the AI Context Pack for local-memory-mcp, ask me 3 necessary questions first, then judge whether it fits my task. The answer must cover: who it fits, what it can do, what it cannot do, whether it is worth installing, and where the evidence comes from. Every project fact must cite evidence_refs, source_paths, or a claim_id.
```

### Pre-install experience

- Goal: Let the user feel the core workflow before installing, while avoiding packaging the preview as real capability or a marketing promise.
- Expected output: An experience script with boundary labels, an after-install verification checklist, and a cautious recommendation; with no real-run promises or strong marketing language.

```text
Treat local-memory-mcp as a pre-install experience asset, not an already-installed tool or a real runtime environment.

Output exactly four parts:
1. Ask me 3 necessary questions first.
2. Give an "experience script": use the three labels [Previewable before install], [Must verify after install], and [Insufficient evidence] to show how it might guide the workflow.
3. Give an after-install verification checklist: list which capabilities can only be confirmed after a real install, real host loading, and a real project run.
4. Give a cautious recommendation: only "worth researching/trialing further", "add information before deciding", or "not recommended to continue"; do not endorse the project.

Hard boundaries:
- Do not claim you have installed, run, executed tests, modified files, or produced real results.
- Do not write promise-like phrasing such as "auto-adapts", "guarantees passing", "perfect fit", or "strongly recommend installing".
- If you describe how it works after install, you must use a conditional such as "if installed successfully and the host loads the Skill correctly, it might...".
- The experience script may only be written as "example lines / hypothetical flow": use "might ask / might suggest / might show", not "has written, has generated, has passed, is running, is generating".
- Prompt Preview does not hand out install commands; if the user is ready to trial, only prompt them to read Quick Start and the Risk Card first and to verify in an isolated environment.
- Every project fact must come from a supported claim, evidence_refs, or source_paths; inferred/unverified items can only be risks or open questions.

```

### Role / Skill selection

- Goal: Pick the best-matching asset from the project's roles or Skills.
- Expected output: A list of candidate roles or Skills, each with an applicable scenario, evidence paths, risk boundary, and whether after-install verification is needed.

```text
Read role_skill_index and recommend 3-5 of the most relevant roles or Skills for my target task. For each recommendation, state the applicable scenario, likely output, risk boundary, and evidence_refs.
```

### Risk pre-check

- Goal: Identify environment, permission, rule-conflict, and quality risks before installing or adopting.
- Expected output: A checklist of environment, permission, dependency, license, host-conflict, quality risk, and unknown items.

```text
Based on risk_card, boundaries, and quick_start_candidates, give me a pre-install risk pre-check list. Do not run commands for me; only explain what I should check, why, and what impact a failure would have.
```

### Host AI kickoff instruction

- Goal: Turn the project context into a host AI instruction for the start of a conversation.
- Expected output: A pre-work instruction with clear boundaries and clear evidence citations, suitable to copy to a host AI.

```text
Based on the AI Context Pack for local-memory-mcp, generate a pre-work instruction I can paste to my host AI. This instruction must obey not_runtime=true and must not claim the project has been installed, run, or produced real results.
```

## Role / Skill Index

- Indexed 35 role / Skill / project-doc entries.

- **@vheins/local-memory-mcp** (project_doc): ! npm version https://img.shields.io/npm/v/@vheins/local-memory-mcp.svg https://www.npmjs.com/package/@vheins/local-memory-mcp ! npm downloads https://img.shields.io/npm/dm/@vheins/local-memory-mcp.svg https://www.npmjs.com/package/@vheins/local-memory-mcp ! npm total downloads https://img.shields.io/npm/dt/@vheins/local-memory-mcp.svg https://www.npmjs.com/package/@vheins/local-memory-mcp ! License: MIT https://img… Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `README.md`
- **Application Documentation** (project_doc): This directory contains the complete documentation for the local-memory-mcp application — an MCP Model Context Protocol server with persistent memory, task orchestration, knowledge graph, and codebase intelligence. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `.agents/documents/application/README.md`
- **API Documentation Catalog** (project_doc): Index of all API specification documents across the application modules. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `.agents/documents/application/api/README.md`
- **API Module: Codebase Index** (project_doc): - Design — API Contracts ../../../design/codebase-index/api-contracts.md - Design — Domain Model ../../../design/codebase-index/domain.md - Design — Database Schema ../../../design/codebase-index/schema.md - Testing Module ../../testing/codebase-index/README.md Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `.agents/documents/application/api/codebase-index/README.md`
- **Module Catalog** (project_doc): Index of all application modules with links to their documentation. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `.agents/documents/application/modules/README.md`
- **Module: Codebase Index** (project_doc): Purpose : Parse, index, and query source code structure using tree-sitter AST parsing, enabling agents to understand codebases without reading every file. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `.agents/documents/application/modules/codebase-index/README.md`
- **Testing Documentation Catalog** (project_doc): Index of all testing documents across application modules. Tests follow the project's 4-layer concern model: Database → Service → State → Integration . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `.agents/documents/application/testing/README.md`
- **Testing Module: Codebase Index** (project_doc): - Design — API Contracts ../../../design/codebase-index/api-contracts.md - Design — Domain Model ../../../design/codebase-index/domain.md - API Module ../api/codebase-index/README.md Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `.agents/documents/application/testing/codebase-index/README.md`
- **Git Repository Rules** (project_doc): - MANDATORY: Every commit message MUST include the Title and Summary of the task being worked on derived from the active MCP task . - This ensures full traceability between code changes and the project task system. - Propose a draft commit message that is clear, concise, and focused on "why" rather than just "what", followed by the task metadata. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `GEMINI.md`
- **Contributing Guidelines** (project_doc): Thank you for your interest in contributing to the MCP Local Memory Service! Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `CONTRIBUTING.md`
- **Codebase Index API Reference** (project_doc): Architecture decision context: See ADR-002: Codebase Index Architecture ../../.agents/documents/design/decisions/adr-002-codebase-index.md for design rationale, including the choice of web-tree-sitter WASM bindings, SQLite storage strategy, incremental indexing with SHA-256 checksums, and single-pass parsing for Phase 1.0. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/api/codebase-index.md`
- **Auto-Start Dashboard in IDE** (project_doc): Guide for configuring your favorite IDE to automatically run the Memory Dashboard every time a project is opened. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/en/auto-start-dashboard.md`
- **Integration with Claude Code** (project_doc): Complete guide for connecting MCP Local Memory Service to Claude Code https://code.claude.com — Anthropic's CLI AI agent. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/en/claude-code-integration.md`
- **Integration with Codex OpenAI** (project_doc): Complete guide for connecting MCP Local Memory Service to Codex https://developers.openai.com/codex — OpenAI's AI coding agent. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/en/codex-integration.md`
- **Web Dashboard: Global Command Center + Repo Workspace** (project_doc): Web Dashboard: Global Command Center + Repo Workspace Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/en/dashboard-guide.md`
- **Core Features & V2 Enhancements** (project_doc): This project is more than just text storage; it is a "brain" system for AI agents designed for long-term stability and project consistency. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/en/features.md`
- **Getting Started & Setup** (project_doc): This guide provides instructions for bringing the MCP Local Memory Service to life from two critical perspectives. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/en/getting-started.md`
- **Hybrid Search: How the System "Thinks"** (project_doc): Hybrid Search: How the System "Thinks" Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/en/hybrid-search.md`
- **Integration with Kiro** (project_doc): Complete guide for connecting MCP Local Memory Service to Kiro https://kiro.dev — AI-powered IDE. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/en/kiro-integration.md`
- **MCP Protocol Reference v2025-11-25** (project_doc): This document details the technical interface exposed by the local-memory-mcp server for AI Agents, fully compliant with the Model Context Protocol MCP Specification v2025-11-25 https://modelcontextprotocol.io/specification/2025-11-25/server . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/en/mcp-concepts.md`
- **Tool Reference & Usage Guide** (project_doc): A practical guide to the tools this MCP server exposes to AI agents. Each tool is grouped by domain with usage patterns and examples. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/en/tools-reference.md`
- **Troubleshooting Guide** (project_doc): Common issues when installing or running the MCP Local Memory Service. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/en/troubleshooting.md`
- **Codebase Index** (project_doc): The Codebase Index feature allows AI agents to search for functions, classes, interfaces, types, enums, and other structural entities within project source code. Instead of reading files sequentially to understand a codebase, agents can query a pre-built index that provides structured symbol information on demand. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/features/codebase-index.md`
- **Auto-Start Dashboard di IDE** (project_doc): Panduan mengkonfigurasi IDE favorit kamu untuk menjalankan Memory Dashboard secara otomatis setiap kali project dibuka. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/id/auto-start-dashboard.md`
- **Integrasi dengan Claude Code** (project_doc): Panduan lengkap menghubungkan MCP Local Memory Service ke Claude Code https://code.claude.com — CLI AI agent dari Anthropic. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/id/claude-code-integration.md`
- **Integrasi dengan Codex OpenAI** (project_doc): Panduan lengkap menghubungkan MCP Local Memory Service ke Codex https://developers.openai.com/codex — AI coding agent dari OpenAI. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/id/codex-integration.md`
- **Dasbor Web: Pusat Komando Global + Ruang Kerja Repo** (project_doc): Dasbor Web: Pusat Komando Global + Ruang Kerja Repo Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/id/dashboard-guide.md`
- **Fitur Inti & Peningkatan V2** (project_doc): Proyek ini lebih dari sekadar penyimpanan teks; ini adalah sistem "otak" untuk agen AI yang dirancang untuk stabilitas jangka panjang dan konsistensi proyek. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/id/features.md`
- **Memulai & Pengaturan** (project_doc): Panduan ini memberikan petunjuk untuk menghidupkan MCP Local Memory Service dari dua sudut pandang penting. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/id/getting-started.md`
- **Pencarian Hibrida: Bagaimana Sistem "Berpikir"** (project_doc): Pencarian Hibrida: Bagaimana Sistem "Berpikir" Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/id/hybrid-search.md`
- **Integrasi dengan Kiro** (project_doc): Panduan lengkap menghubungkan MCP Local Memory Service ke Kiro https://kiro.dev — AI-powered IDE. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/id/kiro-integration.md`
- **Referensi Protokol MCP v2025-11-25** (project_doc): Dokumen ini merinci antarmuka teknis yang diekspos oleh server local-memory-mcp untuk Agen AI, sepenuhnya sesuai dengan Model Context Protocol MCP Specification v2025-11-25 https://modelcontextprotocol.io/specification/2025-11-25/server . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/id/mcp-concepts.md`
- **Referensi Alat & Panduan Penggunaan** (project_doc): Referensi Alat & Panduan Penggunaan Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/id/tools-reference.md`
- **Panduan Pemecahan Masalah** (project_doc): Masalah umum saat menginstal atau menjalankan MCP Local Memory Service. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/id/troubleshooting.md`
- **Codebase Index — Operations Guide** (project_doc): Architecture decision context: See ADR-002: Codebase Index Architecture ../../.agents/documents/design/decisions/adr-002-codebase-index.md for design rationale. Feature overview: Codebase Index Feature Guide ../features/codebase-index.md API Reference: Codebase Index API ../api/codebase-index.md Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/operations/codebase-index.md`

## Evidence Index

- Indexed 73 evidence entries.

- **@vheins/local-memory-mcp** (documentation): ! npm version https://img.shields.io/npm/v/@vheins/local-memory-mcp.svg https://www.npmjs.com/package/@vheins/local-memory-mcp ! npm downloads https://img.shields.io/npm/dm/@vheins/local-memory-mcp.svg https://www.npmjs.com/package/@vheins/local-memory-mcp ! npm total downloads https://img.shields.io/npm/dt/@vheins/local-memory-mcp.svg https://www.npmjs.com/package/@vheins/local-memory-mcp ! License: MIT https://img.shields.io/badge/License-MIT-yellow.svg https://opensource.org/licenses/MIT Evidence: `README.md`
- **Application Documentation** (documentation): This directory contains the complete documentation for the local-memory-mcp application — an MCP Model Context Protocol server with persistent memory, task orchestration, knowledge graph, and codebase intelligence. Evidence: `.agents/documents/application/README.md`
- **API Documentation Catalog** (documentation): Index of all API specification documents across the application modules. Evidence: `.agents/documents/application/api/README.md`
- **API Module: Codebase Index** (documentation): - Design — API Contracts ../../../design/codebase-index/api-contracts.md - Design — Domain Model ../../../design/codebase-index/domain.md - Design — Database Schema ../../../design/codebase-index/schema.md - Testing Module ../../testing/codebase-index/README.md Evidence: `.agents/documents/application/api/codebase-index/README.md`
- **Module Catalog** (documentation): Index of all application modules with links to their documentation. Evidence: `.agents/documents/application/modules/README.md`
- **Module: Codebase Index** (documentation): Purpose : Parse, index, and query source code structure using tree-sitter AST parsing, enabling agents to understand codebases without reading every file. Evidence: `.agents/documents/application/modules/codebase-index/README.md`
- **Package** (package_manifest): { "name": "@vheins/local-memory-mcp", "version": "0.23.0", "description": "MCP Local Memory Service for coding copilot agents", "mcpName": "io.github.vheins/local-memory-mcp", "type": "module", "main": "dist/server.js", "bin": { "local-memory-mcp": "bin/mcp-memory-server.js", "mcp-memory-server": "bin/mcp-memory-server.js", "mcp-memory-dashboard": "bin/mcp-memory-dashboard.js" }, "files": "dist", "bin", "storage/.gitkeep", "dist/prompts/definitions", "dist/prompts/server" , "repository": { "type": "git", "url": "git+https://github.com/vheins/local-memory-mcp.git" }, "bugs": { "url": "https://github.com/vheins/local-memory-mcp/issues" }, "homepage": "https://github.com/vheins/local-memory-mc… Evidence: `package.json`
- **Package** (package_manifest): { "dependencies": { "marked": "^18.0.2", "svelte": "^5.56.8" } } Evidence: `src/dashboard/ui/package.json`
- **Testing Documentation Catalog** (documentation): Index of all testing documents across application modules. Tests follow the project's 4-layer concern model: Database → Service → State → Integration . Evidence: `.agents/documents/application/testing/README.md`
- **Testing Module: Codebase Index** (documentation): - Design — API Contracts ../../../design/codebase-index/api-contracts.md - Design — Domain Model ../../../design/codebase-index/domain.md - API Module ../api/codebase-index/README.md Evidence: `.agents/documents/application/testing/codebase-index/README.md`
- **Git Repository Rules** (documentation): - MANDATORY: Every commit message MUST include the Title and Summary of the task being worked on derived from the active MCP task . - This ensures full traceability between code changes and the project task system. - Propose a draft commit message that is clear, concise, and focused on "why" rather than just "what", followed by the task metadata. Evidence: `GEMINI.md`
- **Contributing Guidelines** (documentation): Thank you for your interest in contributing to the MCP Local Memory Service! Evidence: `CONTRIBUTING.md`
- **Codebase Index API Reference** (documentation): Architecture decision context: See ADR-002: Codebase Index Architecture ../../.agents/documents/design/decisions/adr-002-codebase-index.md for design rationale, including the choice of web-tree-sitter WASM bindings, SQLite storage strategy, incremental indexing with SHA-256 checksums, and single-pass parsing for Phase 1.0. Evidence: `docs/api/codebase-index.md`
- **Auto-Start Dashboard in IDE** (documentation): Guide for configuring your favorite IDE to automatically run the Memory Dashboard every time a project is opened. Evidence: `docs/en/auto-start-dashboard.md`
- **Integration with Claude Code** (documentation): Complete guide for connecting MCP Local Memory Service to Claude Code https://code.claude.com — Anthropic's CLI AI agent. Evidence: `docs/en/claude-code-integration.md`
- **Integration with Codex OpenAI** (documentation): Complete guide for connecting MCP Local Memory Service to Codex https://developers.openai.com/codex — OpenAI's AI coding agent. Evidence: `docs/en/codex-integration.md`
- **Web Dashboard: Global Command Center + Repo Workspace** (documentation): Web Dashboard: Global Command Center + Repo Workspace Evidence: `docs/en/dashboard-guide.md`
- **Core Features & V2 Enhancements** (documentation): This project is more than just text storage; it is a "brain" system for AI agents designed for long-term stability and project consistency. Evidence: `docs/en/features.md`
- **Getting Started & Setup** (documentation): This guide provides instructions for bringing the MCP Local Memory Service to life from two critical perspectives. Evidence: `docs/en/getting-started.md`
- **Hybrid Search: How the System "Thinks"** (documentation): Hybrid Search: How the System "Thinks" Evidence: `docs/en/hybrid-search.md`
- **Integration with Kiro** (documentation): Complete guide for connecting MCP Local Memory Service to Kiro https://kiro.dev — AI-powered IDE. Evidence: `docs/en/kiro-integration.md`
- **MCP Protocol Reference v2025-11-25** (documentation): This document details the technical interface exposed by the local-memory-mcp server for AI Agents, fully compliant with the Model Context Protocol MCP Specification v2025-11-25 https://modelcontextprotocol.io/specification/2025-11-25/server . Evidence: `docs/en/mcp-concepts.md`
- **Tool Reference & Usage Guide** (documentation): A practical guide to the tools this MCP server exposes to AI agents. Each tool is grouped by domain with usage patterns and examples. Evidence: `docs/en/tools-reference.md`
- **Troubleshooting Guide** (documentation): Common issues when installing or running the MCP Local Memory Service. Evidence: `docs/en/troubleshooting.md`
- **Codebase Index** (documentation): The Codebase Index feature allows AI agents to search for functions, classes, interfaces, types, enums, and other structural entities within project source code. Instead of reading files sequentially to understand a codebase, agents can query a pre-built index that provides structured symbol information on demand. Evidence: `docs/features/codebase-index.md`
- **Auto-Start Dashboard di IDE** (documentation): Panduan mengkonfigurasi IDE favorit kamu untuk menjalankan Memory Dashboard secara otomatis setiap kali project dibuka. Evidence: `docs/id/auto-start-dashboard.md`
- **Integrasi dengan Claude Code** (documentation): Panduan lengkap menghubungkan MCP Local Memory Service ke Claude Code https://code.claude.com — CLI AI agent dari Anthropic. Evidence: `docs/id/claude-code-integration.md`
- **Integrasi dengan Codex OpenAI** (documentation): Panduan lengkap menghubungkan MCP Local Memory Service ke Codex https://developers.openai.com/codex — AI coding agent dari OpenAI. Evidence: `docs/id/codex-integration.md`
- **Dasbor Web: Pusat Komando Global + Ruang Kerja Repo** (documentation): Dasbor Web: Pusat Komando Global + Ruang Kerja Repo Evidence: `docs/id/dashboard-guide.md`
- **Fitur Inti & Peningkatan V2** (documentation): Proyek ini lebih dari sekadar penyimpanan teks; ini adalah sistem "otak" untuk agen AI yang dirancang untuk stabilitas jangka panjang dan konsistensi proyek. Evidence: `docs/id/features.md`
- **Memulai & Pengaturan** (documentation): Panduan ini memberikan petunjuk untuk menghidupkan MCP Local Memory Service dari dua sudut pandang penting. Evidence: `docs/id/getting-started.md`
- **Pencarian Hibrida: Bagaimana Sistem "Berpikir"** (documentation): Pencarian Hibrida: Bagaimana Sistem "Berpikir" Evidence: `docs/id/hybrid-search.md`
- **Integrasi dengan Kiro** (documentation): Panduan lengkap menghubungkan MCP Local Memory Service ke Kiro https://kiro.dev — AI-powered IDE. Evidence: `docs/id/kiro-integration.md`
- **Referensi Protokol MCP v2025-11-25** (documentation): Dokumen ini merinci antarmuka teknis yang diekspos oleh server local-memory-mcp untuk Agen AI, sepenuhnya sesuai dengan Model Context Protocol MCP Specification v2025-11-25 https://modelcontextprotocol.io/specification/2025-11-25/server . Evidence: `docs/id/mcp-concepts.md`
- **Referensi Alat & Panduan Penggunaan** (documentation): Referensi Alat & Panduan Penggunaan Evidence: `docs/id/tools-reference.md`
- **Panduan Pemecahan Masalah** (documentation): Masalah umum saat menginstal atau menjalankan MCP Local Memory Service. Evidence: `docs/id/troubleshooting.md`
- **Codebase Index — Operations Guide** (documentation): Architecture decision context: See ADR-002: Codebase Index Architecture ../../.agents/documents/design/decisions/adr-002-codebase-index.md for design rationale. Feature overview: Codebase Index Feature Guide ../features/codebase-index.md API Reference: Codebase Index API ../api/codebase-index.md Evidence: `docs/operations/codebase-index.md`
- **Kgcontroller** (source_file): import express from "express"; import { db } from "../lib/context"; import { jsonApiRes, jsonApiError, getAttributes } from "../lib/jsonApi"; ⋮---- export class KGController ⋮---- static async listEntities req: express.Request, res: express.Response ⋮---- static async getEntity req: express.Request, res: express.Response ⋮---- static async listRelations req: express.Request, res: express.Response ⋮---- static async listGraph req: express.Request, res: express.Response ⋮---- static async createEntity req: express.Request, res: express.Response ⋮---- static async deleteEntity req: express.Request, res: express.Response ⋮---- static async createRelation req: express.Request, res: express.Respo… Evidence: `src/dashboard/controllers/KGController.ts`
- **Memoriescontroller** (source_file): import express from "express"; import { randomUUID } from "crypto"; import { db } from "../lib/context"; import { jsonApiRes, jsonApiError, getAttributes } from "../lib/jsonApi"; import type { MemoryType, MemoryEntry } from "../../mcp/types/index"; import type { IdParams, MemoryListQuery } from "../../mcp/interfaces/index"; ⋮---- export class MemoriesController ⋮---- static async list req: express.Request, res: express.Response ⋮---- static async get req: express.Request, res: express.Response ⋮---- static async create req: express.Request, res: express.Response ⋮---- static async update req: express.Request, res: express.Response ⋮---- static async delete req: express.Request, res: express… Evidence: `src/dashboard/controllers/MemoriesController.ts`
- **Systemcontroller** (source_file): import express from "express"; import fs from "fs"; import path from "path"; import { fileURLToPath } from "url"; import { db, mcpClient, startTime } from "../lib/context"; import { jsonApiRes, jsonApiError, getAttributes } from "../lib/jsonApi"; import { condenseRecentActions } from "../lib/helpers"; import { parseRepoInput } from "../../mcp/utils/normalize"; import { TOOL DEFINITIONS } from "../../mcp/tools/tool-definitions"; import { listResources } from "../../mcp/resources/index"; import { PROMPTS } from "../../mcp/prompts/registry"; import type { RecentAction } from "../ui/src/lib/interfaces/common"; import { handleHandoffList, handleHandoffCreate, handleHandoffUpdate, handleTaskClaim… Evidence: `src/dashboard/controllers/SystemController.ts`
- **Taskscontroller** (source_file): import express from "express"; import { randomUUID } from "crypto"; import { db, mcpClient } from "../lib/context.js"; import { jsonApiRes, jsonApiError, getAttributes } from "../lib/jsonApi.js"; import type { Task } from "../../mcp/types/index.js"; import type { IdParams, TaskListQuery } from "../../mcp/interfaces/index.js"; ⋮---- export class TasksController ⋮---- static async list req: express.Request, res: express.Response ⋮---- static async get req: express.Request, res: express.Response ⋮---- static async getByCode req: express.Request, res: express.Response ⋮---- static async create req: express.Request, res: express.Response ⋮---- static async update req: express.Request, res: expre… Evidence: `src/dashboard/controllers/TasksController.ts`
- **Unifiedgraphcontroller** (source_file): import express from "express"; import { db } from "../lib/context"; import { jsonApiRes, jsonApiError } from "../lib/jsonApi"; import { parseRepoInput } from "../../mcp/utils/normalize"; ⋮---- export class UnifiedGraphController ⋮---- static async getGraph req: express.Request, res: express.Response Evidence: `src/dashboard/controllers/UnifiedGraphController.ts`
- **Index** (source_file): import { Router } from "express"; import systemRoutes from "./system.routes"; import memoryRoutes from "./memory.routes"; import taskRoutes from "./task.routes"; import standardRoutes from "./standard.routes"; import coordinationRoutes from "./coordination.routes"; import kgRoutes from "./kg.routes"; import codebaseRoutes from "./codebase.routes"; import unifiedGraphRoutes from "./unified-graph.routes"; Evidence: `src/dashboard/routes/index.ts`
- **Server** (source_file): import express from "express"; import path from "path"; import fs from "fs"; import { fileURLToPath } from "url"; import { db, mcpClient, logger } from "./lib/context"; import { addLogSink, createFileSink } from "../mcp/utils/logger"; import routes from "./routes/index"; ⋮---- function authMiddleware req: express.Request, res: express.Response, next: express.NextFunction : void ⋮---- function getStaticRoot ⋮---- function startServer Evidence: `src/dashboard/server.ts`
- **Usedetailhandoff** (source_file): import { get } from "svelte/store"; import { api } from "../api"; import { copyToClipboard } from "../utils"; import type { Handoff } from "../stores"; import type { DetailState, DetailUpdate } from "./useDetailTypes"; import { INITIAL HANDOFF FORM } from "./useDetailTypes"; ⋮---- export function createDetailHandoff subscribe: run: s: DetailState = void = = void, update: DetailUpdate ⋮---- function setHandoff handoff: Handoff null ⋮---- function initNewHandoff repoName: string ⋮---- function parseHandoffContext value: string : Record ⋮---- async function createHandoff onCreated: = void, repo: string ⋮---- async function updateHandoffStatus status: string, onUpdated: = void ⋮---- async funct… Evidence: `src/dashboard/ui/src/lib/composables/useDetailHandoff.ts`
- **Usedetailstandard** (source_file): import { get } from "svelte/store"; import { api } from "../api"; import { copyToClipboard } from "../utils"; import { confirmDelete, alertError } from "../confirm"; import type { CodingStandard } from "../stores"; import type { DetailState, DetailUpdate } from "./useDetailTypes"; import { INITIAL STANDARD FORM as INIT STD } from "./useDetailTypes"; ⋮---- function splitList value: string ⋮---- function parseMetadata value: string : Record null ⋮---- function stringifyMetadata value: Record ⋮---- export function createDetailStandard subscribe: run: s: DetailState = void = = void, update: DetailUpdate ⋮---- function setStandard standard: CodingStandard null ⋮---- function startStandardEdit ⋮-… Evidence: `src/dashboard/ui/src/lib/composables/useDetailStandard.ts`
- **Usememory** (source_file): import { writable, get } from "svelte/store"; import { api } from "../api"; import { currentRepo } from "../stores"; import { confirmDelete } from "../confirm"; import type { Memory } from "../stores"; ⋮---- export interface MemoryForm { title: string; type: string; content: string; importance: number; tags: string; agent: string; model: string; } ⋮---- export interface UseMemoryProps { onSaved: mem: Memory = void; onDeleted: id: string = void; onClose: = void; } ⋮---- export function createMemoryHandler props: UseMemoryProps ⋮---- function reset memory: Memory null ⋮---- function parseTags raw: string : string ⋮---- async function save ⋮---- async function deleteMemory Evidence: `src/dashboard/ui/src/lib/composables/useMemory.ts`
- **Memory** (source_file): export interface Memory { id: string; title: string; content: string; type: string; importance: number; scope: { repo: string }; tags?: string ; created at: string; updated at: string; ttl days?: number; hit count?: number; last accessed at?: string; is global?: boolean; status?: string; metadata?: Record ; agent?: string; model?: string; } Evidence: `src/dashboard/ui/src/lib/interfaces/memory.ts`
- **Task** (source_file): export interface TaskCoordination { active claim count: number; active claim agent: string null; active claim role: string null; active claim claimed at: string null; pending handoff count: number; pending handoff id: string null; pending handoff summary: string null; pending handoff to agent: string null; pending handoff created at: string null; } ⋮---- export interface Task { id: string; repo: string; task code: string; phase: string; title: string; description: string null; status: string; priority: number; agent?: string; role?: string; created at: string; updated at: string; finished at?: string null; in progress at?: string null; est tokens?: number; tags?: string ; metadata?: Record… Evidence: `src/dashboard/ui/src/lib/interfaces/task.ts`
- **Cli** (source_file): import process from "node:process"; import { performance } from "node:perf hooks"; import { SQLiteStore } from "../storage/sqlite.js"; import { TreeSitterParserPool } from "./parser/parser-pool.js"; import { createCodebaseIndexService } from "./services/indexing-service.js"; import type { IndexResult } from "./services/indexing-service.js"; ⋮---- export interface CliIndexArgs { repo: string; path: string; includeGlobs: string ; excludeGlobs: string ; } ⋮---- type ParseResult = CliIndexArgs { error: string }; ⋮---- export function parseIndexArgs argv: string : ParseResult ⋮---- function log message: string : void ⋮---- export async function runCliIndex : Promise Evidence: `src/mcp/codebase-index/cli.ts`
- **Parser Pool** (source_file): import fs from "node:fs"; import path from "node:path"; import { fileURLToPath } from "node:url"; import { performance } from "node:perf hooks"; import { Parser, Language } from "web-tree-sitter"; import type { ParseResult, ParserPool, LanguageVisitor } from "./language-visitor.js"; import { TypeScriptVisitor } from "./typescript-visitor.js"; import { GoVisitor } from "./visitors/go-visitor.js"; import { PythonVisitor } from "./visitors/python-visitor.js"; import { PhpVisitor } from "./visitors/php-visitor.js"; import { DartVisitor } from "./visitors/dart-visitor.js"; import { RustVisitor } from "./visitors/rust-visitor.js"; import { JavaVisitor } from "./visitors/java-visitor.js"; import {… Evidence: `src/mcp/codebase-index/parser/parser-pool.ts`
- **Architecture Service** (source_file): import type { CodebaseFile } from "../../types/codebase-file"; import type { CodebaseSymbol } from "../../types/codebase-symbol"; ⋮---- export interface DirectoryNode { path: string; name: string; type: "file" "directory"; children?: DirectoryNode ; symbolCounts?: Record ; hasMoreFiles?: boolean; } ⋮---- export interface ArchitectureSummary { totalFiles: number; totalSymbols: number; languageBreakdown: Record ; topLevelExports: CodebaseSymbol ; } ⋮---- export interface ArchitectureResult { root: DirectoryNode; summary: ArchitectureSummary; } ⋮---- interface DirTree { name: string; path: string; files: CodebaseFile ; subdirs: Map ; } ⋮---- function createDirTree name: string, path: string :… Evidence: `src/mcp/codebase-index/services/architecture-service.ts`
- **File Discovery** (source_file): import fs from "node:fs"; import path from "node:path"; import { performance } from "node:perf hooks"; import fg from "fast-glob"; import ignoreLib from "ignore"; import { logger } from "../../utils/logger.js"; import type { DiscoveredFile, DiscoverFilesResult, DiscoveryError, FileDiscoveryOptions } from "../types/index.js"; ⋮---- function detectLanguage filePath: string : string null ⋮---- function findGitignoreFiles root: string : string ⋮---- function transformGitignorePatterns content: string, scopePrefix: string : string ⋮---- if pattern === "" continue; // bare "!" — skip ⋮---- // git determines anchoring by presence of a non-trailing / // or a leading / which we strip before scoping… Evidence: `src/mcp/codebase-index/services/file-discovery.ts`
- **Indexing Service** (source_file): import fs from "node:fs"; import path from "node:path"; import os from "node:os"; import crypto from "node:crypto"; import { performance } from "node:perf hooks"; import { discoverFiles } from "./file-discovery.js"; import type { ParserPool } from "../parser/index.js"; import type { ParseResult } from "../parser/language-visitor.js"; import type { SQLiteStore } from "../../storage/sqlite.js"; import type { CodebaseFileInsert } from "../../types/codebase-file.js"; import type { CodebaseSymbolInsert } from "../../types/codebase-symbol.js"; import type { DiscoveredFile } from "../types/index.js"; import { logger } from "../../utils/logger.js"; import { RecoverableError, FatalError } from "../t… Evidence: `src/mcp/codebase-index/services/indexing-service.ts`
- **Symbol Ranking** (source_file): import type { CodebaseSymbol } from "../../types/codebase-symbol"; ⋮---- export enum RankTier { Exact = 1, CamelCase = 2, Prefix = 3, Substring = 4, FTS5 = 5 } ⋮---- export interface RankedSymbol { symbol: CodebaseSymbol; rankTier: RankTier; score: number; } ⋮---- export interface SymbolFilter { kind?: string ; repo?: string; filePath?: string; exportedOnly?: boolean; } ⋮---- export function rankSymbols symbols: CodebaseSymbol , query: string : RankedSymbol ⋮---- // Assign each symbol to its best-matching tier ⋮---- // Flatten tiers and score within each ⋮---- / Filter symbols by optional criteria. All filters are AND-combined. / export function filterSymbols symbols: CodebaseSymbol , filte… Evidence: `src/mcp/codebase-index/services/symbol-ranking.ts`
- **Trace Service** (source_file): import type { CodebaseSymbol } from "../../types/codebase-symbol"; ⋮---- export interface TraceResult { symbol: CodebaseSymbol; definition: { file: string; line: number; column: number; }; references: TraceReference ; exportChain: { exported: boolean; defaultExport: boolean; }; disambiguation?: CodebaseSymbol ; } ⋮---- export interface TraceReference { filePath: string; startLine: number; startCol: number; context: string; } ⋮---- export class SymbolNotFoundError extends Error ⋮---- constructor name: string, repo?: string ⋮---- export class AmbiguousSymbolError extends Error ⋮---- constructor name: string, disambiguation: CodebaseSymbol , repo?: string ⋮---- export function traceSymbol name… Evidence: `src/mcp/codebase-index/services/trace-service.ts`
- **Index** (source_file): export interface DiscoveredFile { path: string; absolutePath: string; language: string; sizeBytes: number; } ⋮---- export interface FileDiscoveryOptions { projectPath: string; includeGlobs?: string ; excludeGlobs?: string ; respectGitignore?: boolean; maxFiles?: number; } ⋮---- export interface DiscoverFilesResult { files: DiscoveredFile ; totalFiles: number; supportedFiles: number; skippedFiles: number; skippedByExtension: number; skippedByGitignore: number; durationMs: number; errors: DiscoveryError ; } ⋮---- export interface DiscoveryError { path: string; error: string; } Evidence: `src/mcp/codebase-index/types/index.ts`
- **Handoff** (source_file): import { randomUUID } from "crypto"; import { BaseEntity } from "../storage/base"; import { Handoff, HandoffRow, Claim, ClaimRow } from "../types"; ⋮---- export class HandoffEntity extends BaseEntity ⋮---- private rowToHandoff row: HandoffRow : Handoff ⋮---- private rowToClaim row: ClaimRow : Claim ⋮---- createHandoff params: { owner: string; repo: string; from agent: string; to agent?: string null; task id?: string null; summary: string; context?: Record ; expires at?: string null; } : Handoff ⋮---- listHandoffs params: { owner: string; repo: string; status?: Handoff "status" ; to agent?: string; from agent?: string; limit?: number; offset?: number; } : Handoff ⋮---- getHandoffById id: str… Evidence: `src/mcp/entities/handoff.ts`
- **Memory.Archive** (source_file): import { BaseEntity } from "../storage/base"; ⋮---- export class MemoryArchiveEntity extends BaseEntity ⋮---- bulkDeleteMemories ids: string : number ⋮---- archiveExpiredMemories force: boolean = false : number ⋮---- archiveLowScoreMemories force: boolean = false : number Evidence: `src/mcp/entities/memory.archive.ts`
- **Memory** (source_file): import { BaseEntity } from "../storage/base"; import { MemoryEntry, MemoryRow, MemoryType } from "../types/index"; import { CountResult, TypeCountResult } from "../types/common"; ⋮---- export class MemoryEntity extends BaseEntity ⋮---- insert entry: MemoryEntry : void ⋮---- private mergeStructuredData metadata: Record , structuredData?: Record : Record ⋮---- update id: string, updates: Partial : void ⋮---- delete id: string : void ⋮---- getById id: string : MemoryEntry null ⋮---- getByCode code: string, owner?: string, repo?: string : MemoryEntry null ⋮---- getByIdWithStats id: string : MemoryEntry & ⋮---- getByIds ids: string , options: ⋮---- getStats owner?: string, repo?: string : ⋮----… Evidence: `src/mcp/entities/memory.ts`
- The remaining 13 evidence entries are in `AI_CONTEXT_PACK.json` or `EVIDENCE_INDEX.json`.

## Rules the Host AI Must Follow

- **Treat this asset as pre-work context, not a runtime environment.**: The AI Context Pack contains only an evidence-backed understanding of the project, not the project's executable state. Evidence: `README.md`, `.agents/documents/application/README.md`, `.agents/documents/application/api/README.md`
- **When answering the user, distinguish what can be previewed from what can only be verified after install.**: The consumer value of the pre-install experience comes from reducing bad installs and misjudgments, not from pretending to be a real run. Evidence: `README.md`, `.agents/documents/application/README.md`, `.agents/documents/application/api/README.md`

## Questions the User Should Answer First

- Which host AI or local environment do you plan to use it in?
- Do you just want to experience the workflow first, or are you ready to actually install?
- What matters most to you: install cost, output quality, or conflicts with your existing rules?

## Acceptance Checks

- Every capability claim can be traced back to a file path in evidence_refs.
- AI_CONTEXT_PACK.md does not package previews as a real run.
- The user can understand who it fits, what it can do, how to start, and the risk boundaries within 3 minutes.

---

## 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 and System Architecture**: importance `high`
  - source_paths: README.md, package.json, bin/mcp-memory-server.js, bin/mcp-memory-dashboard.js, src/mcp/server.ts
- **Codebase Index and Source Code Search**: importance `high`
  - source_paths: src/mcp/codebase-index/cli.ts, src/mcp/codebase-index/services/file-discovery.ts, src/mcp/codebase-index/services/indexing-service.ts, src/mcp/codebase-index/services/architecture-service.ts, src/mcp/codebase-index/services/trace-service.ts
- **Memory Management, Semantic Search, and Knowledge Graph**: importance `high`
  - source_paths: src/mcp/entities/memory.ts, src/mcp/entities/standard.ts, src/mcp/entities/memory.vector.ts, src/mcp/entities/memory.archive.ts, src/mcp/entities/task.ts
- **Dashboard UI, Performance, and Operations**: importance `high`
  - source_paths: src/dashboard/server.ts, src/dashboard/controllers/SystemController.ts, src/dashboard/controllers/MemoriesController.ts, src/dashboard/controllers/TasksController.ts, src/dashboard/controllers/KGController.ts

## Repo Inspection Evidence

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `93995053c6851c0185d6e20cdeed390af92659c5`
- inspected_files: `README.md`, `package.json`, `docs/api/codebase-index.md`, `docs/en/auto-start-dashboard.md`, `docs/en/claude-code-integration.md`, `docs/en/codex-integration.md`, `docs/en/dashboard-guide.md`, `docs/en/features.md`, `docs/en/getting-started.md`, `docs/en/hybrid-search.md`, `docs/en/kiro-integration.md`, `docs/en/mcp-concepts.md`, `docs/en/tools-reference.md`, `docs/en/troubleshooting.md`, `docs/features/codebase-index.md`, `docs/id/auto-start-dashboard.md`, `docs/id/claude-code-integration.md`, `docs/id/codex-integration.md`, `docs/id/dashboard-guide.md`, `docs/id/features.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: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: feat: full-local natural language codebase search (codebase_search tool)
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: feat: full-local natural language codebase search (codebase_search tool). Context: Observed when using python
- Why it matters: Developers may fail before the first successful local run: feat: full-local natural language codebase search (codebase_search tool)
- Evidence: failure_mode_cluster:github_issue | https://github.com/vheins/local-memory-mcp/issues/45
- 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: Developers should check this installation risk before relying on the project: feat: tambahkan monorepo workspace seperti turbo repo
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: feat: tambahkan monorepo workspace seperti turbo repo. Context: Observed when using node
- Why it matters: Developers may fail before the first successful local run: feat: tambahkan monorepo workspace seperti turbo repo
- Evidence: failure_mode_cluster:github_issue | https://github.com/vheins/local-memory-mcp/issues/42
- 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: Developers should check this installation risk before relying on the project: perf: tree-sitter grammar WASMs eager-loaded at startup — 30MB+ waste
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: perf: tree-sitter grammar WASMs eager-loaded at startup — 30MB+ waste. Context: Observed when using python
- Why it matters: Developers may fail before the first successful local run: perf: tree-sitter grammar WASMs eager-loaded at startup — 30MB+ waste
- Evidence: failure_mode_cluster:github_issue | https://github.com/vheins/local-memory-mcp/issues/50
- 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: Developers should check this configuration risk before relying on the project: feat: unified neural network graph for memory, codebase, and task visualization
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: feat: unified neural network graph for memory, codebase, and task visualization. Context: Observed when using node
- Why it matters: Developers may misconfigure credentials, environment, or host setup: feat: unified neural network graph for memory, codebase, and task visualization
- Evidence: failure_mode_cluster:github_issue | https://github.com/vheins/local-memory-mcp/issues/58
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 5: Configuration risk requires verification

- Trigger: Developers should check this configuration risk before relying on the project: perf: missing composite indexes on (owner, repo) — full table scans on frequent queries
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: perf: missing composite indexes on (owner, repo) — full table scans on frequent queries. Context: Observed during version upgrade or migration.
- Why it matters: Developers may misconfigure credentials, environment, or host setup: perf: missing composite indexes on (owner, repo) — full table scans on frequent queries
- Evidence: failure_mode_cluster:github_issue | https://github.com/vheins/local-memory-mcp/issues/49
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.