# memorycrystal - 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: `memorycrystal/memorycrystal` - capability: Persistent memory for AI agents — OpenClaw plugin + MCP server - expected_user_outcome: Persistent memory for AI agents — OpenClaw plugin + MCP server ## 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. - **System Architecture & Memory Model**: importance `high` - source_paths: README.md, convex/crystal/recall.ts, convex/crystal/recallRanking.ts, convex/crystal/memories.ts, convex/crystal/messages.ts - **Integrations & Host Plugins**: importance `high` - source_paths: plugin/index.js, plugin/capture-hook.js, plugin/recall-hook.js, plugin/handler.js, plugin/memory-formatter.js - **Backend, Knowledge Bases & Security**: importance `high` - source_paths: convex/schema.ts, convex/http.ts, convex/crystal/knowledgeBases.ts, convex/crystal/knowledgeHttp.ts, convex/crystal/auth.ts - **Operations, Deployment & Diagnostics**: importance `high` - source_paths: scripts/crystal-doctor.sh, scripts/crystal-enable.sh, scripts/crystal-disable.sh, scripts/crystal-bootstrap.sh, scripts/convex-local-up.sh ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `56e0271e51d91258e3cd30f346a4838352f34ad4` - inspected_files: `README.md`, `package.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: Identity risk requires verification - Trigger: Project evidence flags a identity 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: identity.distribution | https://github.com/memorycrystal/memorycrystal - 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: Memory Crystal v0.8.11 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Memory Crystal v0.8.11. Context: Observed during installation or first-run setup. - Why it matters: Upgrade or migration may change expected behavior: Memory Crystal v0.8.11 - Evidence: failure_mode_cluster:github_release | https://github.com/memorycrystal/memorycrystal/releases/tag/v0.8.11 - 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: Memory Crystal v0.8.12 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Memory Crystal v0.8.12. Context: Observed during installation or first-run setup. - Why it matters: Upgrade or migration may change expected behavior: Memory Crystal v0.8.12 - Evidence: failure_mode_cluster:github_release | https://github.com/memorycrystal/memorycrystal/releases/tag/v0.8.12 - 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: Memory Crystal v0.8.13 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Memory Crystal v0.8.13. Context: Observed during installation or first-run setup. - Why it matters: Upgrade or migration may change expected behavior: Memory Crystal v0.8.13 - Evidence: failure_mode_cluster:github_release | https://github.com/memorycrystal/memorycrystal/releases/tag/v0.8.13 - 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: Developers should check this installation risk before relying on the project: Memory Crystal v0.8.14 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Memory Crystal v0.8.14. Context: Observed during installation or first-run setup. - Why it matters: Upgrade or migration may change expected behavior: Memory Crystal v0.8.14 - Evidence: failure_mode_cluster:github_release | https://github.com/memorycrystal/memorycrystal/releases/tag/v0.8.14 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: Installation risk requires verification - Trigger: Developers should check this installation risk before relying on the project: Memory Crystal v0.8.4 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Memory Crystal v0.8.4. Context: Observed when using docker - Why it matters: Upgrade or migration may change expected behavior: Memory Crystal v0.8.4 - Evidence: failure_mode_cluster:github_release | https://github.com/memorycrystal/memorycrystal/releases/tag/v0.8.4 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: Installation risk requires verification - Trigger: Developers should check this installation risk before relying on the project: Memory Crystal v0.8.5 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Memory Crystal v0.8.5. Context: Observed during installation or first-run setup. - Why it matters: Upgrade or migration may change expected behavior: Memory Crystal v0.8.5 - Evidence: failure_mode_cluster:github_release | https://github.com/memorycrystal/memorycrystal/releases/tag/v0.8.5 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 8: Installation risk requires verification - Trigger: Developers should check this installation risk before relying on the project: Memory Crystal v0.8.6 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Memory Crystal v0.8.6. Context: Observed during installation or first-run setup. - Why it matters: Upgrade or migration may change expected behavior: Memory Crystal v0.8.6 - Evidence: failure_mode_cluster:github_release | https://github.com/memorycrystal/memorycrystal/releases/tag/v0.8.6 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 9: Installation risk requires verification - Trigger: Developers should check this installation risk before relying on the project: Memory Crystal v0.8.7 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Memory Crystal v0.8.7. Context: Observed during installation or first-run setup. - Why it matters: Upgrade or migration may change expected behavior: Memory Crystal v0.8.7 - Evidence: failure_mode_cluster:github_release | https://github.com/memorycrystal/memorycrystal/releases/tag/v0.8.7 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 10: Installation risk requires verification - Trigger: Developers should check this installation risk before relying on the project: Memory Crystal v0.8.8 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Memory Crystal v0.8.8. Context: Observed during installation or first-run setup. - Why it matters: Upgrade or migration may change expected behavior: Memory Crystal v0.8.8 - Evidence: failure_mode_cluster:github_release | https://github.com/memorycrystal/memorycrystal/releases/tag/v0.8.8 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.