# depthfusion - 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 depthfusion. 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_0003` supported 0.86 - **Users who want to bring professional workflows into a host AI**: The repo contains Skill documents. Evidence: `docs/designs/DepthFusion Design System/SKILL.md` Claim: `clm_0004` 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: `docs/designs/DepthFusion Design System/SKILL.md` Claim: `clm_0001` 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: `INSTALL.md`, `README.md`, `docs/install/mac-mlx-quickstart.md` Claim: `clm_0002` supported 0.86 ## How to Start - `git clone https://github.com/gregdigittal/depthfusion.git ~/depthfusion` Evidence: `INSTALL.md` Claim: `clm_0005` supported 0.86 - `pip install -e ".[vps-cpu]"` Evidence: `INSTALL.md` Claim: `clm_0006` supported 0.86, `clm_0021` supported 0.86 - `npx tauri build # Compile Rust + bundle installer` Evidence: `INSTALL.md` Claim: `clm_0007` supported 0.86 - `npx tauri build --target universal-apple-darwin` Evidence: `INSTALL.md` Claim: `clm_0008` supported 0.86 - `npx tauri signer generate -w ~/.tauri/depthfusion-signing.key` Evidence: `INSTALL.md` Claim: `clm_0009` supported 0.86 - `curl http://localhost:7300/health` Evidence: `INSTALL.md` Claim: `clm_0010` supported 0.86 - `curl -fsSL https://raw.githubusercontent.com/gregdigittal/depthfusion/main/scripts/install-mac-mlx.sh | bash` Evidence: `README.md` Claim: `clm_0011` supported 0.86 - `git clone https://github.com/gregdigittal/depthfusion.git ~/projects/depthfusion` Evidence: `README.md` Claim: `clm_0012` supported 0.86 - `pip install --upgrade pip` Evidence: `README.md` Claim: `clm_0013` supported 0.86 - `pip install -e '.[local]'` Evidence: `README.md` Claim: `clm_0014` supported 0.86, `clm_0020` 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_0003` 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: `docs/designs/DepthFusion Design System/SKILL.md` Claim: `clm_0004` 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: `docs/designs/DepthFusion Design System/SKILL.md` Claim: `clm_0001` 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: `INSTALL.md`, `README.md`, `docs/install/mac-mlx-quickstart.md` Claim: `clm_0002` 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: `INSTALL.md` Claim: `clm_0005` 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: `AGENTS.md`, `CLAUDE.md`, `docs/designs/DepthFusion Design System/SKILL.md` - **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. - **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: `INSTALL.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: `INSTALL.md`, `README.md`, `docs/install/mac-mlx-quickstart.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: `AGENTS.md`, `CLAUDE.md`, `docs/designs/DepthFusion Design System/SKILL.md` - **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: `INSTALL.md`, `README.md`, `docs/install/mac-mlx-quickstart.md` - **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: `BACKLOG.md`, `CHANGELOG.md`, `INSTALL.md`, `INSTALLATION.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_0029` inferred 0.45 - **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: `INSTALL.md`, `README.md`, `docs/install/mac-mlx-quickstart.md` Claim: `clm_0030` 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: `docs/designs/DepthFusion Design System/SKILL.md` Claim: `clm_0001` 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: `INSTALL.md`, `README.md`, `docs/install/mac-mlx-quickstart.md` Claim: `clm_0002` supported 0.86 ### Context Scale - Total files: 809 - Important-file coverage: 40/809 - Evidence index entries: 80 - Role / Skill entries: 1 ### 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 depthfusion, 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 depthfusion 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 depthfusion, 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 1 role / Skill / project-doc entries. - **depthfusion-design** (skill): Use this skill to generate well-branded interfaces and assets for DepthFusion the "Darkroom Amber" direction , either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping. Activation hint: When the user's task is highly relevant to the workflow described by “depthfusion-design”, use it for a pre-install experience first, then decide whether to install. Evidence: `docs/designs/DepthFusion Design System/SKILL.md` ## Evidence Index - Indexed 80 evidence entries. - **DepthFusion Documentation** (documentation): This directory contains reference documentation, architecture notes, and setup guides for the DepthFusion project. Evidence: `docs/README.md` - **CIQS Benchmark Methodology** (documentation): Owner: E-26 S-63 Benchmark Harness & Evaluation Data Source prompt doc: docs/performance-measurement-prompt.md ../performance-measurement-prompt.md Battery machine-readable : prompts/ciqs-battery.yaml prompts/ciqs-battery.yaml Scripts: scripts/ciqs harness.py ../../scripts/ciqs harness.py , scripts/ciqs summarise.py ../../scripts/ciqs summarise.py Evidence: `docs/benchmarks/README.md` - **Handoff: DepthFusion Landing — Darkroom Amber** (documentation): Handoff: DepthFusion Landing — Darkroom Amber Evidence: `docs/design/prototype/design_handoff_depthfusion_landing/README.md` - **DepthFusion Design System — "Darkroom Amber"** (documentation): DepthFusion Design System — "Darkroom Amber" Evidence: `docs/designs/DepthFusion Design System/readme.md` - **DepthFusion Desktop — UI Kit** (documentation): An interactive, high-fidelity recreation of the DepthFusion desktop app Tauri v2 · React 18 in the Darkroom Amber brand direction. It composes the design system's component primitives from ds bundle.js and is styled entirely by the root styles.css . Evidence: `docs/designs/DepthFusion Design System/ui_kits/depthfusion-desktop/README.md` - **DepthFusion Evaluation Sets** (documentation): Owner: E-26 S-64 Labelled Evaluation Data Consumed by: scripts/eval decision.py , scripts/eval dedup.py , scripts/eval negative.py Purpose: Labelled gold sets that turn capture-mechanism precision/recall claims from "asserted" into "measured". Evidence: `docs/eval-sets/README.md` - **Decision-Extraction Gold Set** (documentation): Target: S-45 AC-1 precision ≥ 0.80 on 50 labelled sessions Evidence: `docs/eval-sets/decision-extraction/README.md` - **Dedup Gold Set** (documentation): Target: S-49 AC-2 false-dedup rate ≤ 0.05 on 30 labelled near-duplicate pairs Evidence: `docs/eval-sets/dedup/README.md` - **Negative-Signal Gold Set** (documentation): Target: S-48 AC-2 false-negative rate ≤ 0.10 on 40 labelled examples Evidence: `docs/eval-sets/negative/README.md` - **DepthFusion Install Guides** (documentation): Pick the path that matches your target host. Evidence: `docs/install/README.md` - **DepthFusion v0.5 Planning Artefacts — Index** (documentation): DepthFusion v0.5 Planning Artefacts — Index Evidence: `docs/plans/v0.5/README.md` - **DepthFusion** (documentation): DepthFusion gives AI agents the institutional memory your team already has. Evidence: `README.md` - **DepthFusion Desktop App** (documentation): Tauri 2 + React + TypeScript + Tailwind CSS scaffold. Evidence: `app/README.md` - **Systemd User Services** (documentation): REST API server port 7300 . Requires depthfusion.env at ~/.claude/depthfusion.env . Evidence: `infra/systemd/README.md` - **Package** (package_manifest): { "name": "app", "private": true, "version": "2.1.1", "type": "module", "scripts": { "dev": "vite", "build": "tsc -b && vite build", "lint": "eslint .", "preview": "vite preview", "test": "vitest run", "generate:api": "npx openapi-typescript http://localhost:8000/openapi.json -o src/lib/api-client.ts" }, "dependencies": { "@tauri-apps/plugin-store": "^2.4.3", "lucide-react": "^1.21.0", "react": "^19.2.6", "react-dom": "^19.2.6" }, "overrides": { "esbuild": "^0.28.1" }, "devDependencies": { "@eslint/js": "^10.0.1", "@tailwindcss/vite": "^4.3.1", "@tauri-apps/api": "^2.11.1", "@tauri-apps/cli": "^2.11.3", "@tauri-apps/plugin-process": "^2", "@tauri-apps/plugin-updater": "^2", "@types/node": "… Evidence: `app/package.json` - **DepthFusion V2 — Installation Guide** (documentation): DepthFusion V2 — Installation Guide Evidence: `INSTALL.md` - **Where things are** (skill_instruction): Read the README.md file within this skill, and explore the other available files. If creating visual artifacts slides, mocks, throwaway prototypes, etc , copy assets out and create static HTML files for the user to view. If working on production code, you can copy assets and read the rules here to become an expert in designing with this brand. If the user invokes this skill without any other guidance, ask them what they want to build or design, ask some questions, and act as an expert designer who outputs HTML artifacts or production code, depending on the need. Evidence: `docs/designs/DepthFusion Design System/SKILL.md` - **AGENTS.md — DepthFusion** (documentation): Quick Reference - Stack: Python 3.10+ / numpy / pyyaml / structlog / optional: chromadb / rlms - VPS Path: /home/gregmorris/projects/depthfusion - Description: Depth-aware memory fusion for Claude Code — weighted retrieval, session attention, context routing, recursive LLMs Evidence: `AGENTS.md` - **Skill routing** (documentation): When the user's request matches an available skill, invoke it via the Skill tool. When in doubt, invoke the skill. Evidence: `CLAUDE.md` - **License** (source_file): Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files the "Software" , to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: Evidence: `LICENSE` - **DepthFusion V2 — Installation Guide** (documentation): DepthFusion V2 — Installation Guide Evidence: `INSTALLATION.md` - **Request to DepthFusion — confirm E-27 ready for agent-ops consumption** (documentation): Request to DepthFusion — confirm E-27 ready for agent-ops consumption Evidence: `docs/2026-05-05-to-depthfusion-confirm-e27-ready-for-consumption.md` - **MemPalace vs Saihai Deep DepthFusion + CLaRa — Comparative Analysis** (documentation): MemPalace vs Saihai Deep DepthFusion + CLaRa — Comparative Analysis Date: 2026-05-18 Analyst: Claude automated, via analysis prompt Deliverable: MEMPALACE DEPTHFUSION ANALYSIS.md Evidence: `docs/MEMPALACE_DEPTHFUSION_ANALYSIS.md` - **Add Stop Hook Local Mac** (documentation): Run these two commands in your Mac terminal, one at a time. Evidence: `docs/add-stop-hook.md` - **BI Tool Connectivity — DepthFusion Query API** (documentation): BI Tool Connectivity — DepthFusion Query API Evidence: `docs/bi-connectivity.md` - **Capability Matrix — DepthFusion V2 RBAC** (documentation): Capability Matrix — DepthFusion V2 RBAC Evidence: `docs/capability-matrix.md` - **DepthFusion CLI Reference** (documentation): Generated by cli-printing-press https://github.com/mvanhorn/cli-printing-press v4.11.0 from the DepthFusion REST API 29 endpoints . Compound commands discovery-audit , graph-inspect , batch-recall are hand-authored. Evidence: `docs/cli.md` - **DepthFusion — Project Context Document** (documentation): DepthFusion — Project Context Document Evidence: `docs/context.md` - **DepthFusion Session Handoff — 2026-05-18 S-122** (documentation): DepthFusion Session Handoff — 2026-05-18 S-122 Evidence: `docs/depthfusion-handoff-context.md` - **DepthFusion: Standalone vs SkillForge — Divergence & Alignment Analysis** (documentation): DepthFusion: Standalone vs SkillForge — Divergence & Alignment Analysis Evidence: `docs/depthfusion-skillforge-divergence.md` - **DepthFusion vs Alternatives — Final Comparison** (documentation): DepthFusion vs Alternatives — Final Comparison Date: 2026-03-28 Generated by: /goal autonomous optimization run Evidence: `docs/depthfusion-vs-alternatives-2026-03-28.md` - **E-65 On-Device Verification — macOS** (documentation): E-65 On-Device Verification — macOS Evidence: `docs/e65-on-device-verification.md` - **DepthFusion Honest Assessment** (documentation): DepthFusion Honest Assessment Date: 2026-03-28 Generated by: /goal autonomous optimization run Evidence: `docs/honest-assessment-2026-03-28.md` - **Auth requirements** (documentation): The HTTP MCP server lives in src/depthfusion/mcp/http server.py and exposes the MCP two-endpoint SSE transport on GET /sse and POST /messages . /health is unauthenticated, but /sse and /messages are protected by FastAPI's require principal dependency from src/depthfusion/api/auth.py . Evidence: `docs/mcp-http-server.md` - **DepthFusion — Claude Instance Performance Measurement Framework** (documentation): DepthFusion — Claude Instance Performance Measurement Framework Date: 2026-03-28 Status: ACTIVE Evidence: `docs/performance-measurement-prompt.md` - **DepthFusion — Power User Research Report** (documentation): DepthFusion — Power User Research Report Date: 2026-03-28 Source: /goal autonomous optimization run Evidence: `docs/power-user-research-2026-03-28.md` - **Project Sync — DepthFusion** (documentation): DepthFusion can automatically sync project context BACKLOG.md, CLAUDE.md, git log to its knowledge base when a Claude Code session ends. Evidence: `docs/project-sync.md` - **DepthFusion Release Process** (documentation): 1. All tests pass: 2. Type checking clean: 3. Linting clean: 4. C1-C11 compatibility GREEN: 5. README.md updated version table, MCP tools table, feature flags 6. BACKLOG.md updated relevant items marked x 7. CIQS benchmark runs completed 3 runs, documented in docs/benchmarks/ Evidence: `docs/release-process.md` - **DepthFusion HNSW Implementation Handoff** (documentation): DepthFusion HNSW Implementation Handoff Evidence: `docs/ruflo-mod.md` - **Show HN: DepthFusion — Shared memory for AI agent teams MIT, self-hosted** (documentation): Show HN: DepthFusion — Shared memory for AI agent teams MIT, self-hosted Evidence: `docs/show-hn-post.md` - **DepthFusion → SkillForge Integration Plan** (documentation): DepthFusion → SkillForge Integration Plan Date: 2026-03-28 Status: AWAITING APPROVAL Evidence: `docs/skillforge-integration-plan.md` - **DepthFusion Sync Guide** (documentation): Note: This doc describes V1 behavior. V2 behavior is documented in docs/v2/admin-runbooks.md §4 Backup and Restore . V2 uses admin-managed backup scripts and database checkpoints rather than rsync-based file sync. If you are running the v2-enterprise branch, refer to the V2 admin runbooks instead. Evidence: `docs/sync-guide.md` - **Tauri Updater Signing Key Setup** (documentation): DepthFusion uses Ed25519 signatures to verify update bundles before installation. The public key is embedded in the shipped binary tauri.conf.json → plugins.updater.pubkey . The corresponding private key must be stored as a GitHub Actions secret. Evidence: `app/docs/updater-signing-key-setup.md` - **CIQS Scoring Template - local / run 1** (documentation): CIQS Scoring Template - local / run 1 Evidence: `docs/benchmarks/2026-05-02-local-run1-scoring.md` - **CIQS Scoring Template - local / run 2** (documentation): CIQS Scoring Template - local / run 2 Evidence: `docs/benchmarks/2026-05-02-local-run2-scoring.md` - **CIQS Scoring Template - local / run 3** (documentation): CIQS Scoring Template - local / run 3 Evidence: `docs/benchmarks/2026-05-02-local-run3-scoring.md` - **CIQS Scoring Template - vps-cpu / run 1** (documentation): CIQS Scoring Template - vps-cpu / run 1 Evidence: `docs/benchmarks/2026-05-02-vps-cpu-run1-scoring.md` - **CIQS Scoring Template - vps-cpu / run 2** (documentation): CIQS Scoring Template - vps-cpu / run 2 Evidence: `docs/benchmarks/2026-05-02-vps-cpu-run2-scoring.md` - **CIQS Scoring Template - vps-cpu / run 3** (documentation): CIQS Scoring Template - vps-cpu / run 3 Evidence: `docs/benchmarks/2026-05-02-vps-cpu-run3-scoring.md` - **CIQS Scoring Template - vps-gpu / run 1** (documentation): CIQS Scoring Template - vps-gpu / run 1 Evidence: `docs/benchmarks/2026-05-02-vps-gpu-run1-scoring.md` - **CIQS Scoring Template - vps-gpu / run 2** (documentation): CIQS Scoring Template - vps-gpu / run 2 Evidence: `docs/benchmarks/2026-05-02-vps-gpu-run2-scoring.md` - **CIQS Scoring Template - vps-gpu / run 3** (documentation): CIQS Scoring Template - vps-gpu / run 3 Evidence: `docs/benchmarks/2026-05-02-vps-gpu-run3-scoring.md` - **DepthFusion — Post-Dogfood Benchmark Pass** (documentation): DepthFusion — Post-Dogfood Benchmark Pass Evidence: `docs/benchmarks/2026-05-15-post-dogfood.md` - **CIQS Scoring Template - local / run 1** (documentation): CIQS Scoring Template - local / run 1 Evidence: `docs/benchmarks/2026-05-16-local-run1-scoring.md` - **CIQS Scoring Template - local / run 2** (documentation): CIQS Scoring Template - local / run 2 Evidence: `docs/benchmarks/2026-05-16-local-run2-scoring.md` - **CIQS Scoring Template - local / run 3** (documentation): CIQS Scoring Template - local / run 3 Evidence: `docs/benchmarks/2026-05-16-local-run3-scoring.md` - **CIQS Cat A Scoring — Post-Fix Evaluation** (documentation): CIQS Cat A Scoring — Post-Fix Evaluation Date: 2026-05-17 DepthFusion branch: main post S-115 retrieval fixes Evidence: `docs/benchmarks/2026-05-17-ciqs-a-post-fix-scoring.md` - **CIQS Cat A — Fusion Gates Comparison gates-off vs gates-on** (documentation): CIQS Cat A — Fusion Gates Comparison gates-off vs gates-on Evidence: `docs/benchmarks/2026-05-18-gates-comparison.md` - **Linear Blend vs RRF+Vector — Cat A Retrieval Analysis** (documentation): Linear Blend vs RRF+Vector — Cat A Retrieval Analysis Evidence: `docs/benchmarks/2026-05-18-linear-blend-analysis.md` - **CIQS Scoring Template - local / run 1** (documentation): CIQS Scoring Template - local / run 1 Evidence: `docs/benchmarks/2026-05-18-local-run1-scoring.md` - The remaining 20 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: `docs/README.md`, `docs/benchmarks/README.md`, `docs/design/prototype/design_handoff_depthfusion_landing/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: `docs/README.md`, `docs/benchmarks/README.md`, `docs/design/prototype/design_handoff_depthfusion_landing/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. - **Project Overview & Installation**: importance `high` - source_paths: README.md, INSTALL.md, INSTALLATION.md, setup.sh, scripts/install.sh - **Core Architecture: Retrieval, Fusion & Cognitive Layer**: importance `high` - source_paths: src/depthfusion/retrieval/bm25.py, src/depthfusion/retrieval/hnsw_store.py, src/depthfusion/retrieval/hybrid.py, src/depthfusion/retrieval/reranker.py, src/depthfusion/retrieval/acl_verifier.py - **Tauri Desktop App & 30-Tool MCP Surface**: importance `high` - source_paths: app/src/App.tsx, app/src/DashboardPage.tsx, app/src/SearchPage.tsx, app/src/GraphPage.tsx, app/src/DocumentViewer.tsx - **Deployment, Security, Operations & Extensibility**: importance `high` - source_paths: src/depthfusion/identity/oidc_client.py, src/depthfusion/identity/device_keychain.py, src/depthfusion/identity/device_registry.py, src/depthfusion/identity/device_lease.py, src/depthfusion/identity/token_validator.py ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `f9e3a0a8ee30180afcdb9d190ddc8f68194fc8a0` - inspected_files: `README.md`, `pyproject.toml`, `uv.lock`, `docs/2026-05-05-to-depthfusion-confirm-e27-ready-for-consumption.md`, `docs/Account_synch/AGENTS.md`, `docs/Account_synch/CLAUDE.md`, `docs/Account_synch/depthfusion-build-plan.md`, `docs/Account_synch/depthfusion-mega-prompt.md`, `docs/Account_synch/depthfusion-sprint-backlog.md`, `docs/Account_synch/master-continuity-document.md`, `docs/MEMPALACE_DEPTHFUSION_ANALYSIS.md`, `docs/README.md`, `docs/add-stop-hook.md`, `docs/api/metabase-dashboard.json`, `docs/api/query-api.yaml`, `docs/benchmarks/2026-05-02-local-run1-scoring.md`, `docs/benchmarks/2026-05-02-local-run2-scoring.md`, `docs/benchmarks/2026-05-02-local-run3-scoring.md`, `docs/benchmarks/2026-05-02-vps-cpu-run1-scoring.md`, `docs/benchmarks/2026-05-02-vps-cpu-run2-scoring.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: 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/gregdigittal/depthfusion - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: 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/gregdigittal/depthfusion - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: Security or permission risk requires verification - Trigger: no_demo - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: risks.scoring_risks | https://github.com/gregdigittal/depthfusion - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Maintenance risk requires verification - Trigger: issue_or_pr_quality=unknown。 - 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/gregdigittal/depthfusion - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: Maintenance risk requires verification - Trigger: release_recency=unknown。 - 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/gregdigittal/depthfusion - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.