# reporecall - 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 reporecall. Treat it as pre-work context: help the user understand who it fits, what it can do, how to start, what must be verified after install, and where the risks are. Do not claim that you have already installed, run, or executed the target project.

## Claim Consumption Rules

- **Fact source**: Repo Evidence + Claim/Evidence Graph; the Human Wiki only supplies salience, terminology, and narrative structure.
- **Minimum status for a fact**: `supported`
- `supported`: May be used as a project fact, but the answer must cite the claim_id and evidence path.
- `weak`: Usable only as a low-confidence lead; the user must be asked to keep verifying.
- `inferred`: Usable only for risk notes or open questions; must not be packaged as a project fact.
- `unverified`: Must not be used as fact; state clearly that evidence is insufficient.
- `contradicted`: Must show the conflicting sources and must not force a single version on the user's behalf.

## Who It Fits Best

- **Developers already using host AIs such as Claude/Codex/Cursor/Gemini**: The README or plugin config mentions multiple host AIs. Evidence: `README.md` Claim: `clm_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 @proofofwork-agency/reporecall` Evidence: `README.md` Claim: `clm_0003` supported 0.86

## Continue-or-Stop Decision Card

- **Current recommendation**: Trial role matching first
- **Why**: This project is more of a role library; the core risk is picking the wrong role or treating role copy as execution capability. Trial role matching with Prompt Preview first, then decide whether to sandbox-import it.

### 30-Second Read

- **What to do now**: Trial role matching first
- **Minimum safe next step**: Trial role matching with Prompt Preview first; import in isolation only once satisfied
- **Do not trust yet**: Role quality and task fit cannot be trusted directly.
- **Continuing will touch**: Role selection bias, Command execution, Local environment or project files

### What You Can Trust Now

- **Target-audience signal: 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_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

- **Role quality and task fit cannot be trusted directly.** (unverified): A role library proves there are many roles; it does not prove each one fits your specific task or that a role produces high-quality results.
- **Do not treat role copy as real execution capability.** (unverified): Before install you can only judge whether the role description and task profile match; you cannot prove it can complete the task inside the host AI.
- **Real output quality cannot be trusted before install.** (unverified): Prompt Preview can only show how it guides you; it cannot prove result quality in the real project.
- **Host AI version compatibility cannot be trusted before install.** (unverified): Host loading rules and version differences across Claude, Cursor, Codex, Gemini, and others must be verified in a real environment.
- **That it will not pollute your existing host AI's behavior cannot be trusted directly.** (inferred): Skill, plugin, and AGENTS/CLAUDE/GEMINI instructions may change the host AI's default behavior.
- **Safe rollback cannot be assumed by default.** (unverified): Unless the project clearly provides uninstall and recovery instructions, verify in an isolated environment first.
- **After a real install, is it compatible with the user's current host AI version?** (unverified): Compatibility can only be verified in the actual host environment.
- **Does the project's output quality meet the user's specific task?** (unverified): The pre-install preview can only show flow and boundaries; it cannot replace real evaluation.

### What Continuing Will Touch

- **Role selection bias**: The user's judgment about which expert role should handle the task. Why: Picking the wrong role makes the AI answer from the wrong expert perspective, wasting time or misleading decisions.
- **Command execution**: Package managers, network downloads, the local plugin directory, project config, or the user's home directory. Why: Running the very first command can already change your environment; decide whether it is worth running first. Evidence: `README.md`
- **Local environment or project files**: Install results, plugin caches, project config, or local dependency directories. Why: The write scope and rollback path cannot be proven before install and need isolated verification. Evidence: `README.md`
- **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.)
- **After install, verify just one minimal task**: Verify loading, compatibility, output quality, and rollback first, then decide whether to use it deeply. (applies when: When moving from a trial into a real workflow.)

### Exit Plan

- **Preserve the pre-install state**: Record the original host config and project state so you can later judge whether it is recoverable.
- **Keep a record of the original role selection**: If output goes off-topic, you can return to the task-profiling stage and reselect a role instead of pushing on with the wrong one.
- **Record the install commands and written paths**: Without clear uninstall instructions, you at least need to know which directories or configs to clean up manually.
- **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_0004` 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_0005` 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: 285
- Important-file coverage: 40/285
- Evidence index entries: 70
- Role / Skill entries: 23

### 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 reporecall, 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 reporecall 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 reporecall, 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 23 role / Skill / project-doc entries.

