# cavemem - 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: `JuliusBrussee/cavemem` - capability: Cross-agent persistent memory for coding assistants. Stored compressed. Retrieved fast. Local by default. - expected_user_outcome: Cross-agent persistent memory for coding assistants. Stored compressed. Retrieved fast. Local by default. ## 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**: importance `high` - source_paths: README.md, apps/cli/package.json, apps/mcp-server/package.json, apps/worker/package.json, package.json - **Cli**: importance `high` - source_paths: apps/cli/.gitignore, apps/cli/CHANGELOG.md, apps/cli/package.json, apps/cli/scripts/pack-release.mjs, apps/cli/scripts/prepack.mjs - **Src**: importance `high` - source_paths: apps/cli/src/commands/compress.ts, apps/cli/src/commands/config.ts, apps/cli/src/commands/doctor.ts, apps/cli/src/commands/export.ts, apps/cli/src/commands/hook.ts - **Commands**: importance `high` - source_paths: apps/cli/src/commands/compress.ts, apps/cli/src/commands/config.ts, apps/cli/src/commands/doctor.ts, apps/cli/src/commands/export.ts, apps/cli/src/commands/hook.ts ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `1fe41e9c9f28380d3da9640f02812f8e5565839a` - inspected_files: `pnpm-lock.yaml`, `README.md`, `package.json`, `docs/architecture.md`, `docs/mcp.md`, `docs/development.md`, `docs/compression.md`, `examples/settings.example.json`, `packages/compress/CHANGELOG.md`, `packages/compress/package.json`, `packages/compress/tsconfig.json`, `packages/core/CHANGELOG.md`, `packages/core/package.json`, `packages/core/tsconfig.json`, `packages/config/CHANGELOG.md`, `packages/config/package.json`, `packages/config/tsconfig.json`, `packages/embedding/CHANGELOG.md`, `packages/embedding/package.json`, `packages/embedding/tsup.config.ts` 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: 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/JuliusBrussee/cavemem/issues/17 - 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: 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/JuliusBrussee/cavemem/issues/11 - 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: community_evidence:github | https://github.com/JuliusBrussee/cavemem/issues/39 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Security or permission risk requires verification - Trigger: Developers should check this security_permissions risk before relying on the project: No per-tool capture allowlist/matcher: sensitive MCP tool I/O captured by default - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: No per-tool capture allowlist/matcher: sensitive MCP tool I/O captured by default. Context: Observed during installation or first-run setup. - Why it matters: Developers may expose sensitive permissions or credentials: No per-tool capture allowlist/matcher: sensitive MCP tool I/O captured by default - Evidence: failure_mode_cluster:github_issue | https://github.com/JuliusBrussee/cavemem/issues/50 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: Security or permission risk requires verification - Trigger: Developers should check this security_permissions risk before relying on the project: Windows: hook commands written with backslashes break under bash -c (path collapse to `C:Usershp...`) - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Windows: hook commands written with backslashes break under bash -c (path collapse to `C:Usershp...`). Context: Observed when using node, windows - Why it matters: Developers may expose sensitive permissions or credentials: Windows: hook commands written with backslashes break under bash -c (path collapse to `C:Usershp...`) - Evidence: failure_mode_cluster:github_issue | https://github.com/JuliusBrussee/cavemem/issues/43 - 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: Developers should check this security_permissions risk before relying on the project: Worker HTTP viewer on 127.0.0.1:37777 is unauthenticated and serves decompressed memory - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Worker HTTP viewer on 127.0.0.1:37777 is unauthenticated and serves decompressed memory. Context: Observed during installation or first-run setup. - Why it matters: Developers may expose sensitive permissions or credentials: Worker HTTP viewer on 127.0.0.1:37777 is unauthenticated and serves decompressed memory - Evidence: failure_mode_cluster:github_issue | https://github.com/JuliusBrussee/cavemem/issues/51 - 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: Developers should check this security_permissions risk before relying on the project: privacy.excludePatterns is documented as enforced but is never read (matching paths still captured) - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: privacy.excludePatterns is documented as enforced but is never read (matching paths still captured). Context: Source discussion did not expose a precise runtime context. - Why it matters: Developers may expose sensitive permissions or credentials: privacy.excludePatterns is documented as enforced but is never read (matching paths still captured) - Evidence: failure_mode_cluster:github_issue | https://github.com/JuliusBrussee/cavemem/issues/48 - 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: Developers should check this security_permissions risk before relying on the project: redactSecrets is a no-op: secrets in tool output are stored verbatim (no output-side scrubber) - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: redactSecrets is a no-op: secrets in tool output are stored verbatim (no output-side scrubber). Context: Source discussion did not expose a precise runtime context. - Why it matters: Developers may expose sensitive permissions or credentials: redactSecrets is a no-op: secrets in tool output are stored verbatim (no output-side scrubber) - Evidence: failure_mode_cluster:github_issue | https://github.com/JuliusBrussee/cavemem/issues/49 - 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: Add Antigravity IDE support - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Add Antigravity IDE support. Context: Observed during installation or first-run setup. - Why it matters: Developers may fail before the first successful local run: Add Antigravity IDE support - Evidence: failure_mode_cluster:github_issue | https://github.com/JuliusBrussee/cavemem/issues/38 - 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: Add Trae SOLO IDE support - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Add Trae SOLO IDE support. Context: Observed during installation or first-run setup. - Why it matters: Developers may fail before the first successful local run: Add Trae SOLO IDE support - Evidence: failure_mode_cluster:github_issue | https://github.com/JuliusBrussee/cavemem/issues/40 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.