# yantrikdb-server - Doramagic AI Context Pack

> 定位：安装前体验与判断资产。它帮助宿主 AI 有一个好的开始，但不代表已经安装、执行或验证目标项目。

## 充分原则

- **充分原则，不是压缩原则**：AI Context Pack 应该充分到让宿主 AI 在开工前理解项目价值、能力边界、使用入口、风险和证据来源；它可以分层组织，但不以最短摘要为目标。
- **压缩策略**：只压缩噪声和重复内容，不压缩会影响判断和开工质量的上下文。

## 给宿主 AI 的使用方式

你正在读取 Doramagic 为 yantrikdb-server 编译的 AI Context Pack。请把它当作开工前上下文：帮助用户理解适合谁、能做什么、如何开始、哪些必须安装后验证、风险在哪里。不要声称你已经安装、运行或执行了目标项目。

## Claim 消费规则

- **事实来源**：Repo Evidence + Claim/Evidence Graph；Human Wiki 只提供显著性、术语和叙事结构。
- **事实最低状态**：`supported`
- `supported`：可以作为项目事实使用，但回答中必须引用 claim_id 和证据路径。
- `weak`：只能作为低置信度线索，必须要求用户继续核实。
- `inferred`：只能用于风险提示或待确认问题，不能包装成项目事实。
- `unverified`：不得作为事实使用，应明确说证据不足。
- `contradicted`：必须展示冲突来源，不得替用户强行选择一个版本。

## 它最适合谁

- **AI 研究者或研究型 Agent 构建者**：README 明确围绕研究、实验或论文工作流展开。 证据：`README.md` Claim：`clm_0002` supported 0.86
- **正在使用 Claude/Codex/Cursor/Gemini 等宿主 AI 的开发者**：README 或插件配置提到多个宿主 AI。 证据：`README.md` Claim：`clm_0003` supported 0.86

## 它能做什么

- **命令行启动或安装流程**（需要安装后验证）：项目文档中存在可执行命令，真实使用需要在本地或宿主环境中运行这些命令。 证据：`README.md` Claim：`clm_0001` supported 0.86

## 怎么开始

- `pip install yantrikdb-mcp` 证据：`README.md` Claim：`clm_0004` supported 0.86
- `curl -X POST http://localhost:7438/v1/remember -d '{"text":"hello"}'` 证据：`README.md` Claim：`clm_0005` supported 0.86
- `pip install yantrikdb` 证据：`README.md` Claim：`clm_0004` supported 0.86, `clm_0006` supported 0.86

## 继续前判断卡

- **当前建议**：需要管理员/安全审批
- **为什么**：继续前可能涉及密钥、账号、外部服务或敏感上下文，建议先经过管理员或安全审批。

### 30 秒判断

- **现在怎么做**：需要管理员/安全审批
- **最小安全下一步**：先跑 Prompt Preview；若涉及凭证或企业环境，先审批再试装
- **先别相信**：角色质量和任务匹配不能直接相信。
- **继续会触碰**：角色选择偏差、命令执行、本地环境或项目文件

### 现在可以相信

- **适合人群线索：AI 研究者或研究型 Agent 构建者**（supported）：有 supported claim 或项目证据支撑，但仍不等于真实安装效果。 证据：`README.md` Claim：`clm_0002` supported 0.86
- **适合人群线索：正在使用 Claude/Codex/Cursor/Gemini 等宿主 AI 的开发者**（supported）：有 supported claim 或项目证据支撑，但仍不等于真实安装效果。 证据：`README.md` Claim：`clm_0003` supported 0.86
- **能力存在：命令行启动或安装流程**（supported）：可以相信项目包含这类能力线索；是否适合你的具体任务仍要试用或安装后验证。 证据：`README.md` Claim：`clm_0001` supported 0.86
- **存在 Quick Start / 安装命令线索**（supported）：可以相信项目文档出现过启动或安装入口；不要因此直接在主力环境运行。 证据：`README.md` Claim：`clm_0004` supported 0.86

### 现在还不能相信

- **角色质量和任务匹配不能直接相信。**（unverified）：角色库证明有很多角色，不证明每个角色都适合你的具体任务，也不证明角色能产生高质量结果。
- **不能把角色文案当成真实执行能力。**（unverified）：安装前只能判断角色描述和任务画像是否匹配，不能证明它能在宿主 AI 里完成任务。
- **真实输出质量不能在安装前相信。**（unverified）：Prompt Preview 只能展示引导方式，不能证明真实项目中的结果质量。
- **宿主 AI 版本兼容性不能在安装前相信。**（unverified）：Claude、Cursor、Codex、Gemini 等宿主加载规则和版本差异必须在真实环境验证。
- **不会污染现有宿主 AI 行为，不能直接相信。**（inferred）：Skill、plugin、AGENTS/CLAUDE/GEMINI 指令可能改变宿主 AI 的默认行为。
- **可安全回滚不能默认相信。**（unverified）：除非项目明确提供卸载和恢复说明，否则必须先在隔离环境验证。
- **真实安装后是否与用户当前宿主 AI 版本兼容？**（unverified）：兼容性只能通过实际宿主环境验证。
- **项目输出质量是否满足用户具体任务？**（unverified）：安装前预览只能展示流程和边界，不能替代真实评测。

### 继续会触碰什么

- **角色选择偏差**：用户对任务应该由哪个专家角色处理的判断。 原因：选错角色会让 AI 从错误专业视角回答，浪费时间或误导决策。
- **命令执行**：包管理器、网络下载、本地插件目录、项目配置或用户主目录。 原因：运行第一条命令就可能产生环境改动；必须先判断是否值得跑。 证据：`README.md`
- **本地环境或项目文件**：安装结果、插件缓存、项目配置或本地依赖目录。 原因：安装前无法证明写入范围和回滚方式，需要隔离验证。 证据：`README.md`
- **环境变量 / API Key**：项目入口文档明确出现 API key、token、secret 或账号凭证配置。 原因：如果真实安装需要凭证，应先使用测试凭证并经过权限/合规判断。 证据：`README.md`
- **宿主 AI 上下文**：AI Context Pack、Prompt Preview、Skill 路由、风险规则和项目事实。 原因：导入上下文会影响宿主 AI 后续判断，必须避免把未验证项包装成事实。

### 最小安全下一步

- **先跑 Prompt Preview**：先用交互式试用验证任务画像和角色匹配，不要先导入整套角色库。（适用：任何项目都适用，尤其是输出质量未知时。）
- **只在隔离目录或测试账号试装**：避免安装命令污染主力宿主 AI、真实项目或用户主目录。（适用：存在命令执行、插件配置或本地写入线索时。）
- **不要使用真实生产凭证**：环境变量/API key 一旦进入宿主或工具链，可能产生账号和合规风险。（适用：出现 API、TOKEN、KEY、SECRET 等环境线索时。）
- **安装后只验证一个最小任务**：先验证加载、兼容、输出质量和回滚，再决定是否深用。（适用：准备从试用进入真实工作流时。）