- **Reporecall** (project_doc): The local-first, auto-injecting, self-aware-about-staleness context + memory layer for coding agents. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `README.md`
- **Benchmark Scripts** (project_doc): Reporecall uses deterministic benchmarks for regression checks and optional live benchmarks for product validation. Prefer deterministic runs before release work; use live runs only when measuring real agent behavior, latency, and cost. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `scripts/benchmarks/README.md`
- **Architecture Overview** (project_doc): Reporecall indexes a project locally and exposes source-grounded context through CLI commands, Claude Code hooks, and MCP tools. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/architecture-overview.md`
- **WP5 Tool Collapse Design Note** (project_doc): - refresh context remains public. WP1/WP3 banners and hook text tell agents to run refresh context ; keeping it avoids breaking the honesty contract. No banner rename needed. - Memory templates from WP2 reference memory actions. To avoid silently re-breaking CLAUDE.md , the surviving memory tool must include both read and write verbs, and src/cli/init.ts plus tests must be updated in the same WP5 commit from store m… Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/design/wp5-tool-collapse.md`
- **Changelog** (project_doc): v0.8.1 — Positioning, Trust & Distribution 2026-07-09 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/docs/changelog.md`
- **Contributing to Reporecall** (project_doc): Reporecall is a local-first codebase context engine for coding agents. Keep changes focused, source-grounded, and easy to verify. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `CONTRIBUTING.md`
- **Changelog** (project_doc): Positioning, Trust & Distribution Improvements toward 9/10 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `CHANGELOG.md`
- **Business Context Schema** (project_doc): Reporecall exposes business-oriented context as an additive view over generated wiki pages. This view is intended for external utilities, planning agents, dashboards, and MCP servers that need product language without changing core code retrieval behavior. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/business-context-schema.md`
- **Reporecall Competitive Positioning July 2026** (project_doc): Reporecall Competitive Positioning July 2026 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/competitive-positioning-2026.md`
- **Release And Verification** (project_doc): Reporecall releases are managed through release-please. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/release-verification.md`
- **Reporecall Context Layer and Competitor Comparison** (project_doc): Reporecall Context Layer and Competitor Comparison Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/reporecall-context-layer-competitor-comparison.md`
- **Reporecall v0.7.0 vs v0.6.2 Comparison** (project_doc): Reporecall v0.7.0 vs v0.6.2 Comparison Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/reporecall-v0.7-comparison.md`
- **Retrieval And Context Pipeline** (project_doc): Reporecall builds context in this order: Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/retrieval-context-pipeline.md`
- **Architecture** (project_doc): Reporecall is the local-first, auto-injecting, self-aware-about-staleness context + memory layer . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/docs/architecture.md`
- **CLI Reference** (project_doc): Every command accepts --project to target a project root other than the current working directory the default is auto-detected from the CWD . Options below are shown with their defaults where they have one. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/docs/cli-reference.md`
- **Reporecall Competitive Positioning July 2026** (project_doc): Reporecall Competitive Positioning July 2026 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/docs/competitive-positioning.md`
- **Configuration** (project_doc): Reporecall reads its configuration from .memory/config.json in the project root created by reporecall init . All keys are optional — anything you omit falls back to a built-in default. Unknown keys are rejected by a strict schema, and the effective config is validated on load. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/docs/configuration.md`
- **Installation & Quick Start** (project_doc): - Node.js = 20 see engines in package.json . - A Unix-compatible shell for Claude Code hooks. On Windows the generated hooks use curl / cat , so Git Bash or WSL must be on your PATH . - No cloud account or API key is required for the default local provider. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/docs/installation.md`
- **Reporecall** (project_doc): Reporecall is the local-first, auto-injecting, self-aware-about-staleness context + memory layer for coding agents. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/docs/intro.md`
- **Architecture Lens** (project_doc): The Lens is Reporecall's architecture dashboard: one command produces a single self-contained HTML file showing your whole codebase at a glance, and the same data is available as a structured JSON export for external tools. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/docs/lens.md`
- **MCP Tools** (project_doc): As of v0.8.0 , Reporecall exposes a deliberately compact 6-tool MCP surface. This is part of the Trust Contract: fewer choices, less confusion, and explicit staleness on every response. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/docs/mcp-tools.md`
- **Persistent Memory** (project_doc): Reporecall maintains persistent project memory across sessions. Memories are Markdown files with frontmatter, stored locally and indexed separately from code. When relevant to a query, they are injected alongside code context — so an agent carries forward rules, decisions, and learned facts instead of rediscovering them every session. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/docs/memory.md`
- **Trust Contract + Token Savings Benchmark Placeholder** (project_doc): Trust Contract + Token Savings Benchmark Placeholder Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `scripts/benchmarks/trust-and-tokens.md`

## Evidence Index

- Indexed 70 evidence entries.

