# memex - 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: `nitekeeper/memex` - capability: Personal knowledge runtime and shared memory plane for Claude Code agent fleets — plugin-agnostic SQLite stores with federated FTS5 + vector search. - expected_user_outcome: Personal knowledge runtime and shared memory plane for Claude Code agent fleets — plugin-agnostic SQLite stores with federated FTS5 + vector search. ## 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. - **Memex Overview and Three-Layer Architecture**: importance `high` - source_paths: README.md, skills/run/SKILL.md, USER_GUIDE.md, CLAUDE.md, docs/CORE.md - **Memex Dashboard, 3D Knowledge Graph, and Federated Search**: importance `high` - source_paths: scripts/dashboard.py, internal/steward/dashboard/SKILL.md, internal/index/search/SKILL.md, internal/codegraph/query/SKILL.md, db/code_graph.sql - **Core Data Operations: Index, Brain, Internal Agents, and Code Graph**: importance `high` - source_paths: internal/index/write/SKILL.md, internal/index/archive/SKILL.md, internal/index/search/SKILL.md, internal/brain/ask/SKILL.md, internal/brain/ingest/SKILL.md - **Installation, Bootstrap, Deployment, and Extensibility**: importance `high` - source_paths: scripts/install.py, scripts/release.py, scripts/bump.py, scripts/upgrade_from_v1.py, scripts/onboarding.py ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `3dfba300f226d76d12ba79cf9819369acb06a23b` - inspected_files: `README.md`, `pyproject.toml`, `docs/BRAIN.md`, `docs/CORE.md`, `docs/INDEX.md`, `docs/PACKAGING.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: v2.10.0 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v2.10.0. Context: Observed during installation or first-run setup. - Why it matters: Upgrade or migration may change expected behavior: v2.10.0 - Evidence: failure_mode_cluster:github_release | https://github.com/nitekeeper/memex/releases/tag/v2.10.0 - 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: v2.11.0 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v2.11.0. Context: Observed when using python - Why it matters: Upgrade or migration may change expected behavior: v2.11.0 - Evidence: failure_mode_cluster:github_release | https://github.com/nitekeeper/memex/releases/tag/v2.11.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: v2.12.0 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v2.12.0. Context: Observed during installation or first-run setup. - Why it matters: Upgrade or migration may change expected behavior: v2.12.0 - Evidence: failure_mode_cluster:github_release | https://github.com/nitekeeper/memex/releases/tag/v2.12.0 - 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: v2.16.0 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v2.16.0. Context: Observed when using node, python - Why it matters: Upgrade or migration may change expected behavior: v2.16.0 - Evidence: failure_mode_cluster:github_release | https://github.com/nitekeeper/memex/releases/tag/v2.16.0 - 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: 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/nitekeeper/memex - 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: Developers should check this configuration risk before relying on the project: v2.13.0 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v2.13.0. Context: Source discussion did not expose a precise runtime context. - Why it matters: Upgrade or migration may change expected behavior: v2.13.0 - Evidence: failure_mode_cluster:github_release | https://github.com/nitekeeper/memex/releases/tag/v2.13.0 - 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/nitekeeper/memex - 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: Developers should check this migration risk before relying on the project: v2.12.2 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v2.12.2. Context: Observed during version upgrade or migration. - Why it matters: Upgrade or migration may change expected behavior: v2.12.2 - Evidence: failure_mode_cluster:github_release | https://github.com/nitekeeper/memex/releases/tag/v2.12.2 - 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: 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/nitekeeper/memex - 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: downstream_validation.risk_items | https://github.com/nitekeeper/memex - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.