# hivemind - 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 hivemind. 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_0004` supported 0.86 - **Users who want to bring professional workflows into a host AI**: The repo contains Skill documents. Evidence: `harnesses/claude-code/skills/hivemind-goals/SKILL.md`, `harnesses/claude-code/skills/hivemind-graph/SKILL.md`, `harnesses/claude-code/skills/hivemind-memory/SKILL.md`, `harnesses/codex/skills/deeplake-memory/SKILL.md` et al. Claim: `clm_0005` supported 0.86 ## What It Can Do - **AI Skill / Agent Instruction Asset Library** (Previewable before install): The project contains Skill or Agent instruction files that a host AI can read, useful for bringing professional workflows into hosts like Claude, Codex, or Cursor. Evidence: `harnesses/claude-code/skills/hivemind-goals/SKILL.md`, `harnesses/claude-code/skills/hivemind-graph/SKILL.md`, `harnesses/claude-code/skills/hivemind-memory/SKILL.md`, `harnesses/codex/skills/deeplake-memory/SKILL.md` et al. Claim: `clm_0001` supported 0.86 - **Multi-Host Install and Distribution** (Verify after install): The project contains plugin or marketplace configuration, indicating it targets install and distribution across one or more AI hosts. Evidence: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`, `harnesses/claude-code/.claude-plugin/plugin.json`, `harnesses/codex/.codex-plugin/plugin.json` et al. Claim: `clm_0002` supported 0.86 - **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`, `harnesses/codex/INSTALL.md` Claim: `clm_0003` supported 0.86 ## How to Start - `npm i -g @deeplake/hivemind && hivemind install` Evidence: `README.md` Claim: `clm_0006` supported 0.86 - `/plugin marketplace add activeloopai/hivemind` Evidence: `README.md` Claim: `clm_0007` supported 0.86 - `/plugin install hivemind` Evidence: `README.md` Claim: `clm_0008` supported 0.86 - `git clone https://github.com/activeloopai/hivemind.git ~/.codex/hivemind` Evidence: `README.md` Claim: `clm_0009` supported 0.86 - `git clone https://github.com/activeloopai/hivemind.git` Evidence: `README.md` Claim: `clm_0009` supported 0.86, `clm_0010` supported 0.86 - `npx @deeplake/hivemind@latest install` Evidence: `harnesses/codex/INSTALL.md` Claim: `clm_0011` supported 0.86 - `npx @deeplake/hivemind@latest codex install` Evidence: `harnesses/codex/INSTALL.md` Claim: `clm_0012` supported 0.86 - `npx @deeplake/hivemind@latest codex uninstall` Evidence: `harnesses/codex/INSTALL.md` Claim: `clm_0013` supported 0.86 ## Continue-or-Stop Decision Card - **Current recommendation**: Needs admin / security approval - **Why**: Continuing may involve secrets, accounts, external services, or sensitive context; get admin or security approval first. ### 30-Second Read - **What to do now**: Needs admin / security approval - **Minimum safe next step**: Run Prompt Preview first; if credentials or an enterprise environment are involved, get approval before trialing - **Do not trust yet**: Real output quality cannot be trusted before install. - **Continuing will touch**: Command execution, Host AI configuration, Local environment or project files ### 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_0004` supported 0.86 - **Target-audience signal: Users who want to bring professional workflows into a host AI** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `harnesses/claude-code/skills/hivemind-goals/SKILL.md`, `harnesses/claude-code/skills/hivemind-graph/SKILL.md`, `harnesses/claude-code/skills/hivemind-memory/SKILL.md`, `harnesses/codex/skills/deeplake-memory/SKILL.md` et al. Claim: `clm_0005` supported 0.86 - **Capability exists: AI Skill / Agent Instruction Asset Library** (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: `harnesses/claude-code/skills/hivemind-goals/SKILL.md`, `harnesses/claude-code/skills/hivemind-graph/SKILL.md`, `harnesses/claude-code/skills/hivemind-memory/SKILL.md`, `harnesses/codex/skills/deeplake-memory/SKILL.md` et al. Claim: `clm_0001` supported 0.86 - **Capability exists: Multi-Host Install and Distribution** (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: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`, `harnesses/claude-code/.claude-plugin/plugin.json`, `harnesses/codex/.codex-plugin/plugin.json` et al. 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`, `harnesses/codex/INSTALL.md` Claim: `clm_0003` 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_0006` supported 0.86 ### What You Cannot Trust Yet - **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: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`, `harnesses/claude-code/.claude-plugin/plugin.json`, `harnesses/claude-code/skills/hivemind-goals/SKILL.md` et al. - **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. Evidence: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`, `harnesses/claude-code/.claude-plugin/plugin.json`, `harnesses/codex/.codex-plugin/plugin.json` et al. - **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. - **Do the install commands require network access, permissions, or global writes?** (unverified): This affects install risk in both enterprise and personal environments. Evidence: `README.md` ### What Continuing Will Touch - **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`, `harnesses/codex/INSTALL.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: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`, `harnesses/claude-code/.claude-plugin/plugin.json`, `harnesses/claude-code/skills/hivemind-goals/SKILL.md` et al. - **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: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`, `README.md`, `harnesses/claude-code/.claude-plugin/plugin.json` et al. - **Environment variables / API keys**: Project entry docs explicitly showing API key, token, secret, or account credential configuration. Why: If a real install needs credentials, use test credentials first and go through a permission/compliance review. Evidence: `README.md`, `library/knowledge/private/auth/auth-architecture.md`, `library/knowledge/private/multi-tenant/org-workspace-model.md`, `library/knowledge/private/security/credential-storage.md` et al. - **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 a pre-install interactive trial to judge whether the way of working fits; it needs no authorization or environment change. (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.) - **Do not use real production credentials**: Once an environment variable / API key enters the host or toolchain, it can create account and compliance risk. (applies when: When environment signals like API, TOKEN, KEY, or SECRET appear.) - **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. - **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. - **Be ready to revoke test API keys or tokens**: If test credentials leak or are misused, you can cut losses quickly. - **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_0014` inferred 0.45 - **Host AI plugin or Skill rule conflicts**: New rules may change how the user's existing host AI behaves. Mitigation: Inspect the plugin manifest and Skill files before installing, and test in isolation if needed. Evidence: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`, `harnesses/claude-code/.claude-plugin/plugin.json`, `harnesses/codex/.codex-plugin/plugin.json` et al. Claim: `clm_0015` supported 0.86 - **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`, `harnesses/codex/INSTALL.md` Claim: `clm_0016` 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 - **AI Skill / Agent Instruction Asset Library**: Use role_skill_index / evidence_index to help the user pick a usable role, Skill, or workflow first. Boundary: Can be experienced via a pre-install Prompt. Evidence: `harnesses/claude-code/skills/hivemind-goals/SKILL.md`, `harnesses/claude-code/skills/hivemind-graph/SKILL.md`, `harnesses/claude-code/skills/hivemind-memory/SKILL.md`, `harnesses/codex/skills/deeplake-memory/SKILL.md` et al. Claim: `clm_0001` supported 0.86 - **Multi-Host Install and Distribution**: 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: `.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`, `harnesses/claude-code/.claude-plugin/plugin.json`, `harnesses/codex/.codex-plugin/plugin.json` et al. Claim: `clm_0002` supported 0.86 - **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`, `harnesses/codex/INSTALL.md` Claim: `clm_0003` supported 0.86 ### Context Scale - Total files: 347 - Important-file coverage: 40/347 - Evidence index entries: 79 - Role / Skill entries: 11 ### 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 hivemind, 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 hivemind 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 hivemind, 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 11 role / Skill / project-doc entries. - **hivemind-goals** (skill): Create, track and update team goals + KPIs via the Deeplake virtual filesystem at memory/goal/ and memory/kpi/. Use whenever the user mentions a goal, objective, KPI, target, milestone, or asks to track progress on something measurable. ALSO use when the user says "task", "todo", "work item", "remind me to", "fix X", or any actionable work item — the goal system replaced the legacy hivemind tasks CLI and now covers… Activation hint: When the user's task is highly relevant to the workflow described by “hivemind-goals”, use it for a pre-install experience first, then decide whether to install. Evidence: `harnesses/claude-code/skills/hivemind-goals/SKILL.md` - **hivemind-graph** (skill): Query the local code graph functions, classes, calls, imports through the Deeplake mount at memory/graph/. Use when the user asks structural questions about the codebase — "what calls X?", "what does Y import?", "where is Z defined?", "what's the architecture / which subsystems exist?", "what's the impact of changing this?". The graph is an AST-derived map of the repo, queried as files no build needed — it rebuilds… Activation hint: When the user's task is highly relevant to the workflow described by “hivemind-graph”, use it for a pre-install experience first, then decide whether to install. Evidence: `harnesses/claude-code/skills/hivemind-graph/SKILL.md` - **hivemind-memory** (skill): Global team and org memory powered by Activeloop. ALWAYS check BOTH built-in memory AND Hivemind memory when recalling information. Activation hint: When the user's task is highly relevant to the workflow described by “hivemind-memory”, use it for a pre-install experience first, then decide whether to install. Evidence: `harnesses/claude-code/skills/hivemind-memory/SKILL.md` - **hivemind-memory** (skill): Global team and org memory powered by Activeloop. ALWAYS check BOTH built-in memory AND Hivemind memory when recalling information. Activation hint: When the user's task is highly relevant to the workflow described by “hivemind-memory”, use it for a pre-install experience first, then decide whether to install. Evidence: `harnesses/codex/skills/deeplake-memory/SKILL.md` - **hivemind-goals** (skill): Create, track and update team goals + KPIs via the Deeplake virtual filesystem at memory/goal/ and memory/kpi/. Use whenever the user mentions a goal, objective, KPI, target, milestone, or asks to track progress on something measurable. ALSO use when the user says "task", "todo", "work item", "remind me to", "fix X", or any actionable work item — the goal system replaced the legacy hivemind tasks CLI and now covers… Activation hint: When the user's task is highly relevant to the workflow described by “hivemind-goals”, use it for a pre-install experience first, then decide whether to install. Evidence: `harnesses/codex/skills/hivemind-goals/SKILL.md` - **hivemind-graph** (skill): Query the local code graph functions, classes, calls, imports through the Deeplake mount at memory/graph/. Use when the user asks structural questions about the codebase — "what calls X?", "what does Y import?", "where is Z defined?", "what is the architecture / which subsystems exist?". The graph is an AST-derived map of the repo, queried as files no build needed — it rebuilds automatically . Activation hint: When the user's task is highly relevant to the workflow described by “hivemind-graph”, use it for a pre-install experience first, then decide whether to install. Evidence: `harnesses/codex/skills/hivemind-graph/SKILL.md` - **hivemind-goals** (skill): Create, track and update team goals + KPIs in Hivemind via the hivemind CLI. Use whenever the user mentions a goal, objective, KPI, target, milestone, or asks to track progress on something measurable. ALSO use when the user says "task", "todo", "work item", "remind me to", "fix X", or any actionable work item — the goal system replaced the legacy hivemind tasks CLI and now covers both objectives and tasks. Activation hint: When the user's task is highly relevant to the workflow described by “hivemind-goals”, use it for a pre-install experience first, then decide whether to install. Evidence: `harnesses/hermes/skills/hivemind-goals/SKILL.md` - **hivemind-graph** (skill): Query the local code graph functions, classes, calls, imports through the Deeplake mount at memory/graph/. Use when the user asks structural questions about the codebase — "what calls X?", "what does Y import?", "where is Z defined?", "what is the architecture / which subsystems exist?". The graph is an AST-derived map of the repo, queried as files no build needed — it rebuilds automatically . Activation hint: When the user's task is highly relevant to the workflow described by “hivemind-graph”, use it for a pre-install experience first, then decide whether to install. Evidence: `harnesses/hermes/skills/hivemind-graph/SKILL.md` - **hivemind** (skill): Global team and org memory powered by Activeloop. ALWAYS check BOTH built-in memory AND Hivemind memory when recalling information. Activation hint: When the user's task is highly relevant to the workflow described by “hivemind”, use it for a pre-install experience first, then decide whether to install. Evidence: `harnesses/openclaw/skills/SKILL.md` - **hivemind-goals** (skill): Create, track, and read team goals + KPIs via Hivemind from openclaw. Use whenever the user mentions a goal, objective, KPI, target, milestone, or asks to track progress on something measurable. ALSO use when the user says "task", "todo", "work item", "remind me to", "fix X", or any actionable work item — the goal system replaced the legacy hivemind tasks CLI and now covers both objectives and tasks. Activation hint: When the user's task is highly relevant to the workflow described by “hivemind-goals”, use it for a pre-install experience first, then decide whether to install. Evidence: `harnesses/openclaw/skills/hivemind-goals/SKILL.md` - **hivemind-graph** (skill): Query the local AST-derived code graph functions, classes, calls, imports for structural codebase questions — what calls X, what does Y import, where is Z defined, blast radius of a change. The graph rebuilds automatically after each agent turn; use hivemind graph search and hivemind graph neighborhood tools no manual build step . Activation hint: When the user's task is highly relevant to the workflow described by “hivemind-graph”, use it for a pre-install experience first, then decide whether to install. Evidence: `harnesses/openclaw/skills/hivemind-graph/SKILL.md` ## Evidence Index - Indexed 79 evidence entries. - **Benchmarks** (documentation): Auto-learning, cloud-backed shared brain for Claude Code • OpenClaw • Codex • Cursor • Hermes • pi • Claude Cowork Alpha agents. Evidence: `README.md` - **Library** (documentation): Documentation root for this repository. Schema version: v2 . Evidence: `library/README.md` - **Hivemind** (documentation): Cloud-backed shared memory for AI agents. Install once, memory persists across sessions, machines, and channels — and is shared with every teammate in your Deeplake org. Evidence: `harnesses/openclaw/README.md` - **Issues** (documentation): Reactive bug and incident work IRDs , organized by lifecycle state. Evidence: `library/issues/README.md` - **Issues — Backlog** (documentation): Tracked issues with a fix plan, not yet in active resolution. Evidence: `library/issues/backlog/README.md` - **Issues — Completed** (documentation): Resolved IRD folders. Entire ird- - / folders land here when the GitHub issue closes and the fix is confirmed. Do not edit files here after landing. Evidence: `library/issues/completed/README.md` - **Issues — In Work** (documentation): IRDs currently being resolved. Move from backlog/ → here when fix work starts, then completed/ when the GitHub issue closes. Evidence: `library/issues/in-work/README.md` - **Knowledge** (documentation): Reference documentation for this repository, organized by audience. Evidence: `library/knowledge/README.md` - **Knowledge — Private** (documentation): Internal documentation for engineers, product, and AI agents. Evidence: `library/knowledge/private/README.md` - **Knowledge — Public** (documentation): Customer-facing documentation. Anything in this folder may eventually be published. Evidence: `library/knowledge/public/README.md` - **Notes** (documentation): Human-only scratch space. Agents never read or write here. Evidence: `library/notes/README.md` - **Requirements** (documentation): Product and feature work, organized by lifecycle state. Evidence: `library/requirements/README.md` - **Requirements — Backlog** (documentation): Planned PRDs not yet in implementation. All new PRD folders are created here. Evidence: `library/requirements/backlog/README.md` - **Requirements — Completed** (documentation): Shipped PRD folders. Entire prd- - / folders land here after the work ships and is confirmed in production. Do not edit files here after landing. Evidence: `library/requirements/completed/README.md` - **Requirements — In Work** (documentation): PRDs currently being implemented. Folder location = lifecycle state. Evidence: `library/requirements/in-work/README.md` - **Requirements — Reports** (documentation): Routine code-scan and audit reports not tied to any specific PRD. Evidence: `library/requirements/reports/README.md` - **Package** (package_manifest): { "name": "@deeplake/hivemind", "version": "0.7.118", "description": "Cloud-backed persistent shared memory for AI agents powered by Deeplake", "type": "module", "repository": { "type": "git", "url": "git+https://github.com/activeloopai/hivemind.git" }, "publishConfig": { "access": "public" }, "bin": { "hivemind": "bundle/cli.js" }, "files": "bundle", "harnesses/codex/bundle", "harnesses/codex/skills", "harnesses/cursor/bundle", "harnesses/hermes/bundle", "mcp/bundle", "harnesses/pi/extension-source", "harnesses/openclaw/dist", "harnesses/openclaw/skills", "harnesses/openclaw/openclaw.plugin.json", "harnesses/openclaw/package.json", ".claude-plugin", "scripts", "README.md", "LICENSE" , "scr… Evidence: `package.json` - **Package** (package_manifest): { "name": "hivemind-codex", "version": "0.7.118", "description": "Cloud-backed persistent shared memory for OpenAI Codex CLI powered by Deeplake", "type": "module" } Evidence: `harnesses/codex/package.json` - **Package** (package_manifest): { "name": "hivemind", "version": "0.7.118", "type": "module", "description": "Hivemind — cloud-backed persistent shared memory for AI agents, powered by DeepLake", "license": "Apache-2.0", "openclaw": { "extensions": "./dist/index.js" , "install": { "npmSpec": "@deeplake/hivemind", "minHostVersion": " =2026.3.22" }, "compat": { "pluginApi": " =1.0.0" }, "build": { "openclawVersion": "2026.3.22" } }, "files": "dist", "openclaw.plugin.json" , "scripts": { "build": "node esbuild.config.mjs" } } Evidence: `harnesses/openclaw/package.json` - **Hivemind Goals** (skill_instruction): Track goals and KPIs as Markdown files inside the Deeplake virtual filesystem. Each file is one row in a dedicated team-shared table — the path encodes the structural metadata, the file body holds the human-readable description. Evidence: `harnesses/claude-code/skills/hivemind-goals/SKILL.md` - **Hivemind Code Graph** (skill_instruction): A deterministic, AST-derived map of the current repository — every function, class, method, interface, type, enum, const, and module, plus the edges between them calls , imports , extends , implements , method of . It is queried as synthesized files under the Deeplake mount; there are no real files on disk and no network call in the read path. Evidence: `harnesses/claude-code/skills/hivemind-graph/SKILL.md` - **Hivemind Memory** (skill_instruction): You have TWO memory sources. ALWAYS check BOTH when the user asks you to recall, remember, or look up ANY information: Evidence: `harnesses/claude-code/skills/hivemind-memory/SKILL.md` - **Installing Hivemind for Codex CLI** (documentation): The fastest path installs hivemind into every AI coding assistant on your machine Claude Code, Codex, OpenClaw with one command: Evidence: `harnesses/codex/INSTALL.md` - **Hivemind Memory** (skill_instruction): You have persistent memory at ~/.deeplake/memory/ — global memory shared across all sessions, users, and agents in the org. Evidence: `harnesses/codex/skills/deeplake-memory/SKILL.md` - **Hivemind Goals** (skill_instruction): Track goals and KPIs as Markdown files inside the Deeplake virtual filesystem. Each file is one row in a dedicated team-shared table — the path encodes the structural metadata, the file body holds the human-readable description. Evidence: `harnesses/codex/skills/hivemind-goals/SKILL.md` - **Hivemind Code Graph** (skill_instruction): A deterministic, AST-derived map of the current repository — every function, class, method, interface, type, enum, const, and module, plus the edges between them calls , imports , extends , implements , method of . It is queried as synthesized files under the Deeplake mount; there are no real files on disk and no network call in the read path. Evidence: `harnesses/codex/skills/hivemind-graph/SKILL.md` - **Hivemind Goals — CLI only Hermes** (skill_instruction): ⚠️ CRITICAL: On this runtime Hermes , you MUST use the hivemind shell CLI for goals + KPIs. DO NOT use write file on ~/.deeplake/memory/goal/... paths — those writes go to the local filesystem and never reach the team-shared hivemind goals table. Other team members will NOT see them. Evidence: `harnesses/hermes/skills/hivemind-goals/SKILL.md` - **Hivemind Code Graph** (skill_instruction): A deterministic, AST-derived map of the current repository — every function, class, method, interface, type, enum, const, and module, plus the edges between them calls , imports , extends , implements , method of . It is queried as synthesized files under the Deeplake mount; there are no real files on disk and no network call in the read path. Evidence: `harnesses/hermes/skills/hivemind-graph/SKILL.md` - **Hivemind Memory** (skill_instruction): You have TWO memory sources. ALWAYS check BOTH when the user asks you to recall, remember, or look up ANY information: Evidence: `harnesses/openclaw/skills/SKILL.md` - **Hivemind Goals openclaw** (skill_instruction): OpenClaw exposes purpose-built tools for goals + KPIs. Use them directly — do NOT try to write files via the host filesystem. Evidence: `harnesses/openclaw/skills/hivemind-goals/SKILL.md` - **Hivemind Code Graph OpenClaw** (skill_instruction): A deterministic, AST-derived map of the current repository — every function, class, method, interface, type, enum, const, and module, plus the edges between them calls , imports , extends , implements , method of . Evidence: `harnesses/openclaw/skills/hivemind-graph/SKILL.md` - **Marketplace** (structured_config): { "name": "hivemind", "owner": { "name": "Activeloop", "email": "support@activeloop.ai" }, "metadata": { "description": "Cloud-backed persistent shared memory for AI agents powered by Deeplake", "version": "0.7.118" }, "plugins": { "name": "hivemind", "description": "Persistent shared memory powered by Deeplake — captures all session activity and provides cross-session, cross-agent memory search", "version": "0.7.118", "source": { "source": "git-subdir", "url": "https://github.com/activeloopai/hivemind.git", "path": "harnesses/claude-code", "sha": "c065c43b3965b5cdeee90d3627a2c771da1b20ba" }, "homepage": "https://github.com/activeloopai/hivemind" } } Evidence: `.claude-plugin/marketplace.json` - **Plugin** (structured_config): { "name": "hivemind", "description": "Cloud-backed persistent memory powered by Deeplake — read, write, and share memory across Claude Code sessions and agents", "version": "0.7.118", "author": { "name": "Activeloop", "url": "https://deeplake.ai" }, "homepage": "https://deeplake.ai", "repository": "https://github.com/activeloopai/hivemind", "license": "Apache-2.0", "keywords": "memory", "deeplake", "persistent-memory", "shared-memory", "agent-memory" } Evidence: `.claude-plugin/plugin.json` - **Plugin** (structured_config): { "name": "hivemind", "description": "Cloud-backed persistent memory powered by Deeplake — read, write, and share memory across Claude Code sessions and agents", "version": "0.7.118", "author": { "name": "Activeloop", "url": "https://deeplake.ai" }, "homepage": "https://deeplake.ai", "repository": "https://github.com/activeloopai/hivemind", "license": "Apache-2.0", "keywords": "memory", "deeplake", "persistent-memory", "shared-memory", "agent-memory" } Evidence: `harnesses/claude-code/.claude-plugin/plugin.json` - **Plugin** (structured_config): { "name": "hivemind", "version": "0.6.7", "description": "Cloud-backed persistent memory powered by Deeplake — read, write, and share memory across Codex sessions and agents", "skills": , "mcpServers": , "apps": , "interface": { "displayName": "Hivemind Memory", "shortDescription": "Persistent shared memory for AI agents powered by Deeplake", "longDescription": "Captures all session activity and provides cross-session, cross-agent memory search via ~/.deeplake/memory/. Memory is stored in Deeplake managed tables and shared across sessions, users, and agents in your organization.", "developerName": "Activeloop", "category": "productivity", "capabilities": "memory", "session-capture", "search… Evidence: `harnesses/codex/.codex-plugin/plugin.json` - **License** (source_file): Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ Evidence: `LICENSE` - **Architecture** (documentation): Agent Mechanism Hooks/tools wired ------------------- ------------------------------------ ----------------------------------------------------------------------------------------- Claude Code Marketplace plugin SessionStart · UserPromptSubmit · PreToolUse · PostToolUse · Stop · SubagentStop · SessionEnd Codex ~/.codex/hooks.json SessionStart · UserPromptSubmit · PreToolUse Bash · PostToolUse · Stop OpenClaw Native extension at ~/.openclaw/extensions/hivemind/ agent end capture · before agent start recall · contracted tools hivemind search / read / index Cursor 1.7+ ~/.cursor/hooks.json sessionStart · beforeSubmitPrompt · postToolUse · afterAgentResponse · stop · sessionEnd Hermes Skill at… Evidence: `docs/ARCHITECTURE.md` - **Capture Tasks — turning conversation tangents into Hivemind goals** (documentation): Capture Tasks — turning conversation tangents into Hivemind goals Evidence: `docs/CAPTURE_TASKS.md` - **Embeddings semantic search** (documentation): Hivemind can run a local embedding daemon nomic-embed-text-v1.5, ~130 MB so that Grep over ~/.deeplake/memory/ uses hybrid semantic + lexical ranking instead of pure BM25. This is off by default — the daemon depends on @huggingface/transformers , which pulls onnxruntime-node and sharp ~600 MB total with native binaries . Shipping that with every agent install would 60× the install size for a feature most users don't need. Evidence: `docs/EMBEDDINGS.md` - **Skills skillify** (documentation): Hivemind codifies recurring patterns from your team's recent sessions into reusable skills that propagate to every agent on your team — automatically. Same architecture as the wiki worker: an async background process that fires on Stop / SessionEnd, mines recent sessions in scope, asks Haiku whether the activity contains something worth keeping, and writes a SKILL.md if so. Evidence: `docs/SKILLIFY.md` - **Summaries** (documentation): Hivemind doesn't just capture raw events — it also generates an AI-written wiki summary for each session and stores it in the memory table alongside its 768-dim summary embedding . The summary is what shows up when you Grep for past sessions or follow links from ~/.deeplake/memory/index.md . Evidence: `docs/SUMMARIES.md` - **Embed Daemon** (source_file): function socketPathFor uid, dir = DEFAULT SOCKET DIR function pidPathFor uid, dir = DEFAULT SOCKET DIR ⋮---- async function importFromCanonicalSharedDeps sharedDir = join homedir , ".hivemind", "embed-deps" async function importFromBareSpecifier function normalizeTransformersModule mod async function defaultImportTransformers canonical = importFromCanonicalSharedDeps, bare = importFromBareSpecifier ⋮---- async load addPrefix text, kind async embed text, kind = "document" async embedBatch texts, kind = "document" truncate vec ⋮---- function isDebug function log tag, msg ⋮---- appendFileSync LOG, ${ / @ PURE / new Date .toISOString } ${tag} ${msg} ⋮---- var log2 = m function getUid ⋮---- asyn… Evidence: `embeddings/embed-daemon.js` - **Config** (source_file): import { readFileSync, existsSync } from "node:fs"; import { join } from "node:path"; import { homedir, userInfo } from "node:os"; ⋮---- export interface Config { token: string; orgId: string; orgName: string; userName: string; workspaceId: string; apiUrl: string; tableName: string; sessionsTableName: string; skillsTableName: string; rulesTableName: string; goalsTableName: string; kpisTableName: string; codebaseTableName: string; memoryPath: string; } ⋮---- interface Credentials { token: string; orgId: string; orgName?: string; userName?: string; workspaceId?: string; apiUrl?: string; } ⋮---- export function loadConfig : Config null Evidence: `src/config.ts` - **Deeplake Api** (source_file): import { randomUUID } from "node:crypto"; import { log as log } from "./utils/debug.js"; import { sqlStr, sqlIdent } from "./utils/sql.js"; import { SUMMARY EMBEDDING COL } from "./embeddings/columns.js"; import { deeplakeClientHeader } from "./utils/client-header.js"; import { CODEBASE COLUMNS, MEMORY COLUMNS, SESSIONS COLUMNS, SKILLS COLUMNS, RULES COLUMNS, GOALS COLUMNS, KPIS COLUMNS, buildCreateTableSql, healMissingColumns, } from "./deeplake-schema.js"; import { enqueueNotification } from "./notifications/queue.js"; import { loadCredentials } from "./commands/auth-creds.js"; ⋮---- type IndexMarkerStore = typeof import "./index-marker-store.js" ; ⋮---- function getIndexMarkerStore : Pro… Evidence: `src/deeplake-api.ts` - **Index Marker Store** (source_file): import { existsSync, mkdirSync, readFileSync, writeFileSync } from "node:fs"; import { join } from "node:path"; import { tmpdir } from "node:os"; ⋮---- export function getIndexMarkerDir : string ⋮---- export function buildIndexMarkerPath workspaceId: string, orgId: string, table: string, suffix: string : string ⋮---- export function hasFreshIndexMarker markerPath: string : boolean ⋮---- export function writeIndexMarker markerPath: string : void Evidence: `src/index-marker-store.ts` - **User Config** (source_file): import { existsSync, mkdirSync, readFileSync, renameSync, writeFileSync } from "node:fs"; import { homedir } from "node:os"; import { dirname, join } from "node:path"; ⋮---- export interface UserConfig { embeddings?: { enabled?: boolean; }; } ⋮---- let configPath: ⋮---- export function readUserConfig : UserConfig ⋮---- export function writeUserConfig patch: Partial : UserConfig ⋮---- export function getEmbeddingsEnabled : boolean ⋮---- function migrationValueFromEnv : boolean ⋮---- export function setEmbeddingsEnabled enabled: boolean : void ⋮---- function isPlainObject value: unknown : value is Record ⋮---- function deepMerge base: UserConfig, patch: Partial : UserConfig ⋮---- export funct… Evidence: `src/user-config.ts` - **Vitest.Config** (source_file): import { defineConfig } from "vitest/config"; Evidence: `vitest.config.ts` - **Index** (source_file): function definePluginEntry entry: T : T ⋮---- type SetupConfigModule = typeof import "./setup-config.js" ; function loadSetupConfig : Promise ⋮---- import { requestDeviceCode, pollForToken, listOrgs, switchOrg, listWorkspaces, switchWorkspace, healDriftedOrgToken } from "../../../src/commands/auth.js"; import { DeeplakeApi } from "../../../src/deeplake-api.js"; ⋮---- type CredsModule = typeof import "../../../src/commands/auth-creds.js" ; type ConfigModule = typeof import "../../../src/config.js" ; ⋮---- function loadCredsModule : Promise function loadConfigModule : Promise async function loadCredentials async function saveCredentials creds: Awaited : Promise async function loadConfig impor… Evidence: `harnesses/openclaw/src/index.ts` - **Setup Config** (source_file): import { existsSync, readFileSync, writeFileSync, renameSync } from "node:fs"; import { homedir } from "node:os"; import { join } from "node:path"; ⋮---- export function getOpenclawConfigPath : string ⋮---- export function isAllowlistCoveringHivemind alsoAllow: unknown : boolean ⋮---- export function isPluginsAllowMissingHivemind allow: unknown : boolean ⋮---- export type AllowlistDelta = { pluginsAllow: boolean; toolsAlsoAllow: boolean; }; ⋮---- export type SetupResult = { status: "already-set"; configPath: string } { status: "added"; configPath: string; backupPath: string; delta: AllowlistDelta } { status: "error"; configPath: string; error: string }; ⋮---- export function ensureHivemindA… Evidence: `harnesses/openclaw/src/setup-config.ts` - **Index** (source_file): import { installClaude, uninstallClaude } from "./install-claude.js"; import { installCodex, uninstallCodex } from "./install-codex.js"; import { installOpenclaw, uninstallOpenclaw } from "./install-openclaw.js"; import { installCursor, uninstallCursor } from "./install-cursor.js"; import { installHermes, uninstallHermes } from "./install-hermes.js"; import { installCowork, uninstallCowork } from "./install-cowork.js"; import { installPi, uninstallPi } from "./install-pi.js"; import { disableEmbeddings, enableEmbeddings, installEmbeddings, statusEmbeddings, uninstallEmbeddings, } from "./embeddings.js"; import { ensureLoggedIn, isLoggedIn, loginWithProvidedToken, maybeShowOrgChoice } from "… Evidence: `src/cli/index.ts` - **Install Claude** (source_file): import { execFileSync } from "node:child process"; import { existsSync, readFileSync, writeFileSync } from "node:fs"; import { homedir } from "node:os"; import { join } from "node:path"; import { log } from "./util.js"; ⋮---- interface ClaudeResult { ok: boolean; stdout: string; stderr: string; } ⋮---- function runClaude args: string : ClaudeResult ⋮---- function requireClaudeCli : void ⋮---- function marketplaceAlreadyAdded : boolean ⋮---- function pluginAlreadyInstalled : boolean ⋮---- interface HookEntry { type?: string; command?: string; timeout?: number; async?: boolean; } ⋮---- interface HookMatcher { matcher?: string; hooks: HookEntry ; } ⋮---- interface SettingsShape { hooks?: Recor… Evidence: `src/cli/install-claude.ts` - **Install Codex** (source_file): import { existsSync, lstatSync, readFileSync, rmSync, unlinkSync, writeFileSync } from "node:fs"; import { execFileSync } from "node:child process"; import { join } from "node:path"; import { HOME, pkgRoot, ensureDir, copyDir, writeJson, writeJsonIfChanged, symlinkForce, writeVersionStamp, log, warn } from "./util.js"; import { getVersion } from "./version.js"; import { upsertMarkedBlock, stripMarkedBlock, HIVEMIND BLOCK START, HIVEMIND BLOCK END } from "./agents-md.js"; ⋮---- function hookCmd bundleFile: string, timeout: number, matcher?: string : Record ⋮---- function buildHooksJson : Record ⋮---- function stopBlockWithGraph timeout: number : Record ⋮---- export function isHivemindHookEnt… Evidence: `src/cli/install-codex.ts` - **Install Cursor** (source_file): import { existsSync, lstatSync, rmSync, unlinkSync } from "node:fs"; import { join } from "node:path"; import { HOME, pkgRoot, ensureDir, copyDir, readJson, writeJson, writeJsonIfChanged, symlinkForce, writeVersionStamp, log } from "./util.js"; import { getVersion } from "./version.js"; ⋮---- interface CursorHookEntry { type: "command" "prompt"; command?: string; timeout?: number; matcher?: string Record ; } ⋮---- function buildHookCmd bundleFile: string, timeout: number : CursorHookEntry ⋮---- function buildHookCmdShellMatcher bundleFile: string, timeout: number : CursorHookEntry ⋮---- function buildHookConfig : Record ⋮---- export function isHivemindEntry entry: unknown : boolean ⋮---- fu… Evidence: `src/cli/install-cursor.ts` - **Install Hermes** (source_file): import { existsSync, lstatSync, writeFileSync, readFileSync, rmSync, unlinkSync } from "node:fs"; import { join } from "node:path"; ⋮---- import { HOME, pkgRoot, ensureDir, copyDir, symlinkForce, writeVersionStamp, log } from "./util.js"; import { getVersion } from "./version.js"; import { ensureMcpServerInstalled, MCP SERVER PATH } from "./install-mcp-shared.js"; ⋮---- interface HermesHookEntry { matcher?: string; command: string; timeout?: number; } ⋮---- interface HermesConfig { mcp servers?: Record ; hooks?: Record ; hooks auto accept?: boolean; key: string : unknown; } ⋮---- function isHivemindHook entry: unknown : boolean ⋮---- function buildHookEntry bundleFile: string, timeout: numb… Evidence: `src/cli/install-hermes.ts` - **Install Openclaw** (source_file): import { existsSync, copyFileSync, rmSync, lstatSync } from "node:fs"; import { join } from "node:path"; import { HOME, pkgRoot, ensureDir, copyDir, writeVersionStamp, log, warn, symlinkForce } from "./util.js"; import { getVersion } from "./version.js"; import { ensureHivemindAllowlisted } from "../../harnesses/openclaw/src/setup-config.js"; ⋮---- export function installOpenclaw : void ⋮---- export function uninstallOpenclaw : void Evidence: `src/cli/install-openclaw.ts` - **Deeplake Pull** (source_file): import { execFileSync } from "node:child process"; import { createHash } from "node:crypto"; import { existsSync, mkdirSync, renameSync, writeFileSync } from "node:fs"; import { dirname, join } from "node:path"; ⋮---- function workTreeIdFor cwd: string : string ⋮---- import { loadConfig, type Config } from "../config.js"; import { DeeplakeApi } from "../deeplake-api.js"; import { sqlIdent, sqlStr } from "../utils/sql.js"; import { deriveProjectKey } from "../utils/repo-identity.js"; import { writeLastBuild, readLastBuild } from "./last-build.js"; import { appendHistoryEntry } from "./history.js"; import { computeSnapshotSha256, repoDir } from "./snapshot.js"; import type { GraphSnapshot } f… Evidence: `src/graph/deeplake-pull.ts` - **Deeplake Push** (source_file): import { createHash } from "node:crypto"; ⋮---- import { loadConfig, type Config } from "../config.js"; import { DeeplakeApi } from "../deeplake-api.js"; import { sqlIdent, sqlStr } from "../utils/sql.js"; import type { GraphSnapshot } from "./types.js"; ⋮---- export type PushOutcome = { kind: "skipped-no-auth" } { kind: "skipped-no-commit" } { kind: "skipped-disabled" } { kind: "inserted"; commitSha: string } { kind: "inserted-with-duplicate-race"; commitSha: string; rowCount: number } { kind: "already-current"; commitSha: string } { kind: "drift"; commitSha: string; localSha256: string; cloudSha256: string } { kind: "error"; message: string }; ⋮---- export interface PushDeps { loadConfig?… Evidence: `src/graph/deeplake-push.ts` - **Index** (source_file): import { extractTypeScript } from "./typescript.js"; import { extractJavaScript } from "./javascript.js"; import { extractPython } from "./python.js"; import { extractGo } from "./go.js"; import { extractRust } from "./rust.js"; import { extractJava } from "./java.js"; import { extractRuby } from "./ruby.js"; import { extractC } from "./c.js"; import { extractCpp } from "./cpp.js"; import type { FileExtraction } from "../types.js"; ⋮---- export function isPythonPath relativePath: string : boolean ⋮---- export function extractFile sourceCode: string, relativePath: string : FileExtraction Evidence: `src/graph/extract/index.ts` - **Ignore Config** (source_file): import { mkdirSync, readFileSync, writeFileSync } from "node:fs"; import { homedir } from "node:os"; import { join } from "node:path"; ⋮---- export interface GraphIgnoreConfig { ignoreDirs: string ; respectGitignore: boolean; } ⋮---- function defaultConfigObject : Record ⋮---- export function loadGraphIgnore deeplakeDir: string = join homedir , ".deeplake" : GraphIgnoreConfig ⋮---- export function ignoreDirSet config: GraphIgnoreConfig : Set ⋮---- export function pathHasIgnoredSegment relPath: string, ignore: Set : boolean Evidence: `src/graph/ignore-config.ts` - **Capture** (source_file): import { readStdin } from "../utils/stdin.js"; import { loadConfig, type Config } from "../config.js"; import { DeeplakeApi } from "../deeplake-api.js"; import { sqlStr } from "../utils/sql.js"; import { projectNameFromCwd } from "../utils/project-name.js"; import { log as log } from "../utils/debug.js"; import { buildSessionPath } from "../utils/session-path.js"; import { bumpTotalCount, loadTriggerConfig, shouldTrigger, tryAcquireLock, releaseLock, ensureSessionOwner, } from "./summary-state.js"; import { bundleDirFromImportMeta, spawnWikiWorker, wikiLog } from "./spawn-wiki-worker.js"; import { tryStopCounterTrigger } from "../skillify/triggers.js"; import { reactSkillOpt } from "./share… Evidence: `src/hooks/capture.ts` - The remaining 19 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`, `library/README.md`, `harnesses/openclaw/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`, `library/README.md`, `harnesses/openclaw/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. - **System Overview & Architecture**: importance `high` - source_paths: README.md, docs/ARCHITECTURE.md, package.json, src/config.ts, src/deeplake-api.ts - **Agent Integrations & Installer**: importance `high` - source_paths: src/cli/index.ts, src/cli/install-claude.ts, src/cli/install-codex.ts, src/cli/install-cursor.ts, src/cli/install-hermes.ts - **Session Capture, Hooks & Recall**: importance `high` - source_paths: src/hooks/session-start.ts, src/hooks/session-start-setup.ts, src/hooks/capture.ts, src/hooks/pre-tool-use.ts, src/hooks/session-end.ts - **Skillify, Summaries, Rules & Codebase Graph**: importance `high` - source_paths: src/skillify/skillify-worker.ts, src/skillify/skill-writer.ts, src/skillify/scope-config.ts, src/skillify/pull.ts, src/skillify/push.ts ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `64ab629cc9261ee8511eb327f2dfb05a3fee4b10` - inspected_files: `README.md`, `package.json`, `docs/ARCHITECTURE.md`, `docs/CAPTURE_TASKS.md`, `docs/EMBEDDINGS.md`, `docs/SKILLIFY.md`, `docs/SUMMARIES.md`, `src/cli/agents-md.ts`, `src/cli/auth.ts`, `src/cli/embeddings.ts`, `src/cli/index.ts`, `src/cli/install-claude.ts`, `src/cli/install-codex.ts`, `src/cli/install-cowork.ts`, `src/cli/install-cursor.ts`, `src/cli/install-hermes.ts`, `src/cli/install-mcp-shared.ts`, `src/cli/install-openclaw.ts`, `src/cli/install-pi.ts`, `src/cli/install-scan.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: Developers should check this installation risk before relying on the project: Recall UserPromptSubmit hook hangs (2s timeout) when embed-daemon.js launcher is missing from embed-deps despite embeddings enabled - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Recall UserPromptSubmit hook hangs (2s timeout) when embed-daemon.js launcher is missing from embed-deps despite embeddings enabled. Context: Observed when using node, macos - Why it matters: Developers may fail before the first successful local run: Recall UserPromptSubmit hook hangs (2s timeout) when embed-daemon.js launcher is missing from embed-deps despite embeddings enabled - Evidence: failure_mode_cluster:github_issue | https://github.com/activeloopai/hivemind/issues/296 - 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: v0.7.116 — fix(cli): don't crash when optional tree-sitter addon is absent (install P0) - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v0.7.116 — fix(cli): don't crash when optional tree-sitter addon is absent (install P0). Context: Observed during installation or first-run setup. - Why it matters: Upgrade or migration may change expected behavior: v0.7.116 — fix(cli): don't crash when optional tree-sitter addon is absent (install P0) - Evidence: failure_mode_cluster:github_release | https://github.com/activeloopai/hivemind/releases/tag/v0.7.116 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: 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/activeloopai/hivemind - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Runtime risk requires verification - Trigger: Developers should check this runtime risk before relying on the project: session-start: CREATE INDEX IF NOT EXISTS times out at 10s on busy sessions tables - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: session-start: CREATE INDEX IF NOT EXISTS times out at 10s on busy sessions tables. Context: Source discussion did not expose a precise runtime context. - Why it matters: Developers may hit a documented source-backed failure mode: session-start: CREATE INDEX IF NOT EXISTS times out at 10s on busy sessions tables - Evidence: failure_mode_cluster:github_issue | https://github.com/activeloopai/hivemind/issues/89 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: Runtime risk requires verification - Trigger: Developers should check this runtime risk before relying on the project: v0.7.117 — fix: stop wiki summary worker crash on long sessions - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v0.7.117 — fix: stop wiki summary worker crash on long sessions. Context: Source discussion did not expose a precise runtime context. - Why it matters: Upgrade or migration may change expected behavior: v0.7.117 — fix: stop wiki summary worker crash on long sessions - Evidence: failure_mode_cluster:github_release | https://github.com/activeloopai/hivemind/releases/tag/v0.7.117 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: Runtime risk requires verification - Trigger: Developers should check this runtime risk before relying on the project: v0.7.118 — fix: stop wiki summary worker crash on long sessions - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v0.7.118 — fix: stop wiki summary worker crash on long sessions. Context: Source discussion did not expose a precise runtime context. - Why it matters: Upgrade or migration may change expected behavior: v0.7.118 — fix: stop wiki summary worker crash on long sessions - Evidence: failure_mode_cluster:github_release | https://github.com/activeloopai/hivemind/releases/tag/v0.7.118 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.