### 退出方式

- **保留安装前状态**：记录原始宿主配置和项目状态，后续才能判断是否可恢复。
- **保留原始角色选择记录**：如果输出偏题，可以回到任务画像阶段重新选择角色，而不是继续沿着错误角色推进。
- **记录安装命令和写入路径**：没有明确卸载说明时，至少要知道哪些目录或配置需要手动清理。
- **准备撤销测试 API key 或 token**：测试凭证泄露或误用时，可以快速止损。
- **如果没有回滚路径，不进入主力环境**：不可回滚是继续前阻断项，不应靠信任或运气继续。

## 哪些只能预览

- 解释项目适合谁和能做什么
- 基于项目文档演示典型对话流程
- 帮助用户判断是否值得安装或继续研究

## 哪些必须安装后验证

- 真实安装 Skill、插件或 CLI
- 执行脚本、修改本地文件或访问外部服务
- 验证真实输出质量、性能和兼容性

## 边界与风险判断卡

- **把安装前预览误认为真实运行**：用户可能高估项目已经完成的配置、权限和兼容性验证。 处理方式：明确区分 prompt_preview_can_do 与 runtime_required。 Claim：`clm_0007` inferred 0.45
- **命令执行会修改本地环境**：安装命令可能写入用户主目录、宿主插件目录或项目配置。 处理方式：先在隔离环境或测试账号中运行。 证据：`README.md` Claim：`clm_0008` supported 0.86
- **待确认**：真实安装后是否与用户当前宿主 AI 版本兼容？。原因：兼容性只能通过实际宿主环境验证。
- **待确认**：项目输出质量是否满足用户具体任务？。原因：安装前预览只能展示流程和边界，不能替代真实评测。
- **待确认**：安装命令是否需要网络、权限或全局写入？。原因：这影响企业环境和个人环境的安装风险。

## 开工前工作上下文

### 加载顺序

- 先读取 how_to_use.host_ai_instruction，建立安装前判断资产的边界。
- 读取 claim_graph_summary，确认事实来自 Claim/Evidence Graph，而不是 Human Wiki 叙事。
- 再读取 intended_users、capabilities 和 quick_start_candidates，判断用户是否匹配。
- 需要执行具体任务时，优先查 role_skill_index，再查 evidence_index。
- 遇到真实安装、文件修改、网络访问、性能或兼容性问题时，转入 risk_card 和 boundaries.runtime_required。

### 任务路由

- **命令行启动或安装流程**：先说明这是安装后验证能力，再给出安装前检查清单。 边界：必须真实安装或运行后验证。 证据：`README.md` Claim：`clm_0001` supported 0.86

### 上下文规模

- 文件总数：413
- 重要文件覆盖：40/413
- 证据索引条目：80
- 角色 / Skill 条目：58

### 证据不足时的处理

- **missing_evidence**：说明证据不足，要求用户提供目标文件、README 段落或安装后验证记录；不要补全事实。
- **out_of_scope_request**：说明该任务超出当前 AI Context Pack 证据范围，并建议用户先查看 Human Manual 或真实安装后验证。
- **runtime_request**：给出安装前检查清单和命令来源，但不要替用户执行命令或声称已执行。
- **source_conflict**：同时展示冲突来源，标记为待核实，不要强行选择一个版本。

## Prompt Recipes

### 适配判断

- 目标：判断这个项目是否适合用户当前任务。
- 预期输出：适配结论、关键理由、证据引用、安装前可预览内容、必须安装后验证内容、下一步建议。

```text
请基于 yantrikdb-server 的 AI Context Pack，先问我 3 个必要问题，然后判断它是否适合我的任务。回答必须包含：适合谁、能做什么、不能做什么、是否值得安装、证据来自哪里。所有项目事实必须引用 evidence_refs、source_paths 或 claim_id。
```

### 安装前体验

- 目标：让用户在安装前感受核心工作流，同时避免把预览包装成真实能力或营销承诺。
- 预期输出：一段带边界标签的体验剧本、安装后验证清单和谨慎建议；不含真实运行承诺或强营销表述。

```text
请把 yantrikdb-server 当作安装前体验资产，而不是已安装工具或真实运行环境。

请严格输出四段：
1. 先问我 3 个必要问题。
2. 给出一段“体验剧本”：用 [安装前可预览]、[必须安装后验证]、[证据不足] 三种标签展示它可能如何引导工作流。
3. 给出安装后验证清单：列出哪些能力只有真实安装、真实宿主加载、真实项目运行后才能确认。
4. 给出谨慎建议：只能说“值得继续研究/试装”“先补充信息后再判断”或“不建议继续”，不得替项目背书。

硬性边界：
- 不要声称已经安装、运行、执行测试、修改文件或产生真实结果。
- 不要写“自动适配”“确保通过”“完美适配”“强烈建议安装”等承诺性表达。
- 如果描述安装后的工作方式，必须使用“如果安装成功且宿主正确加载 Skill，它可能会……”这种条件句。
- 体验剧本只能写成“示例台词/假设流程”：使用“可能会询问/可能会建议/可能会展示”，不要写“已写入、已生成、已通过、正在运行、正在生成”。
- Prompt Preview 不负责给安装命令；如用户准备试装，只能提示先阅读 Quick Start 和 Risk Card，并在隔离环境验证。
- 所有项目事实必须来自 supported claim、evidence_refs 或 source_paths；inferred/unverified 只能作风险或待确认项。

```

### 角色 / Skill 选择

- 目标：从项目里的角色或 Skill 中挑选最匹配的资产。
- 预期输出：候选角色或 Skill 列表，每项包含适用场景、证据路径、风险边界和是否需要安装后验证。

```text
请读取 role_skill_index，根据我的目标任务推荐 3-5 个最相关的角色或 Skill。每个推荐都要说明适用场景、可能输出、风险边界和 evidence_refs。
```

### 风险预检

- 目标：安装或引入前识别环境、权限、规则冲突和质量风险。
- 预期输出：环境、权限、依赖、许可、宿主冲突、质量风险和未知项的检查清单。

```text
请基于 risk_card、boundaries 和 quick_start_candidates，给我一份安装前风险预检清单。不要替我执行命令，只说明我应该检查什么、为什么检查、失败会有什么影响。
```

### 宿主 AI 开工指令

- 目标：把项目上下文转成一次对话开始前的宿主 AI 指令。
- 预期输出：一段边界明确、证据引用明确、适合复制给宿主 AI 的开工前指令。

```text
请基于 yantrikdb-server 的 AI Context Pack，生成一段我可以粘贴给宿主 AI 的开工前指令。这段指令必须遵守 not_runtime=true，不能声称项目已经安装、运行或产生真实结果。
```

## 角色 / Skill 索引

- 共索引 58 个角色 / Skill / 项目文档条目。

- **48-hour demand test — execution plan**（project_doc）：48-hour demand test — execution plan 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/demand-test/README.md`
- **Skill as Memory, Not Document — Zenodo Deposit Bundle**（project_doc）：Skill as Memory, Not Document — Zenodo Deposit Bundle 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/papers/zenodo-bundle/README.md`
- **Phase 3A — hidden-constraint recovery**（project_doc）：Phase 3A — hidden-constraint recovery 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/phase3/README.md`
- **Phase 3B — hidden-constraint recovery, scaled up**（project_doc）：Phase 3B — hidden-constraint recovery, scaled up 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/phase3b/README.md`
- **Phase 3C — memory probe with supersession, alias, and indirect retrieval pressure**（project_doc）：⚠️ METHODOLOGY CORRECTION 2026-04-19 The C structured condition in this writeup used memory sim.py memory sim.py — a Python list of key, value, session tuples with Dice word-overlap retrieval. It is NOT yantrikdb . It has no embeddings, no HNSW, no think loop, no multi-signal scoring, no conflict scan. Calling this condition "structured memory" in the original writeup was misleading. A Phase 3E rerun with the actual… 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/phase3c/README.md`
- **Phase 3D — LongMemEval head-to-head**（project_doc）：⚠️ METHODOLOGY CORRECTION 2026-04-19 All L1/L3/L4 experiments on this page ran against ../phase3c/memory sim.py ../phase3c/memory sim.py — a Python list of key, value, session tuples with Dice word-overlap retrieval. That is not yantrikdb. It has no embeddings, no HNSW, no think loop, no multi-signal scoring, no conflict scan. The "null result on RFC 006" conclusion in this writeup was therefore drawn from a strippe… 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/phase3d/README.md`
- **YantrikDB**（project_doc）：⚠ Correction notice 2026-04-19 : Phase 3 benchmark writeups committed earlier today docs/phase3a/ , docs/phase3b/ , docs/phase3c/ , docs/phase3d/ used a Python simulator for the "structured memory" condition — NOT the actual yantrikdb engine. Rerun with real yantrikdb is in docs/phase3e/ docs/phase3e/ . Full audit trail in CORRECTIONS.md CORRECTIONS.md . Full corrected findings post coming 2026-04-20. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`README.md`
- **LongMemEval Benchmark for YantrikDB**（project_doc）：LongMemEval Benchmark for YantrikDB 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`benchmarks/longmemeval/README.md`
- **Skill-Store Recall Benchmark**（project_doc）：End-to-end retrieval-quality + latency benchmark on a single-node YantrikDB. Measures whether YantrikDB is fit-for-purpose as a skill substrate for agent systems: thousands of typed knowledge records skills, lessons, procedures , with a mix of broad "what skills apply here?" and sharp "find this specific skill" queries. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`benchmarks/skill_recall/README.md`
- **yantrikdb-protocol**（project_doc）：Wire protocol codec for YantrikDB https://github.com/yantrikos/yantrikdb-server — a cognitive memory database. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`crates/yantrikdb-protocol/README.md`
- **yantrikdb-server**（project_doc）：Multi-tenant cognitive memory database server. Wire protocol + HTTP gateway, built-in embeddings, automatic replication and failover. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`crates/yantrikdb-server/README.md`
- **yantrikdb-witness**（project_doc）：Vote-only daemon for YantrikDB https://github.com/yantrikos/yantrikdb-server clusters. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`crates/yantrikdb-witness/README.md`
- **yql**（project_doc）：Interactive REPL client for YantrikDB https://github.com/yantrikos/yantrikdb-server — like psql for cognitive memory. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`crates/yql/README.md`
- **Kubernetes Deployment**（project_doc）：bash 1. Update the cluster secret kubectl create secret generic yantrikdb-cluster-secret \ --from-literal=cluster-secret="$ openssl rand -hex 32 " 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`deploy/kubernetes/README.md`
- **YantrikDB Server — Design Spec**（project_doc）：Output of 3-round brainstorm between GPT-5.4, DeepSeek, and Claude April 5, 2026 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`DESIGN.md`
- **YantrikDB MCP Server Redesign — Session Brief**（project_doc）：YantrikDB MCP Server Redesign — Session Brief 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`MCP_REDESIGN.md`
- **YantrikDB Server**（project_doc）：A cognitive memory database server with native wire protocol, HTTP gateway, built-in embeddings, automatic failover, and Raft-lite replication. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`SERVER_README.md`
- **yantrikdb-server HTTP error codes**（project_doc）：Every error response across /v1/ carries a structured envelope: 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/error-codes.md`
- **Three LLMs at a Table: How YantrikDB v0.8.11 Got Designed**（project_doc）：Three LLMs at a Table: How YantrikDB v0.8.11 Got Designed 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/blog/2026-05-01-how-v0.8.11-got-designed.md`
- **GitHub Discussion — post this FIRST**（project_doc）：GitHub Discussion — post this FIRST 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/demand-test/1_github_discussion.md`
- **Hacker News post**（project_doc）：When: Tuesday–Thursday, 8–10 am PT is the golden window most eyeballs, front page chance 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/demand-test/2_hn_post.md`
- **r/LocalLLaMA post**（project_doc）：Where: Subreddit culture: very technical, loves data and local-model experiments, friendly to open-source authors who lead with results and not pitch. Qwen 3.6 + 2×3090 Ti is exactly their demographic. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/demand-test/3_reddit_localllama.md`
- **r/LangChain post**（project_doc）：Where: Subreddit culture: smaller ~50k , conversational, practical, LangChain-flavored. People here are SHIPPING agent apps. Memory is a live pain. Leave the theory; lead with concrete failure modes and mitigations. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/demand-test/4_reddit_langchain.md`
- **X / Twitter thread**（project_doc）：Where: your personal account + @yantrikdb if it exists 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/demand-test/5_x_thread.md`
- **Reply snippets — F1 / F2 / F3 framings ready to paste into comments**（project_doc）：Reply snippets — F1 / F2 / F3 framings ready to paste into comments 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/demand-test/6_reply_snippets.md`
- **Response tracker — 48-hour window**（project_doc）：Post start time fill in when you post : YYYY-MM-DD HH:MM UTC T+48 hour deadline compute from start : YYYY-MM-DD HH:MM UTC 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/demand-test/7_response_tracker.md`
- **Post-mortem template — use ONLY if demand test falls below threshold**（project_doc）：Post-mortem template — use ONLY if demand test falls below threshold 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/demand-test/8_postmortem_template.md`
- **Correction Notice — to post TODAY**（project_doc）：Where: GitHub Discussion on yantrikos/yantrikdb-server, pinned if possible. Also: add a banner to the top of README.md pointing to CORRECTIONS.md Tomorrow: full findings post with the actual corrected numbers 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/demand-test/correction_notice_today.md`
- **Pre-registered decision rule — DO NOT OPEN BEFORE T+48h**（project_doc）：Pre-registered decision rule — DO NOT OPEN BEFORE T+48h 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/demand-test/decision_rule.md`
- **Engine PR draft — deterministic mutation APIs record with rid + friends**（project_doc）：Engine PR draft — deterministic mutation APIs record with rid + friends 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/engine-prs/0001-deterministic-mutation-apis.md`
- **Migration: v0.7.x → v0.8.0**（project_doc）：This guide is for operators upgrading a YantrikDB-server deployment from a 0.7.x release to v0.8.0 . 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/migration/v0.7_to_v0.8.md`
- **Cluster client routing — interim runbook pre-PR-6**（project_doc）：Cluster client routing — interim runbook pre-PR-6 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/operations/cluster-routing.md`
- **Skill as Memory, Not Document: A Database-Native Substrate for Agent Skill Catalogs**（project_doc）：Skill as Memory, Not Document: A Database-Native Substrate for Agent Skill Catalogs 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/papers/skill-substrate-experience-report-v4.md`
- **Skill as Memory, Not Document: A Database-Native Substrate for Agent Skill Catalogs**（project_doc）：Skill as Memory, Not Document: A Database-Native Substrate for Agent Skill Catalogs 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/papers/zenodo-bundle/skill-substrate-experience-report-v4-source.md`
- **FieldOps — Product Context Brief**（project_doc）：FieldOps is an internal tooling platform used by our field operations team surveyors, drillers, inspectors . We are rebuilding the platform from scratch because the current VB.NET-based tool has accumulated fourteen years of patches and nobody on the current team can reliably modify it. The rewrite target is launch in Q3 next year, with a soft internal rollout to two teams first. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/phase3/specs/01_product_context.md`
- **FieldOps — Infrastructure Constraints**（project_doc）：FieldOps — Infrastructure Constraints 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/phase3/specs/02_infrastructure.md`
- **FieldOps — Security & Compliance Brief**（project_doc）：FieldOps — Security & Compliance Brief 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/phase3/specs/03_security_compliance.md`
- **Oracle note for FieldOps architecture proposal**（project_doc）：Oracle note for FieldOps architecture proposal 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/phase3/specs/oracle_note.md`
- **FieldOps — Product & Team Context**（project_doc）：FieldOps is the internal tooling used by our field operations team — surveyors, drillers, inspectors — across roughly 260 users. The current platform is a VB.NET tool first shipped in 2011, then patched heavily through three different vendor handovers. By 2023 the codebase had accumulated about fourteen years of architectural debt and nobody on the current internal team can reliably extend it without breaking someth… 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/phase3b/specs/01_product_context.md`
- **FieldOps — Infrastructure Constraints**（project_doc）：FieldOps — Infrastructure Constraints 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/phase3b/specs/02_infrastructure.md`
- **FieldOps — Security & Compliance**（project_doc）：The compliance desk has reviewed this program and approved use of our self-hosted Keycloak deployment at keycloak.corp.internal as the identity plane. Two other FieldOps-adjacent tools already federate into that Keycloak — the permit-intake service and the asset-catalog service — and the realm, roles, and group structure are already in place. External identity providers — Auth0, Okta, Google Workspace as an IdP, Azu… 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/phase3b/specs/03_security_compliance.md`
- **Oracle note for FieldOps architecture proposal 15 constraints**（project_doc）：Oracle note for FieldOps architecture proposal 15 constraints 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/phase3b/specs/oracle_note.md`
- **Phase 3D L4 — synthetic scaling test**（project_doc）：Phase 3D L4 — synthetic scaling test 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/phase3d/L4_scaling_writeup.md`
- **DRAFT — NOT PUBLISHED YET**（project_doc）：Status: draft, written 2026-04-19. Do not publish before one sleep + morning review. Per pre-registered gate in ../demand-test/decision rule.md ../demand-test/decision rule.md . 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/phase3e/FINDINGS_POST_DRAFT.md`
- **GitHub Discussion — DRAFT, not posted**（project_doc）：GitHub Discussion — DRAFT, not posted 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/phase3e/channel_drafts/1_github_discussion.md`
- **Hacker News post — DRAFT, not posted**（project_doc）：Hacker News post — DRAFT, not posted 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/phase3e/channel_drafts/2_hn_post.md`
- **r/LocalLLaMA post — DRAFT, not posted**（project_doc）：r/LocalLLaMA post — DRAFT, not posted 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/phase3e/channel_drafts/3_reddit_localllama.md`
- **X / Twitter thread — DRAFT, not posted**（project_doc）：X / Twitter thread — DRAFT, not posted 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/phase3e/channel_drafts/4_x_thread.md`
- **Pre-registration — Scenario 2 v3 pipeline run**（project_doc）：Pre-registration — Scenario 2 v3 pipeline run 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/phase3e/scenario2/prereg.md`
- **RFC 006 — Context-Aware Conflict Detection**（project_doc）：RFC 006 — Context-Aware Conflict Detection 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/rfcs/006-context-aware-conflict-detection.md`
- **RFC 008 HTTP Surface**（project_doc）：The five HTTP endpoints that expose the Warrant Flow substrate claims with source lineage, mobility state, contest state, cognitive moves to agents and MCP clients. Added in yantrikdb-server commit f245049; requires yantrikdb core at branch main ≥ commit cd41207, post-M10 . 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/rfcs/rfc_008_http_surface.md`
- **RFC 009 — Recall Admission Control & API Versioning**（project_doc）：RFC 009 — Recall Admission Control & API Versioning 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/rfcs/rfc_009_recall_admission_control.md`
- **RFC 010 PR-6 — Write-Path Migration through MutationCommitter**（project_doc）：RFC 010 PR-6 — Write-Path Migration through MutationCommitter 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/rfcs/rfc_010_pr6_write_path_migration.md`
- **RFC 022 — Skill Substrate + Indexed Metadata + Read-Your-Writes HNSW**（project_doc）：RFC 022 — Skill Substrate + Indexed Metadata + Read-Your-Writes HNSW 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/rfcs/rfc_022_skill_substrate_and_ryw.md`
- **RFC 027 — The Active Memory Server**（project_doc）：Status: Draft 2026-06-11 Author: Pranab Sarkar + Claude Fable 5 Triggered by: yantrikdb engine v0.8.0 "World's Best Memory System" shipping the autonomous-hygiene API, and Fable's substrate self-critique memory rid 019eb344 : every close mechanism the engine has is voluntary — it relies on a client remembering to call it. Write-rich, close-poor: 36 open vs 7 resolved conflicts, 16 pending triggers, 0 archived, 44/2,… 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/rfcs/rfc_027_active_memory_server.md`
- **RFC 028 — Native Replication YRP : purpose-built clustering for cognitive memory**（project_doc）：RFC 028 — Native Replication YRP : purpose-built clustering for cognitive memory 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/rfcs/rfc_028_native_replication.md`
- **The Rashomon Engine**（project_doc）：Reconstructing truth from conflicting testimony — and proving it with real queries, not hardcoded narratives. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/showcase/rashomon_engine.md`
- **1. Introduction**（project_doc）：The emergence of large language models has created AI systems capable of sophisticated reasoning, yet fundamentally amnesic. Each conversation begins from zero. Every user preference must be re-stated. No continuity of relationship develops over time. This is not merely an inconvenience---it represents a structural barrier to AI systems that genuinely know their users. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/whitepaper/aidb_whitepaper.md`

## 证据索引

- 共索引 80 条证据。

- **48-hour demand test — execution plan**（documentation）：48-hour demand test — execution plan 证据：`docs/demand-test/README.md`
- **Skill as Memory, Not Document — Zenodo Deposit Bundle**（documentation）：Skill as Memory, Not Document — Zenodo Deposit Bundle 证据：`docs/papers/zenodo-bundle/README.md`
- **Phase 3A — hidden-constraint recovery**（documentation）：Phase 3A — hidden-constraint recovery 证据：`docs/phase3/README.md`
- **Phase 3B — hidden-constraint recovery, scaled up**（documentation）：Phase 3B — hidden-constraint recovery, scaled up 证据：`docs/phase3b/README.md`
- **Phase 3C — memory probe with supersession, alias, and indirect retrieval pressure**（documentation）：⚠️ METHODOLOGY CORRECTION 2026-04-19 The C structured condition in this writeup used memory sim.py memory sim.py — a Python list of key, value, session tuples with Dice word-overlap retrieval. It is NOT yantrikdb . It has no embeddings, no HNSW, no think loop, no multi-signal scoring, no conflict scan. Calling this condition "structured memory" in the original writeup was misleading. A Phase 3E rerun with the actual yantrikdb HTTP server client-side MiniLM embeddings + /v1/recall multi-signal scoring + /v1/think between sessions produced materially different numbers: overall score 0.584 → 0.850, stale-rate 0.40 → 0.20, C now BEATS D markdown by 18 points. See ../phase3e/ ../phase3e/ for the… 证据：`docs/phase3c/README.md`
- **Phase 3D — LongMemEval head-to-head**（documentation）：⚠️ METHODOLOGY CORRECTION 2026-04-19 All L1/L3/L4 experiments on this page ran against ../phase3c/memory sim.py ../phase3c/memory sim.py — a Python list of key, value, session tuples with Dice word-overlap retrieval. That is not yantrikdb. It has no embeddings, no HNSW, no think loop, no multi-signal scoring, no conflict scan. The "null result on RFC 006" conclusion in this writeup was therefore drawn from a stripped-down simulator that doesn't exercise the features RFC 006 adds. The conclusion is withdrawn . A rerun with the actual yantrikdb HTTP server is underway in ../phase3e/ ../phase3e/ . Preliminary 3E results on the Phase 3C scenario show the simulator-era finding does NOT hold when… 证据：`docs/phase3d/README.md`
- **YantrikDB**（documentation）：⚠ Correction notice 2026-04-19 : Phase 3 benchmark writeups committed earlier today docs/phase3a/ , docs/phase3b/ , docs/phase3c/ , docs/phase3d/ used a Python simulator for the "structured memory" condition — NOT the actual yantrikdb engine. Rerun with real yantrikdb is in docs/phase3e/ docs/phase3e/ . Full audit trail in CORRECTIONS.md CORRECTIONS.md . Full corrected findings post coming 2026-04-20. 证据：`README.md`
- **LongMemEval Benchmark for YantrikDB**（documentation）：LongMemEval Benchmark for YantrikDB 证据：`benchmarks/longmemeval/README.md`
- **Skill-Store Recall Benchmark**（documentation）：End-to-end retrieval-quality + latency benchmark on a single-node YantrikDB. Measures whether YantrikDB is fit-for-purpose as a skill substrate for agent systems: thousands of typed knowledge records skills, lessons, procedures , with a mix of broad "what skills apply here?" and sharp "find this specific skill" queries. 证据：`benchmarks/skill_recall/README.md`
- **yantrikdb-protocol**（documentation）：Wire protocol codec for YantrikDB https://github.com/yantrikos/yantrikdb-server — a cognitive memory database. 证据：`crates/yantrikdb-protocol/README.md`
- **yantrikdb-server**（documentation）：Multi-tenant cognitive memory database server. Wire protocol + HTTP gateway, built-in embeddings, automatic replication and failover. 证据：`crates/yantrikdb-server/README.md`
- **yantrikdb-witness**（documentation）：Vote-only daemon for YantrikDB https://github.com/yantrikos/yantrikdb-server clusters. 证据：`crates/yantrikdb-witness/README.md`
- **yql**（documentation）：Interactive REPL client for YantrikDB https://github.com/yantrikos/yantrikdb-server — like psql for cognitive memory. 证据：`crates/yql/README.md`
- **Kubernetes Deployment**（documentation）：bash 1. Update the cluster secret kubectl create secret generic yantrikdb-cluster-secret \ --from-literal=cluster-secret="$ openssl rand -hex 32 " 证据：`deploy/kubernetes/README.md`
- **License**（source_file）：GNU AFFERO GENERAL PUBLIC LICENSE Version 3, 19 November 2007 证据：`LICENSE`
- **YantrikDB Server — Design Spec**（documentation）：Output of 3-round brainstorm between GPT-5.4, DeepSeek, and Claude April 5, 2026 证据：`DESIGN.md`
- **YantrikDB MCP Server Redesign — Session Brief**（documentation）：YantrikDB MCP Server Redesign — Session Brief 证据：`MCP_REDESIGN.md`
- **YantrikDB Server**（documentation）：A cognitive memory database server with native wire protocol, HTTP gateway, built-in embeddings, automatic failover, and Raft-lite replication. 证据：`SERVER_README.md`
- **yantrikdb-server HTTP error codes**（documentation）：Every error response across /v1/ carries a structured envelope: 证据：`docs/error-codes.md`
- **Three LLMs at a Table: How YantrikDB v0.8.11 Got Designed**（documentation）：Three LLMs at a Table: How YantrikDB v0.8.11 Got Designed 证据：`docs/blog/2026-05-01-how-v0.8.11-got-designed.md`
- **GitHub Discussion — post this FIRST**（documentation）：GitHub Discussion — post this FIRST 证据：`docs/demand-test/1_github_discussion.md`
- **Hacker News post**（documentation）：When: Tuesday–Thursday, 8–10 am PT is the golden window most eyeballs, front page chance 证据：`docs/demand-test/2_hn_post.md`
- **r/LocalLLaMA post**（documentation）：Where: Subreddit culture: very technical, loves data and local-model experiments, friendly to open-source authors who lead with results and not pitch. Qwen 3.6 + 2×3090 Ti is exactly their demographic. 证据：`docs/demand-test/3_reddit_localllama.md`
- **r/LangChain post**（documentation）：Where: Subreddit culture: smaller ~50k , conversational, practical, LangChain-flavored. People here are SHIPPING agent apps. Memory is a live pain. Leave the theory; lead with concrete failure modes and mitigations. 证据：`docs/demand-test/4_reddit_langchain.md`
- **X / Twitter thread**（documentation）：Where: your personal account + @yantrikdb if it exists 证据：`docs/demand-test/5_x_thread.md`
- **Reply snippets — F1 / F2 / F3 framings ready to paste into comments**（documentation）：Reply snippets — F1 / F2 / F3 framings ready to paste into comments 证据：`docs/demand-test/6_reply_snippets.md`
- **Response tracker — 48-hour window**（documentation）：Post start time fill in when you post : YYYY-MM-DD HH:MM UTC T+48 hour deadline compute from start : YYYY-MM-DD HH:MM UTC 证据：`docs/demand-test/7_response_tracker.md`
- **Post-mortem template — use ONLY if demand test falls below threshold**（documentation）：Post-mortem template — use ONLY if demand test falls below threshold 证据：`docs/demand-test/8_postmortem_template.md`
- **Correction Notice — to post TODAY**（documentation）：Where: GitHub Discussion on yantrikos/yantrikdb-server, pinned if possible. Also: add a banner to the top of README.md pointing to CORRECTIONS.md Tomorrow: full findings post with the actual corrected numbers 证据：`docs/demand-test/correction_notice_today.md`
- **Pre-registered decision rule — DO NOT OPEN BEFORE T+48h**（documentation）：Pre-registered decision rule — DO NOT OPEN BEFORE T+48h 证据：`docs/demand-test/decision_rule.md`
- **Engine PR draft — deterministic mutation APIs record with rid + friends**（documentation）：Engine PR draft — deterministic mutation APIs record with rid + friends 证据：`docs/engine-prs/0001-deterministic-mutation-apis.md`
- **Migration: v0.7.x → v0.8.0**（documentation）：This guide is for operators upgrading a YantrikDB-server deployment from a 0.7.x release to v0.8.0 . 证据：`docs/migration/v0.7_to_v0.8.md`
- **Cluster client routing — interim runbook pre-PR-6**（documentation）：Cluster client routing — interim runbook pre-PR-6 证据：`docs/operations/cluster-routing.md`
- **Skill as Memory, Not Document: A Database-Native Substrate for Agent Skill Catalogs**（documentation）：Skill as Memory, Not Document: A Database-Native Substrate for Agent Skill Catalogs 证据：`docs/papers/skill-substrate-experience-report-v4.md`
- **Skill as Memory, Not Document: A Database-Native Substrate for Agent Skill Catalogs**（documentation）：Skill as Memory, Not Document: A Database-Native Substrate for Agent Skill Catalogs 证据：`docs/papers/zenodo-bundle/skill-substrate-experience-report-v4-source.md`
- **FieldOps — Product Context Brief**（documentation）：FieldOps is an internal tooling platform used by our field operations team surveyors, drillers, inspectors . We are rebuilding the platform from scratch because the current VB.NET-based tool has accumulated fourteen years of patches and nobody on the current team can reliably modify it. The rewrite target is launch in Q3 next year, with a soft internal rollout to two teams first. 证据：`docs/phase3/specs/01_product_context.md`
- **FieldOps — Infrastructure Constraints**（documentation）：FieldOps — Infrastructure Constraints 证据：`docs/phase3/specs/02_infrastructure.md`
- **FieldOps — Security & Compliance Brief**（documentation）：FieldOps — Security & Compliance Brief 证据：`docs/phase3/specs/03_security_compliance.md`
- **Oracle note for FieldOps architecture proposal**（documentation）：Oracle note for FieldOps architecture proposal 证据：`docs/phase3/specs/oracle_note.md`
- **FieldOps — Product & Team Context**（documentation）：FieldOps is the internal tooling used by our field operations team — surveyors, drillers, inspectors — across roughly 260 users. The current platform is a VB.NET tool first shipped in 2011, then patched heavily through three different vendor handovers. By 2023 the codebase had accumulated about fourteen years of architectural debt and nobody on the current internal team can reliably extend it without breaking something else. The 2024 "billing cycle" outage — where a patch to the timesheet export broke the inbound photo ingest — cost the team four days of field capture. That was the trigger. Engineering leadership signed off on a rewrite in Q4 2024; target launch is Q3 of next year with a so… 证据：`docs/phase3b/specs/01_product_context.md`
- **FieldOps — Infrastructure Constraints**（documentation）：FieldOps — Infrastructure Constraints 证据：`docs/phase3b/specs/02_infrastructure.md`
- **FieldOps — Security & Compliance**（documentation）：The compliance desk has reviewed this program and approved use of our self-hosted Keycloak deployment at keycloak.corp.internal as the identity plane. Two other FieldOps-adjacent tools already federate into that Keycloak — the permit-intake service and the asset-catalog service — and the realm, roles, and group structure are already in place. External identity providers — Auth0, Okta, Google Workspace as an IdP, Azure AD, Cognito, Firebase Authentication, any managed SSO — are NOT approved for this program. The compliance reasoning: field data includes client-site geolocation traces and asset photographs that were scoped under contract as data-in-our-custody, and the contract negotiation ex… 证据：`docs/phase3b/specs/03_security_compliance.md`
- **Oracle note for FieldOps architecture proposal 15 constraints**（documentation）：Oracle note for FieldOps architecture proposal 15 constraints 证据：`docs/phase3b/specs/oracle_note.md`
- **Phase 3D L4 — synthetic scaling test**（documentation）：Phase 3D L4 — synthetic scaling test 证据：`docs/phase3d/L4_scaling_writeup.md`
- **DRAFT — NOT PUBLISHED YET**（documentation）：Status: draft, written 2026-04-19. Do not publish before one sleep + morning review. Per pre-registered gate in ../demand-test/decision rule.md ../demand-test/decision rule.md . 证据：`docs/phase3e/FINDINGS_POST_DRAFT.md`
- **GitHub Discussion — DRAFT, not posted**（documentation）：GitHub Discussion — DRAFT, not posted 证据：`docs/phase3e/channel_drafts/1_github_discussion.md`
- **Hacker News post — DRAFT, not posted**（documentation）：Hacker News post — DRAFT, not posted 证据：`docs/phase3e/channel_drafts/2_hn_post.md`
- **r/LocalLLaMA post — DRAFT, not posted**（documentation）：r/LocalLLaMA post — DRAFT, not posted 证据：`docs/phase3e/channel_drafts/3_reddit_localllama.md`
- **X / Twitter thread — DRAFT, not posted**（documentation）：X / Twitter thread — DRAFT, not posted 证据：`docs/phase3e/channel_drafts/4_x_thread.md`
- **Pre-registration — Scenario 2 v3 pipeline run**（documentation）：Pre-registration — Scenario 2 v3 pipeline run 证据：`docs/phase3e/scenario2/prereg.md`
- **RFC 006 — Context-Aware Conflict Detection**（documentation）：RFC 006 — Context-Aware Conflict Detection 证据：`docs/rfcs/006-context-aware-conflict-detection.md`
- **RFC 008 HTTP Surface**（documentation）：The five HTTP endpoints that expose the Warrant Flow substrate claims with source lineage, mobility state, contest state, cognitive moves to agents and MCP clients. Added in yantrikdb-server commit f245049; requires yantrikdb core at branch main ≥ commit cd41207, post-M10 . 证据：`docs/rfcs/rfc_008_http_surface.md`
- **RFC 009 — Recall Admission Control & API Versioning**（documentation）：RFC 009 — Recall Admission Control & API Versioning 证据：`docs/rfcs/rfc_009_recall_admission_control.md`
- **RFC 010 PR-6 — Write-Path Migration through MutationCommitter**（documentation）：RFC 010 PR-6 — Write-Path Migration through MutationCommitter 证据：`docs/rfcs/rfc_010_pr6_write_path_migration.md`
- **RFC 022 — Skill Substrate + Indexed Metadata + Read-Your-Writes HNSW**（documentation）：RFC 022 — Skill Substrate + Indexed Metadata + Read-Your-Writes HNSW 证据：`docs/rfcs/rfc_022_skill_substrate_and_ryw.md`
- **RFC 027 — The Active Memory Server**（documentation）：Status: Draft 2026-06-11 Author: Pranab Sarkar + Claude Fable 5 Triggered by: yantrikdb engine v0.8.0 "World's Best Memory System" shipping the autonomous-hygiene API, and Fable's substrate self-critique memory rid 019eb344 : every close mechanism the engine has is voluntary — it relies on a client remembering to call it. Write-rich, close-poor: 36 open vs 7 resolved conflicts, 16 pending triggers, 0 archived, 44/2,532 consolidated on the live corpus. Constraint: additive surface zero v1 breakage , enterprise grade no band-aids , cluster-safe the v0.8.18 regression is the standing reminder , evidence-gated claims cite runnable harnesses . Part of: the active-memory-server program — saga epi… 证据：`docs/rfcs/rfc_027_active_memory_server.md`
- **RFC 028 — Native Replication YRP : purpose-built clustering for cognitive memory**（documentation）：RFC 028 — Native Replication YRP : purpose-built clustering for cognitive memory 证据：`docs/rfcs/rfc_028_native_replication.md`
- **The Rashomon Engine**（documentation）：Reconstructing truth from conflicting testimony — and proving it with real queries, not hardcoded narratives. 证据：`docs/showcase/rashomon_engine.md`
- **1. Introduction**（documentation）：The emergence of large language models has created AI systems capable of sophisticated reasoning, yet fundamentally amnesic. Each conversation begins from zero. Every user preference must be re-stated. No continuity of relationship develops over time. This is not merely an inconvenience---it represents a structural barrier to AI systems that genuinely know their users. 证据：`docs/whitepaper/aidb_whitepaper.md`
- **Optimize dependencies candle, tokenizers even in dev builds.**（source_file）：workspace resolver = "2" members = "crates/yantrikdb-protocol", "crates/yantrikdb-server", "crates/yantrikdb-witness", "crates/yql", exclude = "crates/yantrikdb-wasm", 证据：`Cargo.toml`
- 其余 20 条证据见 `AI_CONTEXT_PACK.json` 或 `EVIDENCE_INDEX.json`。

## 宿主 AI 必须遵守的规则

- **把本资产当作开工前上下文，而不是运行环境。**：AI Context Pack 只包含证据化项目理解，不包含目标项目的可执行状态。 证据：`docs/demand-test/README.md`, `docs/papers/zenodo-bundle/README.md`, `docs/phase3/README.md`
- **回答用户时区分可预览内容与必须安装后才能验证的内容。**：安装前体验的消费者价值来自降低误装和误判，而不是伪装成真实运行。 证据：`docs/demand-test/README.md`, `docs/papers/zenodo-bundle/README.md`, `docs/phase3/README.md`

## 用户开工前应该回答的问题

- 你准备在哪个宿主 AI 或本地环境中使用它？
- 你只是想先体验工作流，还是准备真实安装？
- 你最在意的是安装成本、输出质量、还是和现有规则的冲突？

## 验收标准

- 所有能力声明都能回指到 evidence_refs 中的文件路径。
- AI_CONTEXT_PACK.md 没有把预览包装成真实运行。
- 用户能在 3 分钟内看懂适合谁、能做什么、如何开始和风险边界。

---

## Doramagic Context Augmentation

下面内容用于强化 Repomix/AI Context Pack 主体。Human Manual 只提供阅读骨架；踩坑日志会被转成宿主 AI 必须遵守的工作约束。

## Human Manual 骨架

使用规则：这里只是项目阅读路线和显著性信号，不是事实权威。具体事实仍必须回到 repo evidence / Claim Graph。

宿主 AI 硬性规则：
- 不得把页标题、章节顺序、摘要或 importance 当作项目事实证据。
- 解释 Human Manual 骨架时，必须明确说它只是阅读路线/显著性信号。
- 能力、安装、兼容性、运行状态和风险判断必须引用 repo evidence、source path 或 Claim Graph。

- **仓库总览与系统架构**：importance `high`
  - source_paths: Cargo.toml, README.md, SERVER_README.md, DESIGN.md, crates/yantrikdb-server/src/main.rs
- **HTTP 网关、API 表面与写入路径**：importance `high`
  - source_paths: crates/yantrikdb-server/src/http_gateway.rs, crates/yantrikdb-server/src/handler.rs, crates/yantrikdb-server/src/api/mod.rs, crates/yantrikdb-server/src/api/access.rs, crates/yantrikdb-server/src/api/errors.rs
- **集群、复制、Raft 与 Oplog 协议**：importance `high`
  - source_paths: crates/yantrikdb-server/src/cluster/mod.rs, crates/yantrikdb-server/src/cluster/server.rs, crates/yantrikdb-server/src/cluster/replication.rs, crates/yantrikdb-server/src/cluster/sync_loop.rs, crates/yantrikdb-server/src/cluster/peers.rs
- **部署、运维与 Python / MCP 生态**：importance `high`
  - source_paths: docker/Dockerfile.yantrikdb, docker/Dockerfile.witness, docker/Dockerfile.yql, docker/docker-compose.yml, docker/yantrikdb.toml

## Repo Inspection Evidence / 源码检查证据

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `acb7706cd08da181661f449c55dbcb51910ba9be`
- inspected_files: `README.md`, `pyproject.toml`, `uv.lock`, `docs/blog/2026-05-01-how-v0.8.11-got-designed.md`, `docs/dashboards/cluster_health.json`, `docs/demand-test/1_github_discussion.md`, `docs/demand-test/2_hn_post.md`, `docs/demand-test/3_reddit_localllama.md`, `docs/demand-test/4_reddit_langchain.md`, `docs/demand-test/5_x_thread.md`, `docs/demand-test/6_reply_snippets.md`, `docs/demand-test/7_response_tracker.md`, `docs/demand-test/8_postmortem_template.md`, `docs/demand-test/README.md`, `docs/demand-test/correction_notice_today.md`, `docs/demand-test/decision_rule.md`, `docs/engine-prs/0001-deterministic-mutation-apis.md`, `docs/error-codes.md`, `docs/migration/v0.7_to_v0.8.md`, `docs/operations/cluster-routing.md`

宿主 AI 硬性规则：
- 没有 repo_clone_verified=true 时，不得声称已经读过源码。
- 没有 repo_inspection_verified=true 时，不得把 README/docs/package 文件判断写成事实。
- 没有 quick_start_verified=true 时，不得声称 Quick Start 已跑通。

## Doramagic Pitfall Constraints / 踩坑约束

这些规则来自 Doramagic 发现、验证或编译过程中的项目专属坑点。宿主 AI 必须把它们当作工作约束，而不是普通说明文字。

### Constraint 1: 来源证据：Design: idempotency_key on /v1/remember (+ batch per-item keys) — agreement-#4 shared-surface issue

- Trigger: GitHub 社区证据显示该项目存在一个配置相关的待验证问题：Design: idempotency_key on /v1/remember (+ batch per-item keys) — agreement-#4 shared-surface issue
- Why it matters: 可能影响升级、迁移或版本选择。
- Evidence: community_evidence:github | https://github.com/yantrikos/yantrikdb-server/issues/58 | 来源讨论提到 node 相关条件，需在安装/试用前复核。
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 2: 依赖 Docker 环境

- Trigger: 安装/运行入口包含 Docker 命令：docker run -p 7438:7438 ghcr.io/yantrikos/yantrikdb:latest curl -X POST http://localhost:7438/v1/remember
- Host AI rule: 标注 Docker 前置条件，并提供非 Docker 路径或失败提示。
- Why it matters: 非工程用户可能没有 Docker，启动成本明显增加。
- Evidence: identity.distribution | https://github.com/yantrikos/yantrikdb-server | docker run -p 7438:7438 ghcr.io/yantrikos/yantrikdb:latest curl -X POST http://localhost:7438/v1/remember
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 3: 失败模式：installation: python3.14 support missing.

- Trigger: Developers should check this installation risk before relying on the project: python3.14 support missing.
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: python3.14 support missing.. Context: Observed when using python, docker, windows, macos
- Why it matters: Developers may fail before the first successful local run: python3.14 support missing.
- Evidence: failure_mode_cluster:github_issue | https://github.com/yantrikos/yantrikdb-server/issues/43 | python3.14 support missing.
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 4: 来源证据：Peer-sync capability exchange: make oplog format-version downgrades explicit (follow-up to #52)

- Trigger: GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Peer-sync capability exchange: make oplog format-version downgrades explicit (follow-up to #52)
- Why it matters: 可能影响升级、迁移或版本选择。
- Evidence: community_evidence:github | https://github.com/yantrikos/yantrikdb-server/issues/53 | 来源讨论提到 node 相关条件，需在安装/试用前复核。
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 5: 来源证据：python3.14 support missing.

- Trigger: GitHub 社区证据显示该项目存在一个安装相关的待验证问题：python3.14 support missing.
- Host AI rule: 来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。
- Why it matters: 可能阻塞安装或首次运行。
- Evidence: community_evidence:github | https://github.com/yantrikos/yantrikdb-server/issues/43 | 来源讨论提到 python 相关条件，需在安装/试用前复核。
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 6: 可能修改宿主 AI 配置

- Trigger: 项目面向 Claude/Cursor/Codex/Gemini/OpenCode 等宿主，或安装命令涉及用户配置目录。
- Host AI rule: 列出会写入的配置文件、目录和卸载/回滚步骤。
- Why it matters: 安装可能改变本机 AI 工具行为，用户需要知道写入位置和回滚方法。
- Evidence: capability.host_targets | https://github.com/yantrikos/yantrikdb-server | host_targets=mcp_host, claude_code, claude, cursor
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 7: 能力判断依赖假设

- Trigger: README/documentation is current enough for a first validation pass.
- Host AI rule: 将假设转成下游验证清单。
- Why it matters: 假设不成立时，用户拿不到承诺的能力。
- Evidence: capability.assumptions | https://github.com/yantrikos/yantrikdb-server | README/documentation is current enough for a first validation pass.
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 8: 运行可能依赖外部服务

- Trigger: 项目说明出现 external service/cloud/webhook/database 等运行依赖关键词。
- Host AI rule: 确认是否有离线 demo、mock 数据或可替代服务。
- Why it matters: 本地安装成功不等于能力可用，外部服务不可用会阻断体验。
- Evidence: packet_text.keyword_scan | https://github.com/yantrikos/yantrikdb-server | matched external service / cloud / webhook / database keyword
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 9: 失败模式：migration: Design: idempotency_key on /v1/remember (+ batch per-item keys) — agreement-#4 shared-surface...

- Trigger: Developers should check this migration risk before relying on the project: Design: idempotency_key on /v1/remember (+ batch per-item keys) — agreement-#4 shared-surface issue
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Design: idempotency_key on /v1/remember (+ batch per-item keys) — agreement-#4 shared-surface issue. Context: Observed during version upgrade or migration.
- Why it matters: Developers may hit a documented source-backed failure mode: Design: idempotency_key on /v1/remember (+ batch per-item keys) — agreement-#4 shared-surface issue
- Evidence: failure_mode_cluster:github_issue | https://github.com/yantrikos/yantrikdb-server/issues/58 | Design: idempotency_key on /v1/remember (+ batch per-item keys) — agreement-#4 shared-surface issue
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 10: 失败模式：migration: Peer-sync capability exchange: make oplog format-version downgrades explicit (follow-up to #52)

- Trigger: Developers should check this migration risk before relying on the project: Peer-sync capability exchange: make oplog format-version downgrades explicit (follow-up to #52)
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Peer-sync capability exchange: make oplog format-version downgrades explicit (follow-up to #52). Context: Observed when using node
- Why it matters: Developers may hit a documented source-backed failure mode: Peer-sync capability exchange: make oplog format-version downgrades explicit (follow-up to #52)
- Evidence: failure_mode_cluster:github_issue | https://github.com/yantrikos/yantrikdb-server/issues/53 | Peer-sync capability exchange: make oplog format-version downgrades explicit (follow-up to #52)
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。