# Midas - 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: `vornicx/Midas` - capability: Local-first, eval-first memory for long-horizon AI agents — no LLM at ingest. Python SDK + MCP server with source-traceable recall, belief revision, selective forgetting, and reproducible benchmarks. - expected_user_outcome: Local-first, eval-first memory for long-horizon AI agents — no LLM at ingest. Python SDK + MCP server with source-traceable recall, belief revision, selective forgetting, and reproducible benchmarks. ## 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 & Architecture**: importance `high` - source_paths: README.md, midas/__init__.py, midas/policy.py, midas/memory.py, midas/types.py - **Core SDK & Memory Operations**: importance `high` - source_paths: midas/memory.py, midas/embeddings.py, midas/store.py, midas/sqlite_store.py, midas/ann.py - **MCP Server, Integrations & Distribution**: importance `high` - source_paths: midas/mcp_server.py, packages/midas-memory-mcp/README.md, packages/midas-memory-mcp/pyproject.toml, packages/midas-memory-mcp/midas_memory_mcp/__init__.py, server.json - **Evaluation, Safety & Governance**: importance `high` - source_paths: midas/guard.py, midas/distill.py, midas/nli.py, midas/state.py, midas/audit.py ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `6548f6d50629f530c9da524bf54cf10efb551b47` - inspected_files: `README.md`, `pyproject.toml`, `docs/MIDAS.md`, `docs/agent-memory-audit.md`, `docs/agent-memory-benches.md`, `docs/frontier-2026.md`, `docs/gtm.md`, `docs/long-horizon-memory.md`, `docs/methodology.md`, `docs/overnight-experiments.md`, `docs/research-notes.md`, `docs/traceability-plan.md`, `examples/coding_agent_demo.py`, `examples/distillation_demo.py`, `examples/turbovec_backend.py`, `packages/midas-memory-mcp/README.md`, `packages/midas-memory-mcp/midas_memory_mcp/__init__.py`, `packages/midas-memory-mcp/pyproject.toml`, `packages/midas-ts/README.md`, `packages/midas-ts/package-lock.json` 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: Add a machine-readable client wiring receipt for init/status - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Add a machine-readable client wiring receipt for init/status. Context: Observed during installation or first-run setup. - Why it matters: Developers may fail before the first successful local run: Add a machine-readable client wiring receipt for init/status - Evidence: failure_mode_cluster:github_issue | https://github.com/vornicx/Midas/issues/15 - 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: Midas v0.1.0 — the midas CLI, Memory Inspector & shared-by-default memory - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Midas v0.1.0 — the midas CLI, Memory Inspector & shared-by-default memory. Context: Observed when using python - Why it matters: Upgrade or migration may change expected behavior: Midas v0.1.0 — the midas CLI, Memory Inspector & shared-by-default memory - Evidence: failure_mode_cluster:github_release | https://github.com/vornicx/Midas/releases/tag/v0.1.0 - 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: Midas v0.1.1 — recall noise floor + end-to-end quickstart - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Midas v0.1.1 — recall noise floor + end-to-end quickstart. Context: Observed when using python - Why it matters: Upgrade or migration may change expected behavior: Midas v0.1.1 — recall noise floor + end-to-end quickstart - Evidence: failure_mode_cluster:github_release | https://github.com/vornicx/Midas/releases/tag/v0.1.1 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Installation risk requires verification - Trigger: Developers should check this installation risk before relying on the project: v0.0.4 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v0.0.4. Context: Observed when using python - Why it matters: Upgrade or migration may change expected behavior: v0.0.4 - Evidence: failure_mode_cluster:github_release | https://github.com/vornicx/Midas/releases/tag/v0.0.4 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: 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/vornicx/Midas/issues/15 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: 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/vornicx/Midas - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: 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/vornicx/Midas - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 8: 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/vornicx/Midas - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 9: 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/vornicx/Midas - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 10: 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/vornicx/Midas - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.