# yantrikdb-server - 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 yantrikdb-server. 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 - **AI researchers or builders of research-oriented Agents**: The README clearly centers on research, experiment, or paper workflows. Evidence: `README.md` Claim: `clm_0002` supported 0.86 - **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 ## What It Can Do - **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` Claim: `clm_0001` supported 0.86 ## How to Start - `pip install yantrikdb-mcp` Evidence: `README.md` Claim: `clm_0004` supported 0.86 - `curl -X POST http://localhost:7438/v1/remember -d '{"text":"hello"}'` Evidence: `README.md` Claim: `clm_0005` supported 0.86 - `pip install yantrikdb` Evidence: `README.md` Claim: `clm_0004` supported 0.86, `clm_0006` 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**: Role quality and task fit cannot be trusted directly. - **Continuing will touch**: Role selection bias, Command execution, Local environment or project files ### What You Can Trust Now - **Target-audience signal: AI researchers or builders of research-oriented Agents** (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_0002` supported 0.86 - **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 - **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` Claim: `clm_0001` 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_0004` supported 0.86 ### What You Cannot Trust Yet - **Role quality and task fit cannot be trusted directly.** (unverified): A role library proves there are many roles; it does not prove each one fits your specific task or that a role produces high-quality results. - **Do not treat role copy as real execution capability.** (unverified): Before install you can only judge whether the role description and task profile match; you cannot prove it can complete the task inside the host AI. - **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. - **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. ### What Continuing Will Touch - **Role selection bias**: The user's judgment about which expert role should handle the task. Why: Picking the wrong role makes the AI answer from the wrong expert perspective, wasting time or misleading decisions. - **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` - **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: `README.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: `README.md` - **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 an interactive trial to verify the task profile and role match first; do not import the whole role library up front. (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.) - **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. - **Keep a record of the original role selection**: If output goes off-topic, you can return to the task-profiling stage and reselect a role instead of pushing on with the wrong one. - **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_0007` 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: `README.md` Claim: `clm_0008` 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 - **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` Claim: `clm_0001` supported 0.86 ### Context Scale - Total files: 413 - Important-file coverage: 40/413 - Evidence index entries: 80 - Role / Skill entries: 60 ### 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 yantrikdb-server, 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 yantrikdb-server 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 yantrikdb-server, 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 60 role / Skill / project-doc entries. - **48-hour demand test — execution plan** (project_doc): 48-hour demand test — execution plan Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/demand-test/README.md` - **Skill as Memory, Not Document — Zenodo Deposit Bundle** (project_doc): Skill as Memory, Not Document — Zenodo Deposit Bundle Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/papers/zenodo-bundle/README.md` - **Phase 3A — hidden-constraint recovery** (project_doc): Phase 3A — hidden-constraint recovery Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/phase3/README.md` - **Phase 3B — hidden-constraint recovery, scaled up** (project_doc): Phase 3B — hidden-constraint recovery, scaled up Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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… Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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… Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `README.md` - **LongMemEval Benchmark for YantrikDB** (project_doc): LongMemEval Benchmark for YantrikDB Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `benchmarks/skill_recall/README.md` - **yantrikdb-protocol** (project_doc): Wire protocol codec for YantrikDB https://github.com/yantrikos/yantrikdb-server — a cognitive memory database. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `crates/yantrikdb-server/README.md` - **yantrikdb-witness** (project_doc): Vote-only daemon for YantrikDB https://github.com/yantrikos/yantrikdb-server clusters. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `crates/yantrikdb-witness/README.md` - **yql** (project_doc): Interactive REPL client for YantrikDB https://github.com/yantrikos/yantrikdb-server — like psql for cognitive memory. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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 " Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `deploy/kubernetes/README.md` - **Changelog** (project_doc): All notable changes to yantrikdb-server are recorded here. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `CHANGELOG.md` - **YantrikDB Server — Design Spec** (project_doc): Output of 3-round brainstorm between GPT-5.4, DeepSeek, and Claude April 5, 2026 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `DESIGN.md` - **YantrikDB MCP Server Redesign — Session Brief** (project_doc): YantrikDB MCP Server Redesign — Session Brief Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `MCP_REDESIGN.md` - **Roadmap** (project_doc): This document captures the public roadmap for yantrikdb-server — what shipped, what's coming, and what we're explicitly not building. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `ROADMAP.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. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `SERVER_README.md` - **yantrikdb-server HTTP error codes** (project_doc): Every error response across /v1/ carries a structured envelope: Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/blog/2026-05-01-how-v0.8.11-got-designed.md` - **GitHub Discussion — post this FIRST** (project_doc): GitHub Discussion — post this FIRST Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/demand-test/4_reddit_langchain.md` - **X / Twitter thread** (project_doc): Where: your personal account + @yantrikdb if it exists Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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 . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/phase3/specs/01_product_context.md` - **FieldOps — Infrastructure Constraints** (project_doc): FieldOps — Infrastructure Constraints Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/phase3/specs/02_infrastructure.md` - **FieldOps — Security & Compliance Brief** (project_doc): FieldOps — Security & Compliance Brief Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/phase3/specs/03_security_compliance.md` - **Oracle note for FieldOps architecture proposal** (project_doc): Oracle note for FieldOps architecture proposal Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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… Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/phase3b/specs/01_product_context.md` - **FieldOps — Infrastructure Constraints** (project_doc): FieldOps — Infrastructure Constraints Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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… Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/phase3b/specs/oracle_note.md` - **Phase 3D L4 — synthetic scaling test** (project_doc): Phase 3D L4 — synthetic scaling test Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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 . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/phase3e/FINDINGS_POST_DRAFT.md` - **GitHub Discussion — DRAFT, not posted** (project_doc): GitHub Discussion — DRAFT, not posted Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/phase3e/channel_drafts/1_github_discussion.md` - **Hacker News post — DRAFT, not posted** (project_doc): Hacker News post — DRAFT, not posted Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/phase3e/channel_drafts/2_hn_post.md` - **r/LocalLLaMA post — DRAFT, not posted** (project_doc): r/LocalLLaMA post — DRAFT, not posted Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/phase3e/channel_drafts/3_reddit_localllama.md` - **X / Twitter thread — DRAFT, not posted** (project_doc): X / Twitter thread — DRAFT, not posted Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/phase3e/channel_drafts/4_x_thread.md` - **Pre-registration — Scenario 2 v3 pipeline run** (project_doc): Pre-registration — Scenario 2 v3 pipeline run Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/phase3e/scenario2/prereg.md` - **RFC 006 — Context-Aware Conflict Detection** (project_doc): RFC 006 — Context-Aware Conflict Detection Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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 . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/rfcs/rfc_008_http_surface.md` - **RFC 009 — Recall Admission Control & API Versioning** (project_doc): RFC 009 — Recall Admission Control & API Versioning Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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,… Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `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. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/whitepaper/aidb_whitepaper.md` ## Evidence Index - Indexed 80 evidence entries. - **48-hour demand test — execution plan** (documentation): 48-hour demand test — execution plan Evidence: `docs/demand-test/README.md` - **Skill as Memory, Not Document — Zenodo Deposit Bundle** (documentation): Skill as Memory, Not Document — Zenodo Deposit Bundle Evidence: `docs/papers/zenodo-bundle/README.md` - **Phase 3A — hidden-constraint recovery** (documentation): Phase 3A — hidden-constraint recovery Evidence: `docs/phase3/README.md` - **Phase 3B — hidden-constraint recovery, scaled up** (documentation): Phase 3B — hidden-constraint recovery, scaled up Evidence: `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… Evidence: `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… Evidence: `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. Evidence: `README.md` - **LongMemEval Benchmark for YantrikDB** (documentation): LongMemEval Benchmark for YantrikDB Evidence: `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. Evidence: `benchmarks/skill_recall/README.md` - **yantrikdb-protocol** (documentation): Wire protocol codec for YantrikDB https://github.com/yantrikos/yantrikdb-server — a cognitive memory database. Evidence: `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. Evidence: `crates/yantrikdb-server/README.md` - **yantrikdb-witness** (documentation): Vote-only daemon for YantrikDB https://github.com/yantrikos/yantrikdb-server clusters. Evidence: `crates/yantrikdb-witness/README.md` - **yql** (documentation): Interactive REPL client for YantrikDB https://github.com/yantrikos/yantrikdb-server — like psql for cognitive memory. Evidence: `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 " Evidence: `deploy/kubernetes/README.md` - **License** (source_file): GNU AFFERO GENERAL PUBLIC LICENSE Version 3, 19 November 2007 Evidence: `LICENSE` - **Changelog** (documentation): All notable changes to yantrikdb-server are recorded here. Evidence: `CHANGELOG.md` - **YantrikDB Server — Design Spec** (documentation): Output of 3-round brainstorm between GPT-5.4, DeepSeek, and Claude April 5, 2026 Evidence: `DESIGN.md` - **YantrikDB MCP Server Redesign — Session Brief** (documentation): YantrikDB MCP Server Redesign — Session Brief Evidence: `MCP_REDESIGN.md` - **Roadmap** (documentation): This document captures the public roadmap for yantrikdb-server — what shipped, what's coming, and what we're explicitly not building. Evidence: `ROADMAP.md` - **YantrikDB Server** (documentation): A cognitive memory database server with native wire protocol, HTTP gateway, built-in embeddings, automatic failover, and Raft-lite replication. Evidence: `SERVER_README.md` - **yantrikdb-server HTTP error codes** (documentation): Every error response across /v1/ carries a structured envelope: Evidence: `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 Evidence: `docs/blog/2026-05-01-how-v0.8.11-got-designed.md` - **GitHub Discussion — post this FIRST** (documentation): GitHub Discussion — post this FIRST Evidence: `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 Evidence: `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. Evidence: `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. Evidence: `docs/demand-test/4_reddit_langchain.md` - **X / Twitter thread** (documentation): Where: your personal account + @yantrikdb if it exists Evidence: `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 Evidence: `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 Evidence: `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 Evidence: `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 Evidence: `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 Evidence: `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 Evidence: `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 . Evidence: `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 Evidence: `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 Evidence: `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 Evidence: `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. Evidence: `docs/phase3/specs/01_product_context.md` - **FieldOps — Infrastructure Constraints** (documentation): FieldOps — Infrastructure Constraints Evidence: `docs/phase3/specs/02_infrastructure.md` - **FieldOps — Security & Compliance Brief** (documentation): FieldOps — Security & Compliance Brief Evidence: `docs/phase3/specs/03_security_compliance.md` - **Oracle note for FieldOps architecture proposal** (documentation): Oracle note for FieldOps architecture proposal Evidence: `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… Evidence: `docs/phase3b/specs/01_product_context.md` - **FieldOps — Infrastructure Constraints** (documentation): FieldOps — Infrastructure Constraints Evidence: `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… Evidence: `docs/phase3b/specs/03_security_compliance.md` - **Oracle note for FieldOps architecture proposal 15 constraints** (documentation): Oracle note for FieldOps architecture proposal 15 constraints Evidence: `docs/phase3b/specs/oracle_note.md` - **Phase 3D L4 — synthetic scaling test** (documentation): Phase 3D L4 — synthetic scaling test Evidence: `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 . Evidence: `docs/phase3e/FINDINGS_POST_DRAFT.md` - **GitHub Discussion — DRAFT, not posted** (documentation): GitHub Discussion — DRAFT, not posted Evidence: `docs/phase3e/channel_drafts/1_github_discussion.md` - **Hacker News post — DRAFT, not posted** (documentation): Hacker News post — DRAFT, not posted Evidence: `docs/phase3e/channel_drafts/2_hn_post.md` - **r/LocalLLaMA post — DRAFT, not posted** (documentation): r/LocalLLaMA post — DRAFT, not posted Evidence: `docs/phase3e/channel_drafts/3_reddit_localllama.md` - **X / Twitter thread — DRAFT, not posted** (documentation): X / Twitter thread — DRAFT, not posted Evidence: `docs/phase3e/channel_drafts/4_x_thread.md` - **Pre-registration — Scenario 2 v3 pipeline run** (documentation): Pre-registration — Scenario 2 v3 pipeline run Evidence: `docs/phase3e/scenario2/prereg.md` - **RFC 006 — Context-Aware Conflict Detection** (documentation): RFC 006 — Context-Aware Conflict Detection Evidence: `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 . Evidence: `docs/rfcs/rfc_008_http_surface.md` - **RFC 009 — Recall Admission Control & API Versioning** (documentation): RFC 009 — Recall Admission Control & API Versioning Evidence: `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 Evidence: `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 Evidence: `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… Evidence: `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 Evidence: `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. Evidence: `docs/showcase/rashomon_engine.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/demand-test/README.md`, `docs/papers/zenodo-bundle/README.md`, `docs/phase3/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/demand-test/README.md`, `docs/papers/zenodo-bundle/README.md`, `docs/phase3/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. - **Overview & Quick Start**: importance `high` - source_paths: README.md, SERVER_README.md, CHANGELOG.md, ROADMAP.md, DESIGN.md - **Workspace, Crates & Process Internals**: importance `high` - source_paths: Cargo.toml, crates/yantrikdb-protocol/Cargo.toml, crates/yantrikdb-server/Cargo.toml, crates/yantrikdb-server/src/main.rs, crates/yantrikdb-server/src/runtime.rs - **HTTP Gateway, Wire Protocol & Memory API**: importance `high` - source_paths: crates/yantrikdb-server/src/http_gateway.rs, crates/yantrikdb-server/src/api/mod.rs, crates/yantrikdb-server/src/api/access.rs, crates/yantrikdb-server/src/api/errors.rs, crates/yantrikdb-server/src/version/mod.rs - **Cluster, HA, Replication & Operations**: importance `high` - source_paths: crates/yantrikdb-server/src/raft/mod.rs, crates/yantrikdb-server/src/raft/assembly.rs, crates/yantrikdb-server/src/raft/committer.rs, crates/yantrikdb-server/src/raft/log_storage.rs, crates/yantrikdb-server/src/raft/state_machine.rs ## 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` 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: 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 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: 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/yantrikos/yantrikdb-server - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: Maintenance risk requires verification - 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 - 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: 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 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.