- **Reporecall** (documentation): The local-first, auto-injecting, self-aware-about-staleness context + memory layer for coding agents. Evidence: `README.md`
- **Benchmark Scripts** (documentation): Reporecall uses deterministic benchmarks for regression checks and optional live benchmarks for product validation. Prefer deterministic runs before release work; use live runs only when measuring real agent behavior, latency, and cost. Evidence: `scripts/benchmarks/README.md`
- **Architecture Overview** (documentation): Reporecall indexes a project locally and exposes source-grounded context through CLI commands, Claude Code hooks, and MCP tools. Evidence: `docs/architecture-overview.md`
- **WP5 Tool Collapse Design Note** (documentation): - refresh context remains public. WP1/WP3 banners and hook text tell agents to run refresh context ; keeping it avoids breaking the honesty contract. No banner rename needed. - Memory templates from WP2 reference memory actions. To avoid silently re-breaking CLAUDE.md , the surviving memory tool must include both read and write verbs, and src/cli/init.ts plus tests must be updated in the same WP5 commit from store memory / recall memories / forget memory to memory action=store recall forget . - memory must not carry readOnlyHint: true , because it includes write verbs. It is also exempt from empty code-index short-circuiting because memory storage is independent of code chunks. Evidence: `docs/design/wp5-tool-collapse.md`
- **Changelog** (documentation): v0.8.1 — Positioning, Trust & Distribution 2026-07-09 Evidence: `website/docs/changelog.md`
- **Package** (package_manifest): { "name": "@proofofwork-agency/reporecall", "version": "0.8.1", "description": "Local-first, auto-injecting, self-aware-about-staleness context + memory layer for coding agents Claude Code, Codex, MCP . Trust contract, hooks-first, hybrid retrieval + compression, zero infra.", "type": "module", "main": "./dist/index.js", "types": "./dist/index.d.ts", "exports": { ".": { "import": "./dist/index.js", "types": "./dist/index.d.ts", "default": "./dist/index.js" } }, "repository": { "type": "git", "url": "https://github.com/proofofwork-agency/reporecall.git" }, "bugs": { "url": "https://github.com/proofofwork-agency/reporecall/issues" }, "homepage": "https://github.com/proofofwork-agency/reporeca… Evidence: `package.json`
- **Package** (package_manifest): { "name": "reporecall-docs", "version": "0.0.0", "private": true, "description": "Documentation site for @proofofwork-agency/reporecall", "scripts": { "docusaurus": "docusaurus", "start": "docusaurus start", "build": "docusaurus build", "serve": "docusaurus serve", "clear": "docusaurus clear", "write-translations": "docusaurus write-translations" }, "dependencies": { "@docusaurus/core": "^3.7.0", "@docusaurus/preset-classic": "^3.7.0", "@mdx-js/react": "^3.0.0", "clsx": "^2.1.1", "prism-react-renderer": "^2.4.0", "react": "^18.3.1", "react-dom": "^18.3.1" }, "devDependencies": { "@docusaurus/module-type-aliases": "^3.7.0" }, "browserslist": { "production": " 0.5%", "not dead", "not op mini… Evidence: `website/package.json`
- **Contributing to Reporecall** (documentation): Reporecall is a local-first codebase context engine for coding agents. Keep changes focused, source-grounded, and easy to verify. Evidence: `CONTRIBUTING.md`
- **License** (source_file): Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files the "Software" , to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: Evidence: `LICENSE`
- **Changelog** (documentation): Positioning, Trust & Distribution Improvements toward 9/10 Evidence: `CHANGELOG.md`
- **Business Context Schema** (documentation): Reporecall exposes business-oriented context as an additive view over generated wiki pages. This view is intended for external utilities, planning agents, dashboards, and MCP servers that need product language without changing core code retrieval behavior. Evidence: `docs/business-context-schema.md`
- **Reporecall Competitive Positioning July 2026** (documentation): Reporecall Competitive Positioning July 2026 Evidence: `docs/competitive-positioning-2026.md`
- **Release And Verification** (documentation): Reporecall releases are managed through release-please. Evidence: `docs/release-verification.md`
- **Reporecall Context Layer and Competitor Comparison** (documentation): Reporecall Context Layer and Competitor Comparison Evidence: `docs/reporecall-context-layer-competitor-comparison.md`
- **Reporecall v0.7.0 vs v0.6.2 Comparison** (documentation): Reporecall v0.7.0 vs v0.6.2 Comparison Evidence: `docs/reporecall-v0.7-comparison.md`
- **Retrieval And Context Pipeline** (documentation): Reporecall builds context in this order: Evidence: `docs/retrieval-context-pipeline.md`
- **Architecture** (documentation): Reporecall is the local-first, auto-injecting, self-aware-about-staleness context + memory layer . Evidence: `website/docs/architecture.md`
- **CLI Reference** (documentation): Every command accepts --project to target a project root other than the current working directory the default is auto-detected from the CWD . Options below are shown with their defaults where they have one. Evidence: `website/docs/cli-reference.md`
- **Reporecall Competitive Positioning July 2026** (documentation): Reporecall Competitive Positioning July 2026 Evidence: `website/docs/competitive-positioning.md`
- **Configuration** (documentation): Reporecall reads its configuration from .memory/config.json in the project root created by reporecall init . All keys are optional — anything you omit falls back to a built-in default. Unknown keys are rejected by a strict schema, and the effective config is validated on load. Evidence: `website/docs/configuration.md`
- **Installation & Quick Start** (documentation): - Node.js = 20 see engines in package.json . - A Unix-compatible shell for Claude Code hooks. On Windows the generated hooks use curl / cat , so Git Bash or WSL must be on your PATH . - No cloud account or API key is required for the default local provider. Evidence: `website/docs/installation.md`
- **Reporecall** (documentation): Reporecall is the local-first, auto-injecting, self-aware-about-staleness context + memory layer for coding agents. Evidence: `website/docs/intro.md`
- **Architecture Lens** (documentation): The Lens is Reporecall's architecture dashboard: one command produces a single self-contained HTML file showing your whole codebase at a glance, and the same data is available as a structured JSON export for external tools. Evidence: `website/docs/lens.md`
- **MCP Tools** (documentation): As of v0.8.0 , Reporecall exposes a deliberately compact 6-tool MCP surface. This is part of the Trust Contract: fewer choices, less confusion, and explicit staleness on every response. Evidence: `website/docs/mcp-tools.md`
- **Persistent Memory** (documentation): Reporecall maintains persistent project memory across sessions. Memories are Markdown files with frontmatter, stored locally and indexed separately from code. When relevant to a query, they are injected alongside code context — so an agent carries forward rules, decisions, and learned facts instead of rediscovering them every session. Evidence: `website/docs/memory.md`
- **Doctor** (source_file): import { Command } from 'commander' import { resolve } from 'path' import { existsSync, statSync, readFileSync } from 'fs' import { detectProjectRoot } from '../core/project.js' import { loadConfig } from '../core/config.js' import { isProcessAlive } from '../core/platform.js' import { assertSqliteRuntimeHealthy } from '../storage/sqlite-utils.js' ⋮---- export function doctorCommand : Command Evidence: `src/cli/doctor.ts`
- **Index Cmd** (source_file): import { Command } from 'commander' import { mkdirSync } from 'fs' import { resolve } from 'path' import { detectProjectRoot } from '../core/project.js' import { loadConfig } from '../core/config.js' import { IndexingPipeline } from '../indexer/pipeline.js' import { OllamaEmbedder } from '../indexer/embedder.js' import { assertSqliteRuntimeHealthy } from '../storage/sqlite-utils.js' import { MemoryStore } from '../storage/memory-store.js' import { createMemoryIndexer } from '../memory/indexer.js' import { WikiGenerator } from '../wiki/generator.js' ⋮---- function progressBar current: number, total: number, width: number : string ⋮---- export function indexCommand : Command ⋮---- async funct… Evidence: `src/cli/index-cmd.ts`
- **Init** (source_file): import { Command } from 'commander' import { resolve, relative, dirname } from 'path' import { mkdirSync, writeFileSync, existsSync, readFileSync } from 'fs' import { execFileSync } from 'child process' import { detectProjectRoot } from '../core/project.js' import { loadConfig } from '../core/config.js' import { homedir } from 'os' ⋮---- export function initCommand : Command ⋮---- const buildCurlHook = endpoint: string, matcher?: string : ⋮---- const isMemoryHook = h: unknown : boolean = ⋮---- function escapeXml str: string : string ⋮---- function setupLaunchAgent projectRoot: string : void ⋮---- // Find the Reporecall binary ⋮---- function setupWindowsTask projectRoot: string : void ⋮----… Evidence: `src/cli/init.ts`
- **Mcp** (source_file): import { Command } from "commander"; import { resolve } from "path"; import { mkdirSync, readFileSync } from "fs"; import { detectProjectRoot } from "../core/project.js"; import { loadConfig } from "../core/config.js"; import { IndexingPipeline } from "../indexer/pipeline.js"; import { HybridSearch } from "../search/hybrid.js"; import { createMCPServer } from "../daemon/mcp-server.js"; import { ReadWriteLock } from "../core/rwlock.js"; import { MemoryStore } from "../storage/memory-store.js"; import { createMemoryIndexer } from "../memory/indexer.js"; import { MemorySearch } from "../memory/search.js"; import { MemoryRuntime } from "../daemon/memory/runtime.js"; import { WikiGenerator } fro… Evidence: `src/cli/mcp.ts`
- **Serve** (source_file): import { Command } from 'commander' import { resolve } from 'path' import { openSync, closeSync, writeSync, unlinkSync, mkdirSync, readFileSync } from 'fs' import { detectProjectRoot } from '../core/project.js' import { loadConfig } from '../core/config.js' import { getLogger, setLogDestination, setLogLevel } from '../core/logger.js' import { IndexingPipeline } from '../indexer/pipeline.js' import { HybridSearch } from '../search/hybrid.js' import { FileWatcher } from '../daemon/watcher.js' import { IndexScheduler } from '../daemon/scheduler.js' import { createDaemonServer } from '../daemon/server.js' import { ReadWriteLock } from '../core/rwlock.js' import { isProcessAlive } from '../core/… Evidence: `src/cli/serve.ts`
- **Stats** (source_file): import { Command } from 'commander' import { resolve } from 'path' import { statSync, existsSync, readFileSync, readdirSync } from 'fs' import { detectProjectRoot } from '../core/project.js' import { loadConfig } from '../core/config.js' import { isProcessAlive } from '../core/platform.js' import { MetadataStore } from '../storage/metadata-store.js' import { MemoryStore } from '../storage/memory-store.js' import { resolveMemoryStatus } from '../memory/types.js' import { banner, computeFreshness } from '../core/staleness.js' ⋮---- export function statsCommand : Command ⋮---- // === Trust / Freshness prominent === ⋮---- // Memory stats ⋮---- // Check daemon status ⋮---- function formatBytes b… Evidence: `src/cli/stats.ts`
- **Staleness** (source_file): import { execFileSync } from "child process"; import { statSync } from "fs"; import { resolve } from "path"; ⋮---- export type FreshnessLevel = "fresh" "stale" "empty"; ⋮---- export interface IndexFreshness { lastIndexedAt: string null; indexedCommit: string null; currentCommit: string null; dirtyFiles: number null; level: FreshnessLevel; } ⋮---- export interface FreshnessMetadata { getStats : { totalChunks: number }; getStat key: string : string undefined; } ⋮---- getStats : getStat key: string : string undefined; ⋮---- export interface FreshnessOptions { now?: = number; ttlMs?: number; } ⋮---- interface CacheEntry { key: string; computedAt: number; value: IndexFreshness; } ⋮---- function… Evidence: `src/core/staleness.ts`
- **Mcp Server** (source_file): import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js' import { z } from 'zod' import { resolve, sep } from 'path' import { realpathSync, unlinkSync, mkdirSync } from 'fs' import type { HybridSearch } from '../search/hybrid.js' import type { IndexingPipeline } from '../indexer/pipeline.js' import type { MetadataStore } from '../storage/metadata-store.js' import { type MemoryConfig, resolveContextBudget } from '../core/config.js' import type { ReadWriteLock } from '../core/rwlock.js' import { resolveSeeds } from '../search/seed.js' import { buildStackTree } from '../search/tree-builder.js' import { assembleFlowContext } from '../search/context-assembler.js' import { createRequir… Evidence: `src/daemon/mcp-server.ts`
- **Server** (source_file): import { createServer, type IncomingMessage, type ServerResponse } from "http"; import { type MemoryConfig, resolveContextBudget } from "../core/config.js"; import type { HybridSearch } from "../search/hybrid.js"; import type { MetadataStore } from "../storage/metadata-store.js"; import { handleSessionStart } from "../hooks/session-start.js"; import { handlePromptContextDetailed } from "../hooks/prompt-context.js"; import { evaluatePreToolUse, type HookSessionSnapshot } from "../hooks/pre-tool-use.js"; import { classifyIntent } from "../search/intent.js"; import { getLogger } from "../core/logger.js"; import { mkdirSync, writeFileSync } from "fs"; import { resolve } from "path"; import { Ro… Evidence: `src/daemon/server.ts`
- **Prompt Context** (source_file): import type { HybridSearch } from "../search/hybrid.js"; import { type MemoryConfig, resolveContextBudget } from "../core/config.js"; import type { AssembledContext } from "../search/types.js"; import type { QueryMode } from "../search/intent.js"; import type { MetadataStore } from "../storage/metadata-store.js"; import type { FTSStore } from "../storage/fts-store.js"; import type { StoredChunk } from "../storage/types.js"; import { resolveSeeds } from "../search/seed.js"; import type { SeedResult } from "../search/seed.js"; import type { BroadSelectionDiagnostics } from "../search/hybrid.js"; import { buildStackTree } from "../search/tree-builder.js"; import { assembleContext, assembleFlow… Evidence: `src/hooks/prompt-context.ts`
- **Context** (source_file): import { countTokens } from "../search/context-assembler.js"; import { type MemoryClass, type MemoryRoute, type MemorySearchResult, resolveMemoryClass, resolveMemorySummary, } from "./types.js"; ⋮---- export interface AssembledMemoryContext { text: string; tokenCount: number; memories: MemorySearchResult ; dropped: Array ; route: MemoryRoute; classTokens: Record ; classCounts: Record ; budget: { total: number; used: number; remaining: number; codeFloorRatio: number; classBudgets: Record ; }; } ⋮---- export interface MemoryAssemblyOptions { classBudgets?: Partial ; codeFloorRatio?: number; maxMemories?: number; } ⋮---- export function assembleMemoryContext memories: MemorySearchResult , toke… Evidence: `src/memory/context.ts`
- **Indexer** (source_file): import { mkdirSync, readdirSync, readFileSync, statSync, writeFileSync, realpathSync } from "fs"; import { resolve, extname, basename, sep } from "path"; import { createHash } from "crypto"; import { homedir } from "os"; import { getLogger } from "../core/logger.js"; import { parseMemoryFile } from "./parser.js"; import type { Memory, MemoryClass, MemoryCompactionOptions, MemoryCompactionResult, MemoryScope, MemorySourceKind, MemoryType, } from "./types.js"; import type { MemoryStore } from "../storage/memory-store.js"; ⋮---- export function discoverClaudeMemoryDir projectRoot: string : string null ⋮---- function memoryId filePath: string : string ⋮---- function scanMemoryFiles dir: string… Evidence: `src/memory/indexer.ts`
- **Capability Evidence** (source_file): import type { MetadataStore } from "../storage/metadata-store.js"; import type { StoredChunk } from "../storage/types.js"; import type { QueryMode } from "./intent.js"; import type { SearchResult } from "./types.js"; import { isTestFile, textMatchesQueryTerm, tokenizeQueryTerms, STOP WORDS, GENERIC BROAD TERMS, GENERIC QUERY ACTION TERMS } from "./utils.js"; import { normalizeTargetText } from "./targets.js"; ⋮---- export type CapabilitySelectionSource = "direct match" "wiki capability" "import neighbor" "call neighbor" "mandatory flow step"; ⋮---- export type CapabilitySelectionReason = "direct match" "wiki related file" "import neighbor" "call neighbor" "mandatory flow step"; ⋮---- export… Evidence: `src/search/capability-evidence.ts`
- **Evidence Compressor** (source_file): import type { ContextOriginalRef, SearchResult } from "./types.js"; ⋮---- export type EvidenceCompressionMode = "off" "auto" "always"; ⋮---- export interface EvidenceCompressionOptions { query?: string; minChunkTokens?: number; targetRatio?: number; } ⋮---- export interface EvidenceCompressionResult { text: string; strategy: "code" "search result" "config or data" "text"; originalRef: ContextOriginalRef; } ⋮---- export function compressEvidenceChunk chunk: SearchResult, options: EvidenceCompressionOptions : EvidenceCompressionResult ⋮---- function inferStrategy chunk: SearchResult : EvidenceCompressionResult "strategy" ⋮---- function selectEvidenceLines chunk: SearchResult, query: string un… Evidence: `src/search/evidence-compressor.ts`
- **Hybrid** (source_file): import { type MemoryConfig, resolveContextBudget } from "../core/config.js"; import type { EmbeddingProvider } from "../indexer/types.js"; import type { VectorStore } from "../storage/vector-store.js"; import type { FTSStore } from "../storage/fts-store.js"; import type { MetadataStore } from "../storage/metadata-store.js"; import { GENERIC BROAD TERMS, GENERIC QUERY ACTION TERMS, textMatchesQueryTerm, } from "./utils.js"; import { assembleContext, } from "./context-assembler.js"; import { getLogger } from "../core/logger.js"; import type { SearchResult, SearchOptions, AssembledContext } from "./types.js"; import type { ReadWriteLock } from "../core/rwlock.js"; import { resolveSeeds } from… Evidence: `src/search/hybrid.ts`
- **Intent** (source_file): export interface QueryIntent { isCodeQuery: boolean; needsNavigation: boolean; prefersBroadContext?: boolean; queryMode: QueryMode; modeConfidence?: number; skipReason?: string; } ⋮---- export type QueryMode = "skip" "lookup" "trace" "bug" "architecture" "change"; ⋮---- // Thanks ⋮---- // Meta about Claude / AI / memory / reporecall ⋮---- // General chat / conversation meta ⋮---- // Short vague directives with no code-specific nouns — conversational, // not worth searching the index for. ⋮---- export function classifyIntent query: string : QueryIntent Evidence: `src/search/intent.ts`
- **Pipeline Core** (source_file): import type { MemoryConfig } from "../core/config.js"; import type { EmbeddingProvider, EmbeddingVector } from "../indexer/types.js"; import type { VectorStore } from "../storage/vector-store.js"; import type { FTSStore } from "../storage/fts-store.js"; import type { MetadataStore } from "../storage/metadata-store.js"; import { reciprocalRankFusion } from "./ranker.js"; import { expandQueryTerms, } from "./utils.js"; import { getLogger } from "../core/logger.js"; import type { SearchResult, SearchOptions } from "./types.js"; import type { ReadWriteLock } from "../core/rwlock.js"; import { classifyIntent } from "./intent.js"; import type { StoredChunk } from "../storage/types.js"; import { c… Evidence: `src/search/pipeline-core.ts`
- **Auto Capture** (source_file): import { execFileSync } from "child process"; import { readFileSync } from "fs"; import { writeManagedMemoryFile, safeMemorySlug } from "../memory/files.js"; import type { MemoryIndexer } from "../memory/indexer.js"; import type { MemoryStore } from "../storage/memory-store.js"; import { resolveAllLinks } from "./links.js"; import { getLogger } from "../core/logger.js"; ⋮---- export interface AutoCaptureOptions { writableDir: string; projectRoot: string; } ⋮---- export class WikiAutoCapture ⋮---- constructor indexer: MemoryIndexer, store: MemoryStore, opts: AutoCaptureOptions ⋮---- async captureFlowResult query: string, flowText: string, seedName: string, relatedFiles: string , relatedSymbo… Evidence: `src/wiki/auto-capture.ts`
- **Business** (source_file): import { basename } from "path"; import type { CommunityRecord, GodNodeRecord, SurpriseRecord } from "../storage/metadata-store.js"; import { slugify } from "../core/strings.js"; ⋮---- export interface BusinessCommunityMember { name: string; filePath: string; kind: string; startLine?: number; endLine?: number; } ⋮---- export interface BusinessPageDraft { slug: string; title: string; description: string; summary: string; content: string; relatedFiles: string ; relatedSymbols: string ; businessTerms: string ; userActions: string ; dataConcepts: string ; externalSystems: string ; links: string ; confidence: number; } ⋮---- interface BusinessCommunitySource { community: CommunityRecord; members… Evidence: `src/wiki/business.ts`
- **Context** (source_file): import type { MemorySearchResult } from "../memory/types.js"; import { resolveMemorySummary } from "../memory/types.js"; import { countTokens } from "../search/context-assembler.js"; ⋮---- export interface AssembledWikiContext { text: string; tokenCount: number; pageCount: number; pageNames: string ; pages?: MemorySearchResult ; } ⋮---- export function assembleWikiContext results: MemorySearchResult , tokenBudget: number, maxPages = 3 : AssembledWikiContext null ⋮---- // For top result, include overview section if available ⋮---- // Extract first section Overview or first paragraph Evidence: `src/wiki/context.ts`
- **Generator** (source_file): import { execFileSync } from "child process"; import { createHash } from "crypto"; import { readFileSync, rmSync } from "fs"; import { basename } from "path"; import type { MetadataStore } from "../storage/metadata-store.js"; import type { MemoryStore } from "../storage/memory-store.js"; import type { MemoryIndexer } from "../memory/indexer.js"; import { writeManagedMemoryFile } from "../memory/files.js"; import { resolveAllLinks } from "./links.js"; import { getLogger } from "../core/logger.js"; import { buildBusinessPages } from "./business.js"; import { slugify } from "../core/strings.js"; ⋮---- export interface WikiGeneratorOptions { writableDir: string; projectRoot: string; maxCommunit… Evidence: `src/wiki/generator.ts`
- **Staleness** (source_file): import { execFileSync } from "child process"; import type { WikiStalenessResult } from "./types.js"; ⋮---- export function checkPageStaleness name: string, sourceCommit: string, relatedFiles: string , projectRoot: string : WikiStalenessResult Evidence: `src/wiki/staleness.ts`
- **Trust Contract + Token Savings Benchmark Placeholder** (documentation): Trust Contract + Token Savings Benchmark Placeholder Evidence: `scripts/benchmarks/trust-and-tokens.md`
- **Devcontainer** (structured_config): { "name": "Reporecall", "image": "mcr.microsoft.com/devcontainers/typescript-node:1-20-bookworm", "workspaceFolder": "/workspaces/${localWorkspaceFolderBasename}", "remoteUser": "node", "updateRemoteUserUID": true, "init": true, "postCreateCommand": "npm ci", "postStartCommand": "bash -lc 'git rev-parse --git-dir /dev/null 2 &1 && git config --global --add safe.directory \"${containerWorkspaceFolder}\" true'", "forwardPorts": 37222 , "portsAttributes": { "37222": { "label": "Reporecall daemon", "onAutoForward": "notify" } }, "customizations": { "vscode": { "extensions": "GitHub.vscode-github-actions", "vitest.explorer", "esbenp.prettier-vscode" , "settings": { "files.eol": "\n", "typescript… Evidence: `.devcontainer/devcontainer.json`
- **.Release Please Config** (structured_config): { "$schema": "https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json", "release-type": "node", "include-v-in-tag": true, "include-component-in-tag": false, "bump-minor-pre-major": true, "bump-patch-for-minor-pre-major": false, "pull-request-title-pattern": "chore: release ${version}", "packages": { ".": { "package-name": "@proofofwork-agency/reporecall", "release-type": "node" } }, "changelog-sections": { "type": "feat", "section": "Features" }, { "type": "fix", "section": "Bug Fixes" }, { "type": "perf", "section": "Performance Improvements" }, { "type": "deps", "section": "Dependencies" }, { "type": "revert", "section": "Reverts" }, { "type": "refactor", "sec… Evidence: `.release-please-config.json`
- **.Release Please Manifest** (structured_config): { ".": "0.8.1" } Evidence: `.release-please-manifest.json`
- **Annotations** (structured_config): { "corpus": "reporecall", "version": "0.4.1", "annotatedAt": "2026-03-21", "scale": { "0": "not relevant", "1": "marginally relevant", "2": "relevant", "3": "highly relevant" }, "queries": { "id": "what-does-sanitizequery-do", "query": "what does sanitizeQuery do?", "category": "exact lookup", "expectedRoute": "lookup", "relevance": { "sanitizeQuery": 3, "handlePromptContext": 1, "handlePromptContextDetailed": 1 } }, { "id": "find-the-hybridsearch-class", "query": "find the HybridSearch class", "category": "exact lookup", "expectedRoute": "lookup", "relevance": { "HybridSearch": 3, "search": 1, "searchWithContext": 1 } }, { "id": "show-me-the-metadatastore-constructor", "query": "show me th… Evidence: `benchmark/annotations.json`
- **External Queries** (structured_config): { "version": "0.3.0", "generatedAt": "2026-03-20T00:00:00.000Z", "suites": { "id": "reporecall-broad-workflows", "corpus": "reporecall", "projectRoot": ".", "queries": { "id": "search-pipeline-files", "query": "which files implement the full search pipeline", "expectedRoute": "architecture", "relevance": { "src/search/hybrid.ts": 3, "src/search/reranker.ts": 3, "src/search/ranker.ts": 3, "src/search/targets.ts": 2, "src/search/seed.ts": 2, "src/search/intent.ts": 2, "src/search/context-assembler.ts": 1, "src/search/tree-builder.ts": 1 } }, { "id": "hook-flow-instrumentation", "query": "add logging to every step in the hook request flow", "expectedRoute": "change", "relevance": { "src/hooks/… Evidence: `benchmark/external-queries.json`
- **Production Queries** (structured_config): { "version": "0.4.1-production-gate", "generatedAt": "2026-03-24T00:00:00.000Z", "suites": { "id": "duto-production", "projectRoot": "../duto", "queries": { "id": "bug-node-compatibility-random", "query": "some of the the nodes can connect to nodes they are not supposed to connect to how is this possible?", "expectedMode": "bug", "relevance": { "src/lib/flow/nodeConnectionSchema.ts": 3, "src/pages/FlowEditor.tsx": 3, "src/components/flow/QuickConnectMenu.tsx": 1 }, "mustInclude": "src/lib/flow/nodeConnectionSchema.ts" , "mustNotInclude": "documentation/NODES.md", "src/components/flow/nodes/nodeRegistry.tsx" }, { "id": "arch-auth-flow", "query": "how does the auth flow work?", "expectedMode"… Evidence: `benchmark/production-queries.json`
- **Project Context Queries** (structured_config): { "version": "0.4.1", "generatedAt": "2026-03-23T00:00:00.000Z", "projectRoot": "../duto", "queries": { "id": "r0-generate-image-implemented", "query": "where is generate-image implemented", "expectedRoute": "R0", "category": "generation", "relevance": { "supabase/functions/generate-image/index.ts": 3 }, "mustInclude": "supabase/functions/generate-image/index.ts" , "mustNotInclude": " tests /", "e2e/" }, { "id": "r0-upload-media-implemented", "query": "where is upload-media implemented", "expectedRoute": "R0", "category": "media", "relevance": { "supabase/functions/upload-media/index.ts": 3 }, "mustInclude": "supabase/functions/upload-media/index.ts" , "mustNotInclude": " tests /", "e2e/" }… Evidence: `benchmark/project-context-queries.json`
- **Queries** (structured_config): { "query": "where is validateToken?", "expectedRoute": "R0", "category": "exact lookup", "description": "Direct symbol lookup for a specific function" }, { "query": "what does sanitizeQuery do?", "expectedRoute": "R0", "category": "exact lookup", "description": "Direct function explanation" }, { "query": "find the HybridSearch class", "expectedRoute": "R0", "category": "exact lookup", "description": "Class lookup by name" }, { "query": "show me the MetadataStore constructor", "expectedRoute": "R0", "category": "exact lookup", "description": "Constructor lookup on a specific class" }, { "query": "where is loadConfig defined?", "expectedRoute": "R0", "category": "exact lookup", "description":… Evidence: `benchmark/queries.json`
- **Glama** (structured_config): { "$schema": "https://glama.ai/mcp/schemas/server.json", "maintainers": "proofofwork" } Evidence: `glama.json`
- **Tsconfig** (structured_config): { "compilerOptions": { "target": "ES2022", "module": "ESNext", "moduleResolution": "bundler", "strict": true, "esModuleInterop": true, "skipLibCheck": true, "forceConsistentCasingInFileNames": true, "outDir": "dist", "rootDir": ".", "declaration": true, "declarationMap": true, "sourceMap": true, "resolveJsonModule": true, "isolatedModules": true, "noUnusedLocals": true, "noUnusedParameters": true, "noFallthroughCasesInSwitch": true, "noUncheckedIndexedAccess": true }, "include": "src/ / ", "bin/ / " , "exclude": "node modules", "dist", "test" } Evidence: `tsconfig.json`
- **Lockfiles: npm is canonical package-lock.json ; ignore pnpm** (source_file): node modules/ dist/ .memory/ .engram/ reports .claude/ .demo/ CLAUDE.md .tsbuildinfo .DS Store skills-lock.json .agents/ .contextrelay/ open-multi-agent-main claude-code-source-main .tmp/ test/.test-data-server- / test/.test-data-server- /graphify-3/ Evidence: `.gitignore`
- **.Mcp.Json** (source_file): { "mcpServers": { "reporecall": { "command": "node", "args": "./dist/memory.js", "mcp", "--project", "${PROJECT ROOT}" } } } Evidence: `.mcp.json.example`
- The remaining 10 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`, `scripts/benchmarks/README.md`, `docs/architecture-overview.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`, `scripts/benchmarks/README.md`, `docs/architecture-overview.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 & the Trust Contract**: importance `high`
  - source_paths: README.md, src/core/staleness.ts, docs/architecture-overview.md, docs/design/wp5-tool-collapse.md
- **MCP Surface, Intent Routing & Hybrid Retrieval**: importance `high`
  - source_paths: src/daemon/mcp-server.ts, src/search/intent.ts, src/search/hybrid.ts, src/search/pipeline-core.ts, src/search/capability-evidence.ts
- **Wiki, Memory, Business Context & Lens**: importance `high`
  - source_paths: src/wiki/generator.ts, src/wiki/staleness.ts, src/wiki/auto-capture.ts, src/wiki/business.ts, src/wiki/context.ts
- **Operations, Configuration & Common Workflows**: importance `medium`
  - source_paths: src/cli/init.ts, src/cli/index-cmd.ts, src/cli/serve.ts, src/cli/mcp.ts, src/cli/doctor.ts

## Repo Inspection Evidence

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `46058a204e9a571bd9617ef9bb4922fd79f9ee14`
- inspected_files: `README.md`, `package.json`, `docs/architecture-overview.md`, `docs/business-context-schema.md`, `docs/competitive-positioning-2026.md`, `docs/design/wp5-tool-collapse.md`, `docs/release-verification.md`, `docs/reporecall-context-layer-competitor-comparison.md`, `docs/reporecall-v0.7-comparison.md`, `docs/retrieval-context-pipeline.md`, `examples/demo.ts`, `src/analysis/call-graph.ts`, `src/analysis/community-detection.ts`, `src/analysis/conventions.ts`, `src/analysis/graph-builder.ts`, `src/analysis/imports.ts`, `src/analysis/resolve.ts`, `src/analysis/semantic-features.ts`, `src/analysis/topology-analysis.ts`, `src/business/product-areas.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: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: v0.5.0 — Topology-Aware Search & Architecture Decomposition
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v0.5.0 — Topology-Aware Search & Architecture Decomposition. Context: Observed when using node, python
- Why it matters: Upgrade or migration may change expected behavior: v0.5.0 — Topology-Aware Search & Architecture Decomposition
- Evidence: failure_mode_cluster:github_release | https://github.com/proofofwork-agency/reporecall/releases/tag/v0.5.0
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 2: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: v0.6.2 — Lens Architecture Dashboard
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v0.6.2 — Lens Architecture Dashboard. Context: Observed when using node, python, windows, macos
- Why it matters: Upgrade or migration may change expected behavior: v0.6.2 — Lens Architecture Dashboard
- Evidence: failure_mode_cluster:github_release | https://github.com/proofofwork-agency/reporecall/releases/tag/v0.6.2
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 3: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: v0.7.1 — Capability Evidence + Business Context Export + Self-Eval Patches
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v0.7.1 — Capability Evidence + Business Context Export + Self-Eval Patches. Context: Observed when using node
- Why it matters: Upgrade or migration may change expected behavior: v0.7.1 — Capability Evidence + Business Context Export + Self-Eval Patches
- Evidence: failure_mode_cluster:github_release | https://github.com/proofofwork-agency/reporecall/releases/tag/v0.7.1
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 4: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: v0.8.0 — Trust Contract Remediation
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v0.8.0 — Trust Contract Remediation. Context: Observed during installation or first-run setup.
- Why it matters: Upgrade or migration may change expected behavior: v0.8.0 — Trust Contract Remediation
- Evidence: failure_mode_cluster:github_release | https://github.com/proofofwork-agency/reporecall/releases/tag/v0.8.0
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 5: Configuration risk requires verification

- Trigger: Developers should check this configuration risk before relying on the project: v0.6.0: Wiki Layer, Topology Tools & Memory Precision
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v0.6.0: Wiki Layer, Topology Tools & Memory Precision. Context: Source discussion did not expose a precise runtime context.
- Why it matters: Upgrade or migration may change expected behavior: v0.6.0: Wiki Layer, Topology Tools & Memory Precision
- Evidence: failure_mode_cluster:github_release | https://github.com/proofofwork-agency/reporecall/releases/tag/v0.6.0
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 6: 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/proofofwork-agency/reporecall
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

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

### Constraint 8: 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/proofofwork-agency/reporecall
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.