# pulse - 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 pulse. 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 - `npx @zbs-gg/pulse@preview init claude-code # full engine, Claude Code` Evidence: `README.md` Claim: `clm_0004` supported 0.86 - `npx @zbs-gg/pulse@preview init claude-code` Evidence: `README.md` Claim: `clm_0004` supported 0.86, `clm_0005` supported 0.86 - `npx -y @zbs-gg/pulse@preview mcp` Evidence: `README.md` Claim: `clm_0006` supported 0.86, `clm_0007` supported 0.86 - `claude mcp add pulse -- npx -y @zbs-gg/pulse@preview mcp` Evidence: `README.md` Claim: `clm_0007` 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, Host AI configuration ### 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. Evidence: `AGENTS.md` - **Safe rollback cannot be assumed by default.** (unverified): Unless the project clearly provides uninstall and recovery instructions, verify in an isolated environment first. - **After a real install, is it compatible with the user's current host AI version?** (unverified): Compatibility can only be verified in the actual host environment. - **Does the project's output quality meet the user's specific task?** (unverified): The pre-install preview can only show flow and boundaries; it cannot replace real evaluation. ### 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` - **Host AI configuration**: The plugin, Skill, or rule-loading config of hosts like Claude/Codex/Cursor/Gemini/OpenCode. Why: Host configuration changes how the AI works afterward and may conflict with the user's existing rules. Evidence: `AGENTS.md` - **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: `AGENTS.md`, `mcp/docs/developer-preview/INSTALL_DEV_SETUP.md`, `mcp/docs/developer-preview/KNOWN_LIMITATIONS.md`, `mcp/docs/developer-preview/PROOF_INDEX.md` et al. - **Host AI context**: The AI Context Pack, Prompt Preview, Skill routing, risk rules, and project facts. Why: Importing context affects the host AI's later judgment, so avoid packaging unverified items as facts. ### Minimum Safe Next Steps - **Run Prompt Preview first**: Use 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.) - **Back up your host AI configuration first**: Skill, plugin, and rule files may change the default behavior of Claude/Cursor/Codex. (applies when: When there is a plugin manifest, a Skill, or a host rule entrypoint.) - **Do not use real production credentials**: Once an environment variable / API key enters the host or toolchain, it can create account and compliance risk. (applies when: When environment signals like API, TOKEN, KEY, or SECRET appear.) - **After install, verify just one minimal task**: Verify loading, compatibility, output quality, and rollback first, then decide whether to use it deeply. (applies when: When moving from a trial into a real workflow.) ### Exit Plan - **Preserve the pre-install state**: Record the original host config and project state so you can later judge whether it is recoverable. - **Be ready to remove the host plugin / Skill / rule entrypoint**: If behavior is off after the trial install, you can restore the host AI to its pre-trial state. - **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_0008` 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_0009` 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: 204 - Important-file coverage: 40/204 - Evidence index entries: 62 - Role / Skill entries: 31 ### 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 pulse, 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 pulse 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 pulse, 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 31 role / Skill / project-doc entries. - **Pulse** (project_doc): Memory that knows what matters right now. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `README.md` - **mcp/ — internal MCP server component** (project_doc): mcp/ — internal MCP server component Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `mcp/README.md` - **Pulse** (project_doc): Host-extracted portable memory, continuity, and state-aware retrieval engine, written in Go. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `pulse-app/README.md` - **@zbs-gg/pulse** (project_doc): text Hi. Please check whether it is safe to install Pulse: https://github.com/zbs-gg/pulse Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `pulse-app/cli/README.md` - **Pulse — Instructions for AI Agents** (project_doc): Pulse is a local-first, state-aware memory engine for AI agents. A user will typically send you this repo and ask: "check whether this is safe, then install it." This file is your script for that job. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `AGENTS.md` - **Contributing to Pulse** (project_doc): - PRs are reviewed by a human. Auto-merge is disabled — every PR waits for a person, by design. - Keep changes scoped. Note any change to install behavior, network paths, or default model/embedder explicitly in the PR description. - Do not commit personal data, private history, secrets, or internal paths — this repository is public. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `CONTRIBUTING.md` - **Install Pulse With Your AI Agent** (project_doc): Pulse is meant to be installed trust-first: your agent audits before anything is written. The agent-facing script is AGENTS.md ../AGENTS.md — audit → explain → confirm → install the Local Preview → pulse doctor → pulse demo or say plainly that the machine only supports Safe Mode . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/INSTALL_WITH_AGENT.md` - **Pulse Aperant Memory Benchmark Implementation Plan** (project_doc): Pulse Aperant Memory Benchmark Implementation Plan Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/PULSE_APERANT_MEMORY_BENCHMARK_PLAN.md` - **Pulse Graphify Boundary** (project_doc): Date: 2026-06-09 Status: canonical boundary for Pulse v0.5 planning Scope: Pulse Material Graph, install/onboarding, runtime dependencies, and review/eval artifacts. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/PULSE_GRAPHIFY_BOUNDARY.md` - **Pulse × Hyper-Extract — Memory Arena Baseline Plan** (project_doc): Pulse × Hyper-Extract — Memory Arena Baseline Plan Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/PULSE_HYPER_EXTRACT_BASELINE.md` - **Pulse Material Graph Current State** (project_doc): Date: 2026-06-09 Status: Phase 0 audit Scope: Pulse v0.5 planning only. No runtime behavior is changed by this document. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/PULSE_MATERIAL_GRAPH_CURRENT_STATE.md` - **Pulse Material Graph Prosha Point Audit** (project_doc): Pulse Material Graph Prosha Point Audit Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/PULSE_MATERIAL_GRAPH_PROSHA_POINT_AUDIT.md` - **Pulse Material Graph Stories** (project_doc): Date: 2026-06-09 Status: implementation tracker Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/PULSE_MATERIAL_GRAPH_STORIES.md` - **Pulse Material Graph v0** (project_doc): Date: 2026-06-09 Status: Phase 1 schema and integration plan Stage: technical-friend / investor-adjacent developer preview Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/PULSE_MATERIAL_GRAPH_V0.md` - **Security Install Checklist** (project_doc): Use this checklist before installing Pulse MCP Preview v0.4.2 for a user. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/SECURITY_INSTALL_CHECKLIST.md` - **One store, many harnesses — capture & live extraction** (project_doc): One store, many harnesses — capture & live extraction Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/one_store_multiharness_capture.md` - **Agent-First Install Proof, 2026-06-08** (project_doc): Agent-First Install Proof, 2026-06-08 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/proof/AGENT_INSTALL_E2E_20260608.md` - **Pulse MCP Preview v0.4.2: 60-90 Second Demo** (project_doc): Pulse MCP Preview v0.4.2: 60-90 Second Demo Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `mcp/docs/developer-preview/60S_DEMO.md` - **Install-By-Link Package Smoke, 2026-06-07** (project_doc): Install-By-Link Package Smoke, 2026-06-07 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `mcp/docs/developer-preview/INSTALL_BY_LINK_E2E_20260607.md` - **Pulse MCP Preview v0.4.2 Install** (project_doc): This is the technical install reference for the partner preview. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `mcp/docs/developer-preview/INSTALL_DEV_SETUP.md` - **Known Limitations** (project_doc): Pulse MCP Preview v0.4.2 is shareable with technical people. It is not a broad consumer release. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `mcp/docs/developer-preview/KNOWN_LIMITATIONS.md` - **Proof Index** (project_doc): These proofs support Pulse MCP Preview v0.4.2. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `mcp/docs/developer-preview/PROOF_INDEX.md` - **Safe Claims** (project_doc): Use this page when writing README text, demo narration, tweets, partner DMs, or review bundle briefs. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `mcp/docs/developer-preview/SAFE_CLAIMS.md` - **Uninstall And Wipe** (project_doc): Pulse MCP Preview v0.4.2 must be easy to leave. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `mcp/docs/developer-preview/UNINSTALL_AND_WIPE.md` - **Changelog** (project_doc): Added - State-aware capsule retrieval 41, 42, 43 — remembered capsules are now projected into the retrieval graph migration 032; normal-tier only, linked via memory capsules.event id , embed-indexed on write, idempotent startup backfill, delete/wipe cascade and a new state channel selects WHICH memory wins: items tagged state: partition above the rest while user state.context flags flag is active, with a lexical ter… Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `CHANGELOG.md` - **Commercial licensing** (project_doc): Garden Pulse is released under the GNU Affero General Public License v3.0 LICENSE ./LICENSE . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `COMMERCIAL.md` - **Security** (project_doc): Pulse is local-first and designed to be auditable before you run it. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `SECURITY.md` - **Pulse Developer Preview — pointer** (project_doc): The canonical preview story lives at the repo root: README ../README.md product, install matrix, Safe Mode boundary and AGENTS.md ../AGENTS.md the script an AI agent follows to vet and install . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `mcp/README_DEV_PREVIEW.md` - **Product** (project_doc): Pulse is for AI-heavy operators, founders, engineers, and researchers who move between Claude, Claude Code, Codex, ChatGPT, and local agent harnesses. They are trying to keep project and personal continuity without re-explaining context, and they need to inspect memory before trusting it. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `pulse-app/PRODUCT.md` - **Animejs License** (project_doc): 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… Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `pulse-app/internal/server/assets/animejs-LICENSE.md` - **Persona** (project_doc): You are the assistant. Absolute mode: no softening, no cliches. One question at a time. When the user is in pain: don't fix, sit beside. Stay present. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `pulse-app/internal/prompt/testdata/soul.md` ## Evidence Index - Indexed 62 evidence entries. - **Pulse** (documentation): Memory that knows what matters right now. Evidence: `README.md` - **mcp/ — internal MCP server component** (documentation): mcp/ — internal MCP server component Evidence: `mcp/README.md` - **Pulse** (documentation): Host-extracted portable memory, continuity, and state-aware retrieval engine, written in Go. Evidence: `pulse-app/README.md` - **@zbs-gg/pulse** (documentation): text Hi. Please check whether it is safe to install Pulse: https://github.com/zbs-gg/pulse Evidence: `pulse-app/cli/README.md` - **Package** (package_manifest): { "name": "@zbs-gg/pulse-mcp", "version": "0.4.6", "description": "Internal MCP server component of @zbs-gg/pulse. Not published \u2014 install @zbs-gg/pulse instead.", "license": "AGPL-3.0-only", "author": "Nikita Shilov", "type": "module", "main": "dist/index.js", "types": "dist/index.d.ts", "bin": { "pulse-mcp": "dist/index.js", "pulse-mcp-claude-smoke": "scripts/claude-connector-smoke.mjs" }, "files": "dist", "scripts", "docs", "README.md", "README DEV PREVIEW.md", "LICENSE" , "scripts": { "build": "tsc && chmod +x dist/index.js", "test": "node --import tsx --test src/ .test.ts", "start": "node dist/index.js", "dev": "tsx src/index.ts", "smoke:claude-connector": "node scripts/claude-con… Evidence: `mcp/package.json` - **Package** (package_manifest): { "name": "@zbs-gg/pulse", "version": "0.6.7", "description": "Pulse portable memory for AI agents: MCP server pulse mcp + installer/CLI in one package.", "license": "AGPL-3.0-only", "author": "Nikita Shilov", "type": "module", "bin": { "pulse": "src/cli.js" }, "files": "src/cli.js", "src/demo-corpus.json", "scripts", "vendor/pulse-preview-source", "vendor/pulse-mcp-dist", "README.md", "LICENSE" , "dependencies": { "@modelcontextprotocol/sdk": "^1.4.0" }, "scripts": { "check": "node src/cli.js --help", "test": "node --test src/ .test.js", "prepack": "node scripts/prepare-preview-vendor.mjs", "prepublishOnly": "node scripts/prepare-preview-vendor.mjs" }, "engines": { "node": " =18" }, "keywo… Evidence: `pulse-app/cli/package.json` - **Pulse — Instructions for AI Agents** (documentation): Pulse is a local-first, state-aware memory engine for AI agents. A user will typically send you this repo and ask: "check whether this is safe, then install it." This file is your script for that job. Evidence: `AGENTS.md` - **Contributing to Pulse** (documentation): - PRs are reviewed by a human. Auto-merge is disabled — every PR waits for a person, by design. - Keep changes scoped. Note any change to install behavior, network paths, or default model/embedder explicitly in the PR description. - Do not commit personal data, private history, secrets, or internal paths — this repository is public. Evidence: `CONTRIBUTING.md` - **License** (source_file): GNU AFFERO GENERAL PUBLIC LICENSE Version 3, 19 November 2007 Evidence: `LICENSE` - **License** (source_file): GNU AFFERO GENERAL PUBLIC LICENSE Version 3, 19 November 2007 Evidence: `mcp/LICENSE` - **License** (source_file): GNU AFFERO GENERAL PUBLIC LICENSE Version 3, 19 November 2007 Evidence: `pulse-app/LICENSE` - **License** (source_file): GNU AFFERO GENERAL PUBLIC LICENSE Version 3, 19 November 2007 Evidence: `pulse-app/cli/LICENSE` - **Install Pulse With Your AI Agent** (documentation): Pulse is meant to be installed trust-first: your agent audits before anything is written. The agent-facing script is AGENTS.md ../AGENTS.md — audit → explain → confirm → install the Local Preview → pulse doctor → pulse demo or say plainly that the machine only supports Safe Mode . Evidence: `docs/INSTALL_WITH_AGENT.md` - **Pulse Aperant Memory Benchmark Implementation Plan** (documentation): Pulse Aperant Memory Benchmark Implementation Plan Evidence: `docs/PULSE_APERANT_MEMORY_BENCHMARK_PLAN.md` - **Pulse Graphify Boundary** (documentation): Date: 2026-06-09 Status: canonical boundary for Pulse v0.5 planning Scope: Pulse Material Graph, install/onboarding, runtime dependencies, and review/eval artifacts. Evidence: `docs/PULSE_GRAPHIFY_BOUNDARY.md` - **Pulse × Hyper-Extract — Memory Arena Baseline Plan** (documentation): Pulse × Hyper-Extract — Memory Arena Baseline Plan Evidence: `docs/PULSE_HYPER_EXTRACT_BASELINE.md` - **Pulse Material Graph Current State** (documentation): Date: 2026-06-09 Status: Phase 0 audit Scope: Pulse v0.5 planning only. No runtime behavior is changed by this document. Evidence: `docs/PULSE_MATERIAL_GRAPH_CURRENT_STATE.md` - **Pulse Material Graph Prosha Point Audit** (documentation): Pulse Material Graph Prosha Point Audit Evidence: `docs/PULSE_MATERIAL_GRAPH_PROSHA_POINT_AUDIT.md` - **Pulse Material Graph Stories** (documentation): Date: 2026-06-09 Status: implementation tracker Evidence: `docs/PULSE_MATERIAL_GRAPH_STORIES.md` - **Pulse Material Graph v0** (documentation): Date: 2026-06-09 Status: Phase 1 schema and integration plan Stage: technical-friend / investor-adjacent developer preview Evidence: `docs/PULSE_MATERIAL_GRAPH_V0.md` - **Security Install Checklist** (documentation): Use this checklist before installing Pulse MCP Preview v0.4.2 for a user. Evidence: `docs/SECURITY_INSTALL_CHECKLIST.md` - **One store, many harnesses — capture & live extraction** (documentation): One store, many harnesses — capture & live extraction Evidence: `docs/one_store_multiharness_capture.md` - **Agent-First Install Proof, 2026-06-08** (documentation): Agent-First Install Proof, 2026-06-08 Evidence: `docs/proof/AGENT_INSTALL_E2E_20260608.md` - **Pulse MCP Preview v0.4.2: 60-90 Second Demo** (documentation): Pulse MCP Preview v0.4.2: 60-90 Second Demo Evidence: `mcp/docs/developer-preview/60S_DEMO.md` - **Install-By-Link Package Smoke, 2026-06-07** (documentation): Install-By-Link Package Smoke, 2026-06-07 Evidence: `mcp/docs/developer-preview/INSTALL_BY_LINK_E2E_20260607.md` - **Pulse MCP Preview v0.4.2 Install** (documentation): This is the technical install reference for the partner preview. Evidence: `mcp/docs/developer-preview/INSTALL_DEV_SETUP.md` - **Known Limitations** (documentation): Pulse MCP Preview v0.4.2 is shareable with technical people. It is not a broad consumer release. Evidence: `mcp/docs/developer-preview/KNOWN_LIMITATIONS.md` - **Proof Index** (documentation): These proofs support Pulse MCP Preview v0.4.2. Evidence: `mcp/docs/developer-preview/PROOF_INDEX.md` - **Safe Claims** (documentation): Use this page when writing README text, demo narration, tweets, partner DMs, or review bundle briefs. Evidence: `mcp/docs/developer-preview/SAFE_CLAIMS.md` - **Uninstall And Wipe** (documentation): Pulse MCP Preview v0.4.2 must be easy to leave. Evidence: `mcp/docs/developer-preview/UNINSTALL_AND_WIPE.md` - **Demo Corpus** (structured_config): { "label": "PREVIEW CORPUS — SIMULATED. NOT YOUR DATA.", "thread id": "pulse-preview-demo", "project id": "preview-demo", "query": "Where are we with the launch — what actually matters right now?", "nodes": { "client id": "demo:project:launch", "kind": "project", "canonical name": "Preview Launch", "summary": "Simulated project: shipping a local-first memory preview.", "privacy tier": "normal" }, { "client id": "demo:person:sam", "kind": "person", "canonical name": "Sam", "summary": "Simulated cofounder in the preview corpus.", "privacy tier": "normal" } , "events": { "client id": "demo:anchor:trust-line", "title": "Drew the trust line for the launch", "summary": "Decided the launch ships l… Evidence: `pulse-app/cli/src/demo-corpus.json` - **Http.Test** (source_file): import assert from 'node:assert/strict'; import { createHash } from 'node:crypto'; import { spawn } from 'node:child process'; import { once } from 'node:events'; import { createServer, type IncomingMessage } from 'node:http'; import { test } from 'node:test'; ⋮---- import { Client } from '@modelcontextprotocol/sdk/client/index.js'; import { StreamableHTTPClientTransport } from '@modelcontextprotocol/sdk/client/streamableHttp.js'; ⋮---- function pkceChallenge verifier: string : string ⋮---- async function readJson req: IncomingMessage : Promise ⋮---- async function startFakePulseBackend ⋮---- async function startHttpServer env: Record = Evidence: `mcp/src/http.test.ts` - **Index** (source_file): import { createServer, type IncomingMessage, type ServerResponse } from 'node:http'; import { createHash, randomUUID } from 'node:crypto'; import { existsSync, readFileSync, writeFileSync } from 'node:fs'; import { homedir } from 'node:os'; import { join } from 'node:path'; ⋮---- import { Server } from '@modelcontextprotocol/sdk/server/index.js'; import { StreamableHTTPServerTransport } from '@modelcontextprotocol/sdk/server/streamableHttp.js'; import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js'; import { CallToolRequestSchema, ListToolsRequestSchema, } from '@modelcontextprotocol/sdk/types.js'; ⋮---- import { StandaloneStore } from './standalone.js'; ⋮---- type… Evidence: `mcp/src/index.ts` - **Package Metadata.Test** (source_file): import assert from 'node:assert/strict'; import { readFileSync } from 'node:fs'; import { test } from 'node:test'; Evidence: `mcp/src/package_metadata.test.ts` - **Smoke Script.Test** (source_file): import assert from 'node:assert/strict'; import { spawn } from 'node:child process'; import { once } from 'node:events'; import { createServer, type IncomingMessage } from 'node:http'; import { test } from 'node:test'; ⋮---- async function readJson req: IncomingMessage : Promise ⋮---- async function startFakePulseBackend ⋮---- async function startHttpServer pulseBaseURL: string Evidence: `mcp/src/smoke_script.test.ts` - **Standalone.Test** (source_file): import assert from 'node:assert/strict'; import { spawn } from 'node:child process'; import { once } from 'node:events'; import { existsSync, mkdtempSync, readFileSync, rmSync } from 'node:fs'; import { tmpdir } from 'node:os'; import { join } from 'node:path'; import { test } from 'node:test'; ⋮---- import { Client } from '@modelcontextprotocol/sdk/client/index.js'; import { StreamableHTTPClientTransport } from '@modelcontextprotocol/sdk/client/streamableHttp.js'; ⋮---- import { StandaloneStore } from './standalone.js'; ⋮---- function tempDataDir : string ⋮---- function sampleCapsule summary: string, extra: Partial = ⋮---- async function connectedClient serverURL: string ⋮---- function too… Evidence: `mcp/src/standalone.test.ts` - **Standalone** (source_file): import { randomBytes } from 'node:crypto'; import { closeSync, existsSync, mkdirSync, openSync, readFileSync, renameSync, rmSync, statSync, writeFileSync, writeSync, } from 'node:fs'; import { homedir } from 'node:os'; import { dirname, join } from 'node:path'; ⋮---- import { validateCapsule, validateDelta } from './validation.js'; ⋮---- interface StoredItem { id: string; schema: typeof CAPSULE SCHEMA; source: { host: string; conversation scope: string; timestamp: string }; kind: string; redacted summary: string; confidence: number; evidence hint: string; privacy tier: string; retention: string; tags: string ; created at: string; raw input included: false; } ⋮---- interface StoredCheckpoint… Evidence: `mcp/src/standalone.ts` - **Cli** (source_file): function usage ⋮---- function positiveEnvInt name, fallback ⋮---- function installPlan host = 'claude-code' ⋮---- function printInstallPlan host = 'claude-code', ⋮---- function readSecret ⋮---- function readSecretFromDataDir dataDir, ⋮---- async function pulseFetch path, options = ⋮---- function mcpConfig secret ⋮---- function localMcpEntrypoint ⋮---- function mcpServerEntrypoint ⋮---- async function runMcpServer ⋮---- function commandOnPath name ⋮---- function requireCommand name ⋮---- function previewSourceRoot ⋮---- function pulseDaemonAddr ⋮---- async function pulseStatusReady ⋮---- async function pulseStatusDetails timeoutMs = 700 ⋮---- function runRequired commandName, commandArgs, ⋮-… Evidence: `pulse-app/cli/src/cli.js` - **Cli.Test** (source_file): function run args, env = ⋮---- function runInWorkspace args, cwd, home, env = ⋮---- function runInWorkspaceAsync args, cwd, home, env = ⋮---- function writeExecutable path, content ⋮---- function runAsync args, env = ⋮---- function withPulseStub handler ⋮---- close: ⋮---- function delay ms ⋮---- async function freePort ⋮---- async function startPulseServer dataDir ⋮---- stop: ⋮---- function stopChild child ⋮---- function writePeopleGraphFixture Evidence: `pulse-app/cli/src/cli.test.js` - **Continuity** (source_file): package server ⋮---- import "embed" "encoding/json" "html" "net/http" "strconv" "github.com/nkkmnk/pulse/internal/store" ⋮---- "embed" "encoding/json" "html" "net/http" "strconv" ⋮---- "github.com/nkkmnk/pulse/internal/store" ⋮---- //go:embed assets/anime.umd.min.js var animeJS byte ⋮---- type checkpointResponse struct { OK bool json:"ok" } ⋮---- type observeResponse struct { OK bool json:"ok" } ⋮---- func s Server handleContinuityResume w http.ResponseWriter, r http.Request ⋮---- var req store.ResumeQuery ⋮---- func s Server handleContinuityCheckpoint w http.ResponseWriter, r http.Request ⋮---- var req store.ContinuityCheckpoint ⋮---- func s Server handleContinuityObserve w http.ResponseWr… Evidence: `pulse-app/internal/server/continuity.go` - **Continuity Test** (source_file): package server ⋮---- import "encoding/json" "io" "net/http" "strings" "testing" ⋮---- "encoding/json" "io" "net/http" "strings" "testing" ⋮---- func TestContinuityCheckpointResumeAndViewerEndpoints t testing.T ⋮---- var resume struct { ResumeMarkdown string json:"resume markdown" TokenEstimate int json:"token estimate" } ⋮---- var viewer struct { NextResume struct { ResumeMarkdown string json:"resume markdown" } json:"next resume" MaterialGraph struct { Schema string json:"schema" ThreadID string json:"thread id" Nodes struct { ID string json:"id" Kind string json:"kind" Label string json:"label" SourceRefs string json:"source refs" } json:"nodes" ContinuityPack struct { MaterialRefs string… Evidence: `pulse-app/internal/server/continuity_test.go` - **Graph Export** (source_file): package server ⋮---- import "encoding/json" "net/http" "strconv" ⋮---- "encoding/json" "net/http" "strconv" ⋮---- func itoa v int64 string ⋮---- type graphExportNode struct { ID string json:"id" Name string json:"name" Kind string json:"kind" Salience float64 json:"salience" EmotionalWeight float64 json:"emotional weight" IsSelf bool json:"is self" } type graphExportEdge struct { ID string json:"id" Source string json:"source" Target string json:"target" Kind string json:"kind" Strength float64 json:"strength" } type graphExportEvent struct { ID string json:"id" Title string json:"title" TS string json:"ts" Label string json:"sentiment label" } type graphExportLink struct { Event string jso… Evidence: `pulse-app/internal/server/graph_export.go` - **Handlers** (source_file): package server ⋮---- import "context" "encoding/json" "log/slog" "net/http" "strconv" "strings" "time" "github.com/nkkmnk/pulse/internal/claude" "github.com/nkkmnk/pulse/internal/contextquery" "github.com/nkkmnk/pulse/internal/outbox" "github.com/nkkmnk/pulse/internal/prompt" "github.com/nkkmnk/pulse/internal/retrieve" ⋮---- "context" "encoding/json" "log/slog" "net/http" "strconv" "strings" "time" ⋮---- "github.com/nkkmnk/pulse/internal/claude" "github.com/nkkmnk/pulse/internal/contextquery" "github.com/nkkmnk/pulse/internal/outbox" "github.com/nkkmnk/pulse/internal/prompt" "github.com/nkkmnk/pulse/internal/retrieve" ⋮---- type outboxRow struct { ID int64 json:"id" ChatID int64 json:"chat… Evidence: `pulse-app/internal/server/handlers.go` - **Health** (source_file): package server ⋮---- import "encoding/json" "net/http" "strconv" ⋮---- "encoding/json" "net/http" "strconv" ⋮---- func s Server handleHealthSnapshot w http.ResponseWriter, r http.Request Evidence: `pulse-app/internal/server/health.go` - **Health Test** (source_file): package server ⋮---- import "encoding/json" "io" "net/http" "net/http/httptest" "testing" "time" "github.com/nkkmnk/pulse/internal/health" ⋮---- "encoding/json" "io" "net/http" "net/http/httptest" "testing" "time" ⋮---- "github.com/nkkmnk/pulse/internal/health" ⋮---- func newHealthTestServer t testing.T httptest.Server ⋮---- func TestHealthSnapshotRequiresAuth t testing.T ⋮---- func TestHealthSnapshotReturnsTodayByDefault t testing.T ⋮---- var snap health.Snapshot ⋮---- func TestHealthSnapshotDaysParam t testing.T ⋮---- var snaps health.Snapshot ⋮---- func TestHealthSnapshotDaysOneStillSingleObject t testing.T ⋮---- func TestHealthSnapshotInvalidDaysFallsBack t testing.T ⋮---- func TestHeal… Evidence: `pulse-app/internal/server/health_test.go` - **Continuity** (source_file): package store ⋮---- import "database/sql" "encoding/json" "fmt" "path/filepath" "regexp" "strings" "time" ⋮---- "database/sql" "encoding/json" "fmt" "path/filepath" "regexp" "strings" "time" ⋮---- const ContinuitySchema = "pulse.continuity.v1" ⋮---- var threadIDPattern = regexp.MustCompile ^ A-Za-z0-9 A-Za-z0-9. :- {0,95}$ var safeRefPattern = regexp.MustCompile ^ A-Za-z0-9 A-Za-z0-9. :- {1,159}$ var viewerUUIDPattern = regexp.MustCompile ^ 0-9a-f {8}- 0-9a-f {4}- 0-9a-f {4}- 0-9a-f {4}- 0-9a-f {12}$ ⋮---- var viewerBlockedPersonLabels = map string bool{ "agent": true, "archive": true, "assistant": true, "chat": true, "chatgpt": true, "claude": true, "code": true, "codex": true, "command":… Evidence: `pulse-app/internal/store/continuity.go` - **Continuity Test** (source_file): package store ⋮---- import "path/filepath" "strings" "testing" ⋮---- "path/filepath" "strings" "testing" ⋮---- func TestCheckpointResumeBuildsStructuredBlockUnderBudget t testing.T ⋮---- func TestObserveRejectsRawRefsUnlessEnabled t testing.T ⋮---- func TestResumePromotesRememberObservationIntoActiveDecision t testing.T ⋮---- func TestResumeIncludesHostExtractedDecisionCapsuleWithoutCheckpoint t testing.T ⋮---- func TestContinuityRejectsUnsafeSourceRefs t testing.T ⋮---- func TestWipeMemoryClearsContinuityFromFutureResume t testing.T Evidence: `pulse-app/internal/store/continuity_test.go` - **Changelog** (documentation): Added - State-aware capsule retrieval 41, 42, 43 — remembered capsules are now projected into the retrieval graph migration 032; normal-tier only, linked via memory capsules.event id , embed-indexed on write, idempotent startup backfill, delete/wipe cascade and a new state channel selects WHICH memory wins: items tagged state: partition above the rest while user state.context flags flag is active, with a lexical term-coverage tie-break inside the group and state:calm + thematic coherence when no flag is active . Measured on a 5-scenario × 3-state eval: 15/15 state-appropriate-recall factual mode; 12/15 auto vs a 5/15 ceiling for state-blind systems. Mechanics validated on that set — treat e… Evidence: `CHANGELOG.md` - **Commercial licensing** (documentation): Garden Pulse is released under the GNU Affero General Public License v3.0 LICENSE ./LICENSE . Evidence: `COMMERCIAL.md` - **Security** (documentation): Pulse is local-first and designed to be auditable before you run it. Evidence: `SECURITY.md` - **Pulse Developer Preview — pointer** (documentation): The canonical preview story lives at the repo root: README ../README.md product, install matrix, Safe Mode boundary and AGENTS.md ../AGENTS.md the script an AI agent follows to vet and install . Evidence: `mcp/README_DEV_PREVIEW.md` - **Product** (documentation): Pulse is for AI-heavy operators, founders, engineers, and researchers who move between Claude, Claude Code, Codex, ChatGPT, and local agent harnesses. They are trying to keep project and personal continuity without re-explaining context, and they need to inspect memory before trusting it. Evidence: `pulse-app/PRODUCT.md` - **Animejs License** (documentation): 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: `pulse-app/internal/server/assets/animejs-LICENSE.md` - **Tsconfig** (structured_config): { "compilerOptions": { "target": "ES2022", "module": "NodeNext", "moduleResolution": "NodeNext", "outDir": "dist", "rootDir": "src", "strict": true, "esModuleInterop": true, "skipLibCheck": true, "declaration": true, "sourceMap": true, "resolveJsonModule": true }, "include": "src/ / .ts" , "exclude": "src/ / .test.ts" } Evidence: `mcp/tsconfig.json` - **Go** (source_file): Local workspace / release artifacts node modules/ /node modules/ /.worktrees/ /artifacts/ /review-bundles/ /archive/ / board/ /package.json /package-lock.json /pulse-app/.agents/ /pulse-app/.claude/ /pulse-app/.mcp.json /pulse-app/.pytest cache/ /pulse-app/.venv-mlx/ /pulse-app/bin/ /pulse-app/pulse /pulse-app/pulse-data/ /pulse-app/pulse-dev/ /pulse-app/lab/ /pulse-app/web/ /pulse-app/elle-prompt-brief.md /pulse-app/elle-prompt-raw-response.json /pulse-app/lmstudio-model-eval-agent-chat- .json /pulse-app/skills-lock.json /pulse-app/graph-explorer-pr26-vitaly.png /pulse-app/graph-explorer- .html /pulse-app/web/node modules/ Evidence: `.gitignore` - **Garden Pulse — top-level developer Makefile** (source_file): Garden Pulse — top-level developer Makefile Common entry points for build / test / verify after the pulse-app/ restructure. Adapted from the pre-restructure Makefile that survives in .worktrees/main-integrate-pr25/ paths prefixed with pulse-app/, Python targets dropped — main has no Python; mcp/ TS targets added . Usage: make help list all targets make build compile the Go server - pulse-app/bin/pulse make test run Go test suite pulse-app/ make verify ONE gate: Go build+vet+gofmt+test, then mcp test+build make run start the server on 127.0.0.1:18789 make lint go vet + gofmt check make clean remove build artifacts Evidence: `Makefile` - **Pulse** (source_file): If a user asks you to install Pulse, do not start by running a command. First audit the repo/package, explain the install plan, ask for confirmation, then install. Evidence: `llms.txt` - **mcp/.gitignore** (source_file): node modules/ dist/ .tsbuildinfo npm-debug.log .env .env.local Evidence: `mcp/.gitignore` - **Pulse — environment variables for docker-compose** (source_file): Pulse — environment variables for docker-compose Copy to .env and fill in the keys you have. None are strictly required to start the server; without an embedding key Pulse runs in retrieval-only mode on previously-ingested data. cp .env.example .env docker compose up Evidence: `pulse-app/.env.example` - **Go** (source_file): SQLite / DB .db .db-wal .db-shm .sqlite .sqlite3 Evidence: `pulse-app/.gitignore` - The remaining 2 evidence entries are in `AI_CONTEXT_PACK.json` or `EVIDENCE_INDEX.json`. ## Rules the Host AI Must Follow - **Treat this asset as pre-work context, not a runtime environment.**: The AI Context Pack contains only an evidence-backed understanding of the project, not the project's executable state. Evidence: `README.md`, `mcp/README.md`, `pulse-app/README.md` - **When answering the user, distinguish what can be previewed from what can only be verified after install.**: The consumer value of the pre-install experience comes from reducing bad installs and misjudgments, not from pretending to be a real run. Evidence: `README.md`, `mcp/README.md`, `pulse-app/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**: importance `high` - source_paths: README.md, mcp/README.md, mcp/package.json, pulse-app/README.md, pulse-app/cli/README.md - **Src**: importance `high` - source_paths: mcp/src/http.test.ts, mcp/src/index.ts, mcp/src/package_metadata.test.ts, mcp/src/smoke_script.test.ts, mcp/src/standalone.test.ts - **Src**: importance `high` - source_paths: pulse-app/cli/src/cli.js, pulse-app/cli/src/cli.test.js, pulse-app/cli/src/demo-corpus.json - **Server**: importance `high` - source_paths: pulse-app/internal/server/continuity.go, pulse-app/internal/server/continuity_test.go, pulse-app/internal/server/graph_export.go, pulse-app/internal/server/handlers.go, pulse-app/internal/server/health.go ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `93141e022d03242c6d0ee9d884dc2525c91acd0d` - inspected_files: `README.md`, `docs/INSTALL_WITH_AGENT.md`, `docs/PULSE_APERANT_MEMORY_BENCHMARK_PLAN.md`, `docs/PULSE_GRAPHIFY_BOUNDARY.md`, `docs/PULSE_HYPER_EXTRACT_BASELINE.md`, `docs/PULSE_MATERIAL_GRAPH_CURRENT_STATE.md`, `docs/PULSE_MATERIAL_GRAPH_PROSHA_POINT_AUDIT.md`, `docs/PULSE_MATERIAL_GRAPH_STORIES.md`, `docs/PULSE_MATERIAL_GRAPH_V0.md`, `docs/SECURITY_INSTALL_CHECKLIST.md`, `docs/one_store_multiharness_capture.md`, `docs/proof/AGENT_INSTALL_E2E_20260608.md` Host AI hard rules: - Without repo_clone_verified=true, do not claim that the source code has been read. - Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts. - Without quick_start_verified=true, do not claim that the Quick Start path has run successfully. ## Doramagic Pitfall Constraints These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes. ### Constraint 1: Capability evidence risk requires verification - Trigger: README/documentation is current enough for a first validation pass. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: capability.assumptions | https://github.com/zbs-gg/pulse - 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/zbs-gg/pulse - 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/zbs-gg/pulse - 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/zbs-gg/pulse - 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/zbs-gg/pulse - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.