# verifiable-memory-mcp - 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 verifiable-memory-mcp. 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

- **Users who want to understand an open-source project's value and boundaries before installing**: Current evidence comes mainly from project documentation. Evidence: `README.md` Claim: `clm_0002` 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

- `npm install -g verifiable-memory-mcp` Evidence: `README.md` Claim: `clm_0003` supported 0.86
- `npx verifiable-memory-mcp` Evidence: `README.md` Claim: `clm_0004` supported 0.86
- `npx -y @modelcontextprotocol/inspector npx -y verifiable-memory-mcp` Evidence: `README.md` Claim: `clm_0005` 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**: Whether this workflow fits your way of working cannot be trusted directly.
- **Continuing will touch**: Host behavior change, Command execution, Local environment or project files

### What You Can Trust Now

- **Target-audience signal: Users who want to understand an open-source project's value and boundaries before installing** (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
- **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_0003` supported 0.86

### What You Cannot Trust Yet

- **Whether this workflow fits your way of working cannot be trusted directly.** (unverified): Workflow-style Skills can strongly constrain AI behavior; they can improve discipline but may also slow your current task pace.
- **That it will not conflict with your existing Claude/Cursor/Codex rules cannot be trusted directly.** (inferred): A dev-workflow Skill changes default behaviors like clarifying, planning, testing, and verifying, so it must be tried in a temporary host.
- **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

- **Host behavior change**: The default development rhythm of clarifying, planning, TDD, verifying, and wrapping up. Why: This kind of Skill draws both its value and its risk from strongly constraining the workflow; confirm first that you are willing to have it change how you work.
- **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**: Feel how it changes the AI's development rhythm first, then decide whether to let it into a real host. (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.
- **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_0006` 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_0007` 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: 58
- Important-file coverage: 40/58
- Evidence index entries: 41
- Role / Skill entries: 8

### 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 verifiable-memory-mcp, 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 verifiable-memory-mcp 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 verifiable-memory-mcp, 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 8 role / Skill / project-doc entries.

- **verifiable-memory-mcp** (project_doc): Local-first, append-only, tamper-evident memory for AI agents. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `README.md`
- **Bundle Verifier static, client-side** (project_doc): Bundle Verifier static, client-side Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `verifier/README.md`
- **ECO and ECOX Model** (project_doc): ECO is the portable evidence artifact. It is the forensic receipt. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/strategy/eco-and-ecox-model.md`
- **ECO Verifier Universal Model** (project_doc): The ECO Verifier is a standalone browser verifier for ECO artifacts. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/strategy/eco-verifier-universal.md`
- **Transparent Agent Evidence** (project_doc): Transparent Agent Evidence is a demo flow for agents that operate under verifiable memory. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/strategy/transparent-agent-evidence.md`
- **VMCP Demo E2E Implementation Plan** (project_doc): For agentic workers: REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development recommended or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox - syntax for tracking. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/superpowers/plans/2026-06-14-vmcp-demo-e2e.md`
- **Interactive Sandbox Implementation Plan** (project_doc): Interactive Sandbox Implementation Plan Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/superpowers/plans/2026-06-24-interactive-sandbox.md`
- **Interactive Sandbox Design** (project_doc): Date: 2026-06-24 Repo: verifiable-memory-mcp Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/superpowers/specs/2026-06-24-interactive-sandbox-design.md`

## Evidence Index

- Indexed 41 evidence entries.

- **verifiable-memory-mcp** (documentation): Local-first, append-only, tamper-evident memory for AI agents. Evidence: `README.md`
- **Bundle Verifier static, client-side** (documentation): Bundle Verifier static, client-side Evidence: `verifier/README.md`
- **Package** (package_manifest): { "name": "verifiable-memory-mcp", "version": "0.2.1", "description": "Local-first, append-only, tamper-evident memory for AI agents via MCP", "type": "module", "main": "dist/index.js", "bin": { "verifiable-memory-mcp": "dist/index.js" }, "scripts": { "build": "tsc", "start": "node dist/index.js", "dev": "tsx src/index.ts", "test": "vitest run", "demo:reset": "bash demo/reset.sh", "demo:scenario:reset": "bash demo/reset.sh && node demo/setup.mjs", "demo:setup": "node demo/setup.mjs", "demo:cycle": "node demo/agent-loop.mjs --once", "demo:agent-loop": "node demo/agent-loop.mjs", "demo:owner-update": "node demo/authorized-source-update.mjs", "demo:authorized-source-update": "node demo/authori… Evidence: `package.json`
- **License** (source_file): Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files the "Software" , to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: Evidence: `LICENSE`
- **ECO and ECOX Model** (documentation): ECO is the portable evidence artifact. It is the forensic receipt. Evidence: `docs/strategy/eco-and-ecox-model.md`
- **ECO Verifier Universal Model** (documentation): The ECO Verifier is a standalone browser verifier for ECO artifacts. Evidence: `docs/strategy/eco-verifier-universal.md`
- **Transparent Agent Evidence** (documentation): Transparent Agent Evidence is a demo flow for agents that operate under verifiable memory. Evidence: `docs/strategy/transparent-agent-evidence.md`
- **VMCP Demo E2E Implementation Plan** (documentation): For agentic workers: REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development recommended or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox - syntax for tracking. Evidence: `docs/superpowers/plans/2026-06-14-vmcp-demo-e2e.md`
- **Interactive Sandbox Implementation Plan** (documentation): Interactive Sandbox Implementation Plan Evidence: `docs/superpowers/plans/2026-06-24-interactive-sandbox.md`
- **Interactive Sandbox Design** (documentation): Date: 2026-06-24 Repo: verifiable-memory-mcp Evidence: `docs/superpowers/specs/2026-06-24-interactive-sandbox-design.md`
- **Sample Bundle** (structured_config): { "format": "verifiable-memory-bundle", "version": "0.1", "exportedAt": "2026-06-12T07:04:33.369Z", "entries": { "id": "mem 15d167fd", "createdAt": "2026-06-12T07:04:33.358Z", "content": "Decisión simulada del agente: preparar instrucción de pago de $10.000 — pendiente de aprobación humana.", "tags": "demo", "simulación" , "contentHash": "2385d94f8902329837b64fcffe17549c3eb05b5d3c1f5e594c43959b898ed831", "prevHash": null, "entryHash": "be3f8edb664063064ab01c0e4b1ca0276f78e59957d7e8002965ef244720767a" }, { "id": "mem 29a800d8", "createdAt": "2026-06-12T07:04:33.366Z", "content": "Contexto usado: límite operativo \"tier-2\", contraparte ACME S.A. ñ, é, 中文, emoji ✓ .", "tags": "demo", "context… Evidence: `verifier/sample-bundle.json`
- **Agent Loop** (source_file): function loadState ⋮---- function dash text ⋮---- function printCycle cycleNumber, result ⋮---- async function runResearch cycleNumber, result ⋮---- async function recordWaitEvidence result ⋮---- function pushEvent events, cycleNumber, now, type, label ⋮---- async function runCycle cycleNumber Evidence: `demo/agent-loop.mjs`
- **Common** (source_file): export function parseBundle text ⋮---- export function parseChain text ⋮---- export function parseEvent entry ⋮---- export function sortByCreatedAt entries ⋮---- export async function readMemoryState dataDir, clientName ⋮---- export function latestPolicy events ⋮---- export function pendingOwnerRequest events ⋮---- export function evaluateCycle Evidence: `demo/common.mjs`
- **Mcp Client** (source_file): function findServer ⋮---- export function resolveDemoDataDir options = ⋮---- function createEnvelope toolCalls, clientName ⋮---- function shellEscape value ⋮---- async function callLocalTool name, args = ⋮---- export async function runToolBatch toolCalls, options = ⋮---- export async function callTools toolCalls, options = ⋮---- export function textContent result Evidence: `demo/mcp-client.mjs`
- **Index** (source_file): verifiable-memory-mcp — memory your AI agents can verify :root { --bg: f5f4ec; --card: ffffff; --ink: 1d1d1b; --muted: 6b6b66; --line: e2e0d5; --green: 136f63; --green-soft: e3f0ee; --red: b3261e; --red-soft: f9e7e6; --idle: 9a988e; --focus: 136f63; --accent: 136f63; } @media prefers-color-scheme: dark { :root { --bg: 14140f; --card: 1e1e18; --ink: f0efe6; --muted: a3a299; --line: 33332a; --green: 4cc2a9; --green-soft: 11332e; --red: ff7a70; --red-soft: 3a1715; --idle: 6e6d64; --focus: 4cc2a9; --accent: 4cc2a9; } } { box-sizing: border-box; } html, body { margin: 0; padding: 0; } body { background: var --bg ; color: var --ink ; font: 16px/1.6 system-ui, -apple-system, "Segoe UI", Roboto, sa… Evidence: `index.html`
- **Index** (source_file): Verifiable Memory MCP — Sandbox :root { --bg: f4f1e8; --panel: ffffff; --ink: 1c1a18; --muted: 68635d; --line: ddd6c8; --accent: 165f56; --accent-soft: e2f0ed; --warn: 8b5e00; --warn-soft: f8edd1; --bad: a02a21; --bad-soft: f8e4e1; --good: 135f3f; --good-soft: e0efe7; } @media prefers-color-scheme: dark { :root { --bg: 12110d; --panel: 1b1814; --ink: f0ece3; --muted: aba399; --line: 363127; --accent: 53c4b1; --accent-soft: 102e2a; --warn: f2c35c; --warn-soft: 3a2d10; --bad: ff8e84; --bad-soft: 3d1714; --good: 65d49b; --good-soft: 10271a; } } { box-sizing: border-box; } body { margin: 0; background: var --bg ; color: var --ink ; font: 16px/1.6 system-ui, -apple-system, "Segoe UI", sans-serif… Evidence: `sandbox/index.html`
- **Db** (source_file): import Database from "better-sqlite3"; import { Entry } from "@napi-rs/keyring"; import path from "node:path"; import os from "node:os"; import { mkdirSync } from "node:fs"; import { MemoryEntry } from "./types.js"; import { sha256 } from "./hashing.js"; ⋮---- export interface StateRootCheck { stateRootVerified: boolean; status: "verified" "missing" "mismatch" "skipped" "unavailable" "empty"; dbRoot: string null; keychainRoot: string null; accountName: string; message?: string; } ⋮---- export function getDb : Database.Database ⋮---- function migrate database: Database.Database : void ⋮---- export function insertEntryAtomic buildEntry: prevHash: string null = MemoryEntry : MemoryEntry ⋮----… Evidence: `src/db.ts`
- **Hashing** (source_file): import { createHash } from "node:crypto"; ⋮---- export function sha256 data: string : string ⋮---- export function hashContent content: string : string ⋮---- export function hashEntry canonical: string : string ⋮---- export function buildEntryCanonical contentHash: string, prevHash: string null, createdAt: string : string Evidence: `src/hashing.ts`
- **Index** (source_file): import { Server } from "@modelcontextprotocol/sdk/server/index.js"; import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js"; import { CallToolRequestSchema, ListToolsRequestSchema, } from "@modelcontextprotocol/sdk/types.js"; import { remember } from "./tools/remember.js"; import { recall } from "./tools/recall.js"; import { verify } from "./tools/verify.js"; import { chainData } from "./tools/chain.js"; import { timeline } from "./tools/timeline.js"; import { exportEntries } from "./tools/export.js"; ⋮---- async function main Evidence: `src/index.ts`
- **Types** (source_file): export interface MemoryEntry { id: string; createdAt: string; content: string; tags: string ; contentHash: string; prevHash: string null; entryHash: string; } ⋮---- export interface VerifyResult { id: string; valid: boolean; storedHash: string; computedHash: string; reason: string; } ⋮---- export interface ExportBundle { format: "verifiable-memory-bundle"; version: "0.1"; exportedAt: string; entries: MemoryEntry ; } ⋮---- export type ToolName = "remember" "recall" "verify" "chain" "timeline" "export"; ⋮---- import type { CallToolResult } from "@modelcontextprotocol/sdk/types.js"; export type ToolResponse = CallToolResult; Evidence: `src/types.ts`
- **Acceptance** (source_file): async function sha256Hex bytes ⋮---- function check label, cond, detail ⋮---- // ---------- main ---------- Evidence: `verifier/acceptance.mjs`
- **--- 3. Optional: OpenTimestamps receipt Bitcoin-attested, third-party time ---** (source_file): set -euo pipefail for dep in node jq; do command -v "$dep" /dev/null 2 &1 { echo "ERROR: falta '$dep' en PATH." &2; exit 1; } done if command -v sha256sum /dev/null 2 &1; then sha256 file { sha256sum "$1"; } elif command -v shasum /dev/null 2 &1; then sha256 file { shasum -a 256 "$1"; } else echo "ERROR: falta 'sha256sum' Linux o 'shasum' macOS en PATH." &2 exit 1 fi HERE="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " ROOT="$ dirname "$HERE" " SERVER="$ROOT/dist/index.js" STAMP="$ date -u +%Y%m%dT%H%M%SZ " OUTDIR="${1:-$ROOT/anchor-out/$STAMP}" REAL DIR="${HOME}/.verifiable-memory-mcp" -n "${VMCP DATA DIR:-}" { echo "ERROR: VMCP DATA DIR is required. Refusing to export unspecified memory."… Evidence: `verifier/anchor.sh`
- **langToggle {** (source_file): Verificador — Evidence Record :root { --bg: f5f4ec; --card: ffffff; --ink: 1d1d1b; --muted: 6b6b66; --line: e2e0d5; --green: 136f63; --green-soft: e3f0ee; --red: b3261e; --red-soft: f9e7e6; --idle: 9a988e; --focus: 136f63; } @media prefers-color-scheme: dark { :root { --bg: 14140f; --card: 1e1e18; --ink: f0efe6; --muted: a3a299; --line: 33332a; --green: 4cc2a9; --green-soft: 11332e; --red: ff7a70; --red-soft: 3a1715; --idle: 6e6d64; --focus: 4cc2a9; } } { box-sizing: border-box; } html, body { margin: 0; padding: 0; } body { background: var --bg ; color: var --ink ; font: 16px/1.5 system-ui, -apple-system, "Segoe UI", Roboto, sans-serif; min-height: 100dvh; display: flex; justify-content: c… Evidence: `verifier/index.html`
- **Export** (source_file): import { getEntriesByIds, getChain } from "../db.js"; import { ToolResponse, ExportBundle } from "../types.js"; ⋮---- export function exportEntries args: Evidence: `src/tools/export.ts`
- **Recall** (source_file): import { searchEntries, searchEntriesFlexible, entryCount } from "../db.js"; import { ToolResponse } from "../types.js"; ⋮---- export function recall args: Evidence: `src/tools/recall.ts`
- **Remember** (source_file): import { randomUUID } from "node:crypto"; import { ToolResponse } from "../types.js"; import { hashContent, hashEntry, buildEntryCanonical } from "../hashing.js"; import { insertEntryAtomic } from "../db.js"; ⋮---- export function remember args: Evidence: `src/tools/remember.ts`
- **Tsconfig** (structured_config): { "compilerOptions": { "target": "ES2022", "module": "ESNext", "moduleResolution": "bundler", "outDir": "dist", "rootDir": "src", "strict": true, "esModuleInterop": true, "skipLibCheck": true, "forceConsistentCasingInFileNames": true, "declaration": true }, "include": "src/ / " } Evidence: `tsconfig.json`
- **Vercel** (structured_config): { "buildCommand": "npm run build", "outputDirectory": "." } Evidence: `vercel.json`
- **.gitignore** (source_file): node modules/ dist/ .db .env .env. .log .DS Store seed.mjs anchor-out/ demo/evidence/latest.eco demo/evidence/latest.json demo/state.json .vercel .env Evidence: `.gitignore`
- **.npmignore** (source_file): src/ seed.mjs tsconfig.json node modules/ .db .env .env. .log .DS Store anchor-out/ demo/evidence/ demo/state.json .tgz Evidence: `.npmignore`
- **Dashboard** (source_file): Verifiable Memory MCP — Live Agent Demo :root { --bg: 0b0f14; --panel: 131a22; --border: 243140; --text: d7e2ec; --muted: 7f93a6; --ok: 34d399; --warn: fbbf24; --bad: f87171; --accent: 60a5fa; --orange: fb923c; } { box-sizing: border-box; } body { margin: 0; font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace; background: var --bg ; color: var --text ; padding: 24px; } h1 { font-size: 18px; margin: 0 0 4px; } h2 { font-size: 13px; margin: 0 0 10px; color: var --accent ; text-transform: uppercase; letter-spacing: 0.08em; } h3 { font-size: 12px; margin: 0 0 6px; color: var --muted ; text-transform: uppercase; letter-spacing: 0.06em; } .sub { color: var --muted ; font-size: 1… Evidence: `demo/dashboard.html`
- **E2E** (source_file): function runStep label, command, args, expectedCodes = 0 Evidence: `demo/e2e.mjs`
- **Evidence Package** (source_file): function sha256 text ⋮---- function padCycle cycle ⋮---- function buildAuthoritySummary state ⋮---- function buildPolicySummary state ⋮---- function buildLedgerSummary state ⋮---- function buildAssetsIndex state ⋮---- function artifactType decision, cycle ⋮---- function lifecycleValue decision ⋮---- function packageStatus decision, memory ⋮---- function reportFor manifest, state ⋮---- export async function createEvidencePackage { state, cycle, decision, memory, failedEntry = null, label = null, dataDir = resolveDemoDataDir , } Evidence: `demo/evidence-package.mjs`
- **Reset** (source_file): set -e DEMO DIR="${VMCP DATA DIR:-${VMCP DEMO DIR:-/tmp/vmcp-agent-demo}}" HERE="$ cd "$ dirname "${BASH SOURCE 0 }" " && pwd " rm -rf "$DEMO DIR" mkdir -p "$DEMO DIR" rm -f "$HERE/state.json" rm -rf "$HERE/evidence" echo "Demo memory reset." echo "Data dir: $DEMO DIR" echo "Dashboard state reset." Evidence: `demo/reset.sh`
- **Tamper** (source_file): demo dir = os.environ.get "VMCP DATA DIR" or os.environ.get "VMCP DEMO DIR", "/tmp/vmcp-agent-demo" db path = os.path.join demo dir, "memory.db" ⋮---- conn = sqlite3.connect db path Evidence: `demo/tamper.py`
- **Telegram Alert** (source_file): export function telegramConfigured ⋮---- async function sendRaw text ⋮---- export async function sendIntegrityStopAlert ⋮---- export async function sendOwnerReviewAlert Evidence: `demo/telegram-alert.mjs`
- **Telegram Bot** (source_file): function apiUrl method ⋮---- async function sendMessage text ⋮---- function runStep command, args, expectedCodes ⋮---- async function runCommand command ⋮---- function evidenceLinks ⋮---- function statusText ⋮---- function helpText ⋮---- async function poll Evidence: `demo/telegram-bot.mjs`
- **Hashing.Test** (source_file): import { describe, it, expect } from "vitest"; import { sha256, hashContent, hashEntry, buildEntryCanonical } from "../src/hashing.js"; Evidence: `test/hashing.test.ts`
- **Memory.Test** (source_file): import { describe, it, expect, beforeEach, afterEach, vi } from "vitest"; import { mkdtempSync, rmSync } from "node:fs"; import { tmpdir } from "node:os"; import { join } from "node:path"; import Database from "better-sqlite3"; ⋮---- function parse res: any : any ⋮---- function rawDb : InstanceType Evidence: `test/memory.test.ts`
- **State Root.Test** (source_file): import { describe, it, expect, beforeEach, afterEach, vi } from "vitest"; import { mkdtempSync, rmSync } from "node:fs"; import { tmpdir } from "node:os"; import { join } from "node:path"; ⋮---- function parse res: any : any ⋮---- async function loadTools : Promise ⋮---- constructor ⋮---- setPassword password: string : void ⋮---- getPassword : string null ⋮---- deletePassword : boolean ⋮---- private key : string Evidence: `test/state-root.test.ts`
- **Sample Bundle** (source_file): 2901e42551170951ce9f1fd5f72ac9a4e6538a83dbb2942c5820b108d19d67d1 sample-bundle.json Evidence: `verifier/sample-bundle.sha256`

## Rules the Host AI Must Follow

- **Treat this asset as pre-work context, not a runtime environment.**: The AI Context Pack contains only an evidence-backed understanding of the project, not the project's executable state. Evidence: `README.md`, `verifier/README.md`, `package.json`
- **When answering the user, distinguish what can be previewed from what can only be verified after install.**: The consumer value of the pre-install experience comes from reducing bad installs and misjudgments, not from pretending to be a real run. Evidence: `README.md`, `verifier/README.md`, `package.json`

## 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 and Core Concepts**: importance `high`
  - source_paths: README.md, package.json, src/types.ts, src/hashing.ts
- **MCP Server Architecture and Tools**: importance `high`
  - source_paths: src/index.ts, src/db.ts, src/hashing.ts, src/types.ts, src/tools/remember.ts
- **Evidence System, Verifier and Anchors**: importance `high`
  - source_paths: src/tools/export.ts, verifier/index.html, verifier/README.md, verifier/acceptance.mjs, verifier/anchor.sh
- **Demo Flows, Scenarios, Operations and Ecosystem**: importance `high`
  - source_paths: demo/setup.mjs, demo/common.mjs, demo/agent-loop.mjs, demo/mcp-client.mjs, demo/authorized-source-update.mjs

## Repo Inspection Evidence

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `a40c258d10caef8d14237e3b9f0737e1dd94e408`
- inspected_files: `README.md`, `package.json`, `docs/strategy/eco-and-ecox-model.md`, `docs/strategy/eco-verifier-universal.md`, `docs/strategy/transparent-agent-evidence.md`, `docs/superpowers/plans/2026-06-14-vmcp-demo-e2e.md`, `docs/superpowers/plans/2026-06-24-interactive-sandbox.md`, `docs/superpowers/specs/2026-06-24-interactive-sandbox-design.md`, `src/db.ts`, `src/hashing.ts`, `src/index.ts`, `src/tools/chain.ts`, `src/tools/export.ts`, `src/tools/recall.ts`, `src/tools/remember.ts`, `src/tools/timeline.ts`, `src/tools/verify.ts`, `src/types.ts`

Host AI hard rules:
- Without repo_clone_verified=true, do not claim that the source code has been read.
- Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts.
- Without quick_start_verified=true, do not claim that the Quick Start path has run successfully.

## Doramagic Pitfall Constraints

These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes.

### Constraint 1: 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/TemporalDynamics/verifiable-memory-mcp
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 2: Security or permission risk requires verification

- Trigger: no_demo
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: downstream_validation.risk_items | https://github.com/TemporalDynamics/verifiable-memory-mcp
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 3: Security or permission risk requires verification

- Trigger: no_demo
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: risks.scoring_risks | https://github.com/TemporalDynamics/verifiable-memory-mcp
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 4: Maintenance risk requires verification

- Trigger: issue_or_pr_quality=unknown。
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://github.com/TemporalDynamics/verifiable-memory-mcp
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 5: Maintenance risk requires verification

- Trigger: release_recency=unknown。
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://github.com/TemporalDynamics/verifiable-memory-mcp
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.