# rac-core - Doramagic AI Context Pack

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

## 充分原则

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

## 给宿主 AI 的使用方式

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

## Claim 消费规则

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

## 它最适合谁

- **正在使用 Claude/Codex/Cursor/Gemini 等宿主 AI 的开发者**：README 或插件配置提到多个宿主 AI。 证据：`README.md` Claim：`clm_0003` supported 0.86
- **希望把专业流程带进宿主 AI 的用户**：仓库包含 Skill 文档。 证据：`.claude/skills/rac-artifacts/SKILL.md`, `.claude/skills/rac-capture/SKILL.md`, `.claude/skills/rac-import/SKILL.md`, `.claude/skills/rac-ingest/SKILL.md` 等 Claim：`clm_0004` supported 0.86

## 它能做什么

- **AI Skill / Agent 指令资产库**（可做安装前预览）：项目包含可被宿主 AI 读取的 Skill 或 Agent 指令文件，可用于把专业流程带入 Claude、Codex、Cursor 等宿主。 证据：`.claude/skills/rac-artifacts/SKILL.md`, `.claude/skills/rac-capture/SKILL.md`, `.claude/skills/rac-import/SKILL.md`, `.claude/skills/rac-ingest/SKILL.md` 等 Claim：`clm_0001` supported 0.86
- **命令行启动或安装流程**（需要安装后验证）：项目文档中存在可执行命令，真实使用需要在本地或宿主环境中运行这些命令。 证据：`README.md`, `docs/quickstart.md` Claim：`clm_0002` supported 0.86

## 怎么开始

- `pip install rac-core` 证据：`README.md` Claim：`clm_0005` supported 0.86
- `claude mcp add lore -- rac mcp` 证据：`README.md` Claim：`clm_0006` supported 0.86
- `pip install -e .[dev]` 证据：`README.md` Claim：`clm_0007` supported 0.86
- `uv tool install rac-core` 证据：`docs/quickstart.md` Claim：`clm_0008` supported 0.86

## 继续前判断卡

- **当前建议**：仅建议沙盒试装
- **为什么**：项目存在安装命令、宿主配置或本地写入线索，不建议直接进入主力环境，应先在隔离环境试装。

### 30 秒判断

- **现在怎么做**：仅建议沙盒试装
- **最小安全下一步**：先跑 Prompt Preview；若仍要安装，只在隔离环境试装
- **先别相信**：真实输出质量不能在安装前相信。
- **继续会触碰**：命令执行、宿主 AI 配置、本地环境或项目文件

### 现在可以相信

- **适合人群线索：正在使用 Claude/Codex/Cursor/Gemini 等宿主 AI 的开发者**（supported）：有 supported claim 或项目证据支撑，但仍不等于真实安装效果。 证据：`README.md` Claim：`clm_0003` supported 0.86
- **适合人群线索：希望把专业流程带进宿主 AI 的用户**（supported）：有 supported claim 或项目证据支撑，但仍不等于真实安装效果。 证据：`.claude/skills/rac-artifacts/SKILL.md`, `.claude/skills/rac-capture/SKILL.md`, `.claude/skills/rac-import/SKILL.md`, `.claude/skills/rac-ingest/SKILL.md` 等 Claim：`clm_0004` supported 0.86
- **能力存在：AI Skill / Agent 指令资产库**（supported）：可以相信项目包含这类能力线索；是否适合你的具体任务仍要试用或安装后验证。 证据：`.claude/skills/rac-artifacts/SKILL.md`, `.claude/skills/rac-capture/SKILL.md`, `.claude/skills/rac-import/SKILL.md`, `.claude/skills/rac-ingest/SKILL.md` 等 Claim：`clm_0001` supported 0.86
- **能力存在：命令行启动或安装流程**（supported）：可以相信项目包含这类能力线索；是否适合你的具体任务仍要试用或安装后验证。 证据：`README.md`, `docs/quickstart.md` Claim：`clm_0002` supported 0.86
- **存在 Quick Start / 安装命令线索**（supported）：可以相信项目文档出现过启动或安装入口；不要因此直接在主力环境运行。 证据：`README.md` Claim：`clm_0005` supported 0.86

### 现在还不能相信

- **真实输出质量不能在安装前相信。**（unverified）：Prompt Preview 只能展示引导方式，不能证明真实项目中的结果质量。
- **宿主 AI 版本兼容性不能在安装前相信。**（unverified）：Claude、Cursor、Codex、Gemini 等宿主加载规则和版本差异必须在真实环境验证。
- **不会污染现有宿主 AI 行为，不能直接相信。**（inferred）：Skill、plugin、AGENTS/CLAUDE/GEMINI 指令可能改变宿主 AI 的默认行为。 证据：`.claude/skills/rac-artifacts/SKILL.md`, `.claude/skills/rac-capture/SKILL.md`, `.claude/skills/rac-import/SKILL.md`, `.claude/skills/rac-ingest/SKILL.md` 等
- **可安全回滚不能默认相信。**（unverified）：除非项目明确提供卸载和恢复说明，否则必须先在隔离环境验证。
- **真实安装后是否与用户当前宿主 AI 版本兼容？**（unverified）：兼容性只能通过实际宿主环境验证。
- **项目输出质量是否满足用户具体任务？**（unverified）：安装前预览只能展示流程和边界，不能替代真实评测。
- **安装命令是否需要网络、权限或全局写入？**（unverified）：这影响企业环境和个人环境的安装风险。 证据：`README.md`

### 继续会触碰什么

- **命令执行**：包管理器、网络下载、本地插件目录、项目配置或用户主目录。 原因：运行第一条命令就可能产生环境改动；必须先判断是否值得跑。 证据：`README.md`, `docs/quickstart.md`
- **宿主 AI 配置**：Claude/Codex/Cursor/Gemini/OpenCode 等宿主的 plugin、Skill 或规则加载配置。 原因：宿主配置会改变 AI 后续工作方式，可能和用户已有规则冲突。 证据：`.claude/skills/rac-artifacts/SKILL.md`, `.claude/skills/rac-capture/SKILL.md`, `.claude/skills/rac-import/SKILL.md`, `.claude/skills/rac-ingest/SKILL.md` 等
- **本地环境或项目文件**：安装结果、插件缓存、项目配置或本地依赖目录。 原因：安装前无法证明写入范围和回滚方式，需要隔离验证。 证据：`README.md`, `docs/quickstart.md`
- **宿主 AI 上下文**：AI Context Pack、Prompt Preview、Skill 路由、风险规则和项目事实。 原因：导入上下文会影响宿主 AI 后续判断，必须避免把未验证项包装成事实。

### 最小安全下一步

- **先跑 Prompt Preview**：用安装前交互式试用判断工作方式是否匹配，不需要授权或改环境。（适用：任何项目都适用，尤其是输出质量未知时。）
- **只在隔离目录或测试账号试装**：避免安装命令污染主力宿主 AI、真实项目或用户主目录。（适用：存在命令执行、插件配置或本地写入线索时。）
- **先备份宿主 AI 配置**：Skill、plugin、规则文件可能改变 Claude/Cursor/Codex 的默认行为。（适用：存在插件 manifest、Skill 或宿主规则入口时。）
- **安装后只验证一个最小任务**：先验证加载、兼容、输出质量和回滚，再决定是否深用。（适用：准备从试用进入真实工作流时。）

### 退出方式

- **保留安装前状态**：记录原始宿主配置和项目状态，后续才能判断是否可恢复。
- **准备移除宿主 plugin / Skill / 规则入口**：如果试装后行为异常，可以把宿主 AI 恢复到试装前状态。
- **记录安装命令和写入路径**：没有明确卸载说明时，至少要知道哪些目录或配置需要手动清理。
- **如果没有回滚路径，不进入主力环境**：不可回滚是继续前阻断项，不应靠信任或运气继续。

## 哪些只能预览

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

## 哪些必须安装后验证

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

## 边界与风险判断卡

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

## 开工前工作上下文

### 加载顺序

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

### 任务路由

- **AI Skill / Agent 指令资产库**：先基于 role_skill_index / evidence_index 帮用户挑选可用角色、Skill 或工作流。 边界：可做安装前 Prompt 体验。 证据：`.claude/skills/rac-artifacts/SKILL.md`, `.claude/skills/rac-capture/SKILL.md`, `.claude/skills/rac-import/SKILL.md`, `.claude/skills/rac-ingest/SKILL.md` 等 Claim：`clm_0001` supported 0.86
- **命令行启动或安装流程**：先说明这是安装后验证能力，再给出安装前检查清单。 边界：必须真实安装或运行后验证。 证据：`README.md`, `docs/quickstart.md` Claim：`clm_0002` supported 0.86

### 上下文规模

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

### 证据不足时的处理

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

## Prompt Recipes

### 适配判断

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

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

### 安装前体验

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

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

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

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

```

### 角色 / Skill 选择

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

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

### 风险预检

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

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

### 宿主 AI 开工指令

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

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

## 角色 / Skill 索引

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

- **rac-artifacts**（skill）：Author and maintain RAC requirements-as-code Markdown artifacts — requirements, decisions, roadmaps, prompts, designs — using the rac CLI. Use when asked to create, read, validate, update, or link Lore RAC artifacts in a project's rac/ directory. 激活提示：当用户任务与“rac-artifacts”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`.claude/skills/rac-artifacts/SKILL.md`
- **rac-capture**（skill）：Capture a NEW decision or requirement from a conversation an interview into ONE valid RAC requirements-as-code artifact — you interview and propose, the human ratifies, rac validate closes, and promotion into the trusted corpus is by pull request reviewed by someone other than the author. Use when a user wants to record a fresh decision or requirement into Lore a project's rac/ directory by talking it through rather… 激活提示：当用户任务与“rac-capture”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`.claude/skills/rac-capture/SKILL.md`
- **rac-import**（skill）：Reformat ONE existing document a decision, requirement, design, roadmap, or prompt into ONE valid RAC requirements-as-code artifact, with a mandatory human-review step before any file is written and rac validate as the deterministic close. Use when a user wants to add or import a single existing decision or document into Lore a project's rac/ directory . Single-document only — for multi-format or bulk conversion use… 激活提示：当用户任务与“rac-import”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`.claude/skills/rac-import/SKILL.md`
- **rac-ingest**（skill）：Convert legacy documents DOCX, PDF, HTML, PPTX, XLSX, Markdown into valid, linked RAC requirements-as-code artifacts using the rac CLI. Use when asked to add, import, convert, or migrate existing documents into Lore a project's rac/ directory . 激活提示：当用户任务与“rac-ingest”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`.claude/skills/rac-ingest/SKILL.md`
- **rac-review**（skill）：Review and triage a RAC requirements-as-code corpus using the rac CLI — work prioritised findings worst-first until validation and relationship checks pass. Use when asked to review, triage, or fix findings across a project's Lore corpus the rac/ directory . 激活提示：当用户任务与“rac-review”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`.claude/skills/rac-review/SKILL.md`
- **rac-artifacts**（skill）：Author and maintain RAC requirements-as-code Markdown artifacts — requirements, decisions, roadmaps, prompts, designs — using the rac CLI. Use when asked to create, read, validate, update, or link Lore RAC artifacts in a project's rac/ directory. 激活提示：当用户任务与“rac-artifacts”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`src/rac/skills/rac-artifacts/SKILL.md`
- **rac-capture**（skill）：Capture a NEW decision or requirement from a conversation an interview into ONE valid RAC requirements-as-code artifact — you interview and propose, the human ratifies, rac validate closes, and promotion into the trusted corpus is by pull request reviewed by someone other than the author. Use when a user wants to record a fresh decision or requirement into Lore a project's rac/ directory by talking it through rather… 激活提示：当用户任务与“rac-capture”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`src/rac/skills/rac-capture/SKILL.md`
- **rac-import**（skill）：Reformat ONE existing document a decision, requirement, design, roadmap, or prompt into ONE valid RAC requirements-as-code artifact, with a mandatory human-review step before any file is written and rac validate as the deterministic close. Use when a user wants to add or import a single existing decision or document into Lore a project's rac/ directory . Single-document only — for multi-format or bulk conversion use… 激活提示：当用户任务与“rac-import”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`src/rac/skills/rac-import/SKILL.md`
- **rac-ingest**（skill）：Convert legacy documents DOCX, PDF, HTML, PPTX, XLSX, Markdown into valid, linked RAC requirements-as-code artifacts using the rac CLI. Use when asked to add, import, convert, or migrate existing documents into Lore a project's rac/ directory . 激活提示：当用户任务与“rac-ingest”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`src/rac/skills/rac-ingest/SKILL.md`
- **rac-review**（skill）：Review and triage a RAC requirements-as-code corpus using the rac CLI — work prioritised findings worst-first until validation and relationship checks pass. Use when asked to review, triage, or fix findings across a project's Lore corpus the rac/ directory . 激活提示：当用户任务与“rac-review”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`src/rac/skills/rac-review/SKILL.md`

## 证据索引

- 共索引 80 条证据。

- **Lore**（documentation）：Quickstart · How it compares · How it works · Docs · CLI · Changelog 证据：`README.md`
- **RAC with Amp**（documentation）：This shows how to connect Amp https://ampcode.com — Sourcegraph's coding agent — to RAC, so Amp respects the decisions your team has already recorded. A stranger can reproduce the setup from this file alone. 证据：`examples/amp/README.md`
- **RAC with Claude Code**（documentation）：Claude Code https://docs.anthropic.com/en/docs/claude-code is RAC's most integrated client — it gets the two surfaces every client gets a generated context file + the lore MCP server , plus two Claude-Code-specific extras: a bundled authoring skill and the only platform seam that allows a real pre-edit veto . A stranger can reproduce this from the file alone. 证据：`examples/claude-code/README.md`
- **RAC with Codex**（documentation）：OpenAI Codex https://developers.openai.com/codex the Codex CLI consumes RAC on the same two surfaces it already supports natively — an AGENTS.md it reads for project instructions, and MCP servers it connects to — so there is no Codex-specific RAC code. A stranger can reproduce this from the file alone. 证据：`examples/codex/README.md`
- **RAC with GitHub Copilot**（documentation）：GitHub Copilot https://github.com/features/copilot in VS Code consumes RAC on two surfaces — a generated custom-instructions file Copilot reads, and the lore MCP server its agent mode connects to. A stranger can reproduce this from the file alone. 证据：`examples/copilot/README.md`
- **RAC with Cursor**（documentation）：Cursor https://cursor.com consumes RAC on two surfaces — a generated context file Cursor reads, and the lore MCP server it connects to. A stranger can reproduce this from the file alone. 证据：`examples/cursor/README.md`
- **Meridian user service — code task starting state**（documentation）：Meridian user service — code task starting state 证据：`examples/guide/task/README.md`
- **Obey-demo — the v0.23.0 grounding success anchor**（documentation）：Obey-demo — the v0.23.0 grounding success anchor 证据：`examples/obey-demo/README.md`
- **RAC with Omnigent**（documentation）：Omnigent https://omnigent.ai is an open-source meta-harness: a layer that sits above agent harnesses Claude Code, Codex, Cursor, Pi, and custom agents so you can swap or combine them without rewriting, govern them with policies, and collaborate on live sessions. Because an Omnigent custom agent is just a config.yaml , it consumes RAC on the same two surfaces every other client does — an AGENTS.md it reads for instructions, and MCP servers it connects to as tools — so there is no Omnigent-specific RAC code. 证据：`examples/omnigent/README.md`
- **requirements-as-code → rac-core**（documentation）：This package has been renamed. requirements-as-code is now published as rac-core https://pypi.org/project/rac-core/ . 证据：`packaging/requirements-as-code-shim/README.md`
- **Settled decisions RAC**（documentation）：These decisions are already accepted. Do not re-open or contradict them; ask the lore MCP tools get artifact , search artifacts for the full text before proposing a change that touches one. 证据：`AGENTS.md`
- **RAC — agent session context**（documentation）：This file is a router. Canonical agent guidance lives in rac/prompts/ , where the RAC corpus gates validate it. Do not add rules here — add them to the corpus artifact and they load through the imports below. 证据：`CLAUDE.md`
- **Package**（package_manifest）：{ "name": "rac-localview", "private": true, "version": "0.1.0", "type": "module", "scripts": { "dev": "vite", "build": "tsc -b && vite build && node scripts/prerender-landing.mjs", "preview": "vite preview", "contrast": "node scripts/contrast-report.mjs", "lantern": "node scripts/make-lantern.mjs", "corpus": "node scripts/make-corpus.mjs", "build:viewer": "tsc -b && vite build --config vite.config.viewer.ts && node scripts/build-viewer-artifact.mjs", "vendor:shell": "node scripts/vendor-portal-shell.mjs", "test": "vitest run" }, "dependencies": { "react": "^18.3.1", "react-dom": "^18.3.1" }, "devDependencies": { "@types/node": "^25.9.3", "@types/react": "^18.3.20", "@types/react-dom": "^18.… 证据：`rac-localview/package.json`
- **Contributing to RAC**（documentation）：Thanks for your interest in improving RAC. The project is early and evolving quickly — contributions, ideas, and experiments are welcome. 证据：`CONTRIBUTING.md`
- **RAC artifacts**（skill_instruction）：RAC models product artifacts as typed, deterministic Markdown files. Five types exist: requirement, decision, roadmap, prompt, design. Type is inferred from section headings, never declared. Frontmatter carries identity only and is machine-generated. 证据：`.claude/skills/rac-artifacts/SKILL.md`
- **RAC interview capture**（skill_instruction）：Turn a conversation into one valid RAC artifact. You interview the author and propose; the human ratifies; rac validate is the deterministic check; an independent reviewer promotes it by pull request. This skill never adds AI to the RAC core — it runs in the coding agent and uses the rac CLI. 证据：`.claude/skills/rac-capture/SKILL.md`
- **RAC single-document import**（skill_instruction）：Reshape one existing document into one valid RAC artifact. You propose; the human ratifies; rac validate is the deterministic check. This skill never adds AI to the RAC core — it runs in the coding agent and uses the rac CLI. 证据：`.claude/skills/rac-import/SKILL.md`
- **RAC legacy document conversion**（skill_instruction）：Turn an existing document into a valid, linked RAC artifact in five steps: convert, classify, restructure, mint identity, validate — then link it into the corpus. 证据：`.claude/skills/rac-ingest/SKILL.md`
- **RAC corpus review**（skill_instruction）：rac review validates every artifact, checks every relationship, and reports findings grouped by priority, worst first. This skill is the procedure for working that report down: blocking findings first, then advisory ones, re-validating after each fix. 证据：`.claude/skills/rac-review/SKILL.md`
- **RAC artifacts**（skill_instruction）：RAC models product artifacts as typed, deterministic Markdown files. Five types exist: requirement, decision, roadmap, prompt, design. Type is inferred from section headings, never declared. Frontmatter carries identity only and is machine-generated. 证据：`src/rac/skills/rac-artifacts/SKILL.md`
- **RAC interview capture**（skill_instruction）：Turn a conversation into one valid RAC artifact. You interview the author and propose; the human ratifies; rac validate is the deterministic check; an independent reviewer promotes it by pull request. This skill never adds AI to the RAC core — it runs in the coding agent and uses the rac CLI. 证据：`src/rac/skills/rac-capture/SKILL.md`
- **RAC single-document import**（skill_instruction）：Reshape one existing document into one valid RAC artifact. You propose; the human ratifies; rac validate is the deterministic check. This skill never adds AI to the RAC core — it runs in the coding agent and uses the rac CLI. 证据：`src/rac/skills/rac-import/SKILL.md`
- **RAC legacy document conversion**（skill_instruction）：Turn an existing document into a valid, linked RAC artifact in five steps: convert, classify, restructure, mint identity, validate — then link it into the corpus. 证据：`src/rac/skills/rac-ingest/SKILL.md`
- **RAC corpus review**（skill_instruction）：rac review validates every artifact, checks every relationship, and reports findings grouped by priority, worst first. This skill is the procedure for working that report down: blocking findings first, then advisory ones, re-validating after each fix. 证据：`src/rac/skills/rac-review/SKILL.md`
- **License**（source_file）：Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ 证据：`LICENSE`
- **Artifacts**（documentation）：RAC understands five artifact types, all written in plain Markdown: 证据：`docs/artifacts.md`
- **CLI Reference**（documentation）：RAC ships a single command, rac , with twenty-two subcommands. This page documents each one: its purpose, inputs, outputs, and exit codes. 证据：`docs/cli.md`
- **Ecosystem**（documentation）：Things that consume RAC artifacts or the RAC engine. Every entry is real and verified at the time of listing: it exists at the cited location and works against a released engine version. There are no planned or placeholder entries. 证据：`docs/ecosystem.md`
- **Examples**（documentation）：Short, realistic artifacts you can adapt. These show the shape of each type — for a blank starter with section guidance, use rac schema --template cli.md cli.md schema . 证据：`docs/examples.md`
- **Governance: the enforcement policy & rac gate**（documentation）：Governance: the enforcement policy & rac gate 证据：`docs/governance.md`
- **What it is**（documentation）：Your agent reintroduces an approach you rejected months ago. It rebuilds something you deliberately removed. The decision was written down — in an ADR nobody, human or agent, ever reopened. 证据：`docs/index.md`
- **RAC Guide — MCP Server**（documentation）：RAC Guide is an MCP server that serves your repository's requirements, decisions, designs, and roadmaps to coding agents as callable tools. It ships inside the rac-core package — no separate install. 证据：`docs/mcp.md`
- **OKF Profile**（documentation）：RAC stores product knowledge the same way Google Cloud's Open Knowledge Format OKF https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md does — a Git tree of Markdown files with YAML front matter. This page is RAC's informative profile of OKF v0.1 Draft : it defines how a RAC repository presents itself as a conformant OKF bundle. It is a derived, interoperability view; RAC Core and rac validate remain the source of truth, and adopting this profile loosens none of RAC's guarantees. The decision behind it is ADR-048 https://github.com/itsthelore/rac-core/blob/main/rac/decisions/adr-048-okf-carrier-profile.md , scoped by the rac-okf-carrier-profile requirement. 证据：`docs/okf-profile.md`
- **Quickstart**（documentation）：Try RAC in about five minutes. You will install the tool, scaffold your first artifact, and run the three commands you'll use most: validate , inspect , and improve . 证据：`docs/quickstart.md`
- **Relationships**（documentation）：Artifacts rarely stand alone — a requirement informs a decision, a roadmap pursues a requirement, a design references both. RAC lets you record those links in the Markdown itself and then validate that they resolve. 证据：`docs/relationships.md`
- **Repository Workflow**（documentation）：RAC runs against any directory of Markdown files, but it shines when a repository gives its product knowledge an intentional home. This page describes the convention RAC itself uses. 证据：`docs/repo-workflow.md`
- **Security posture**（documentation）：RAC is offline by design . The rac CLI and the editor extension model product knowledge from local Markdown files and emit local files and exit codes; they make no network calls and send no telemetry. This document records that posture as a control a security office can verify and sign — not a marketing claim — and points at the artifacts that prove it. 证据：`docs/security.md`
- **v0.22.x-housekeeping — Maintainer Runbook**（documentation）：v0.22.x-housekeeping — Maintainer Runbook 证据：`docs/v0.22-housekeeping-runbook.md`
- **Validation: overrides & SARIF**（documentation）：rac validate is RAC's write-time gate: it fails when any artifact carries an error-severity finding, and over a directory when the corpus is not a conformant OKF v0.1 bundle. Two features make that gate adoptable in CI on a real, pre-existing repository. 证据：`docs/validation.md`
- **Watchkeeper — product knowledge review on pull requests**（documentation）：Watchkeeper — product knowledge review on pull requests 证据：`docs/watchkeeper.md`
- **Agent Memory for Team Knowledge — Competitive Landscape & Lessons for Lore**（documentation）：Agent Memory for Team Knowledge — Competitive Landscape & Lessons for Lore 证据：`docs/research/agent-memory-landscape.md`
- **Team-Scale Knowledge Tooling — Competitive Landscape & Lessons for Lore**（documentation）：Team-Scale Knowledge Tooling — Competitive Landscape & Lessons for Lore 证据：`docs/research/team-scale-landscape.md`
- **Restructure decisiongrounding into rac-benchmarks**（documentation）：Restructure decisiongrounding into rac-benchmarks 证据：`rac/roadmaps/repo-topology/rac-benchmarks.md`
- **Consolidate CI Delivery into rac-ci**（documentation）：Consolidate CI Delivery into rac-ci 证据：`rac/roadmaps/repo-topology/rac-ci.md`
- **Rename lore-connectors to rac-connectors**（documentation）：Rename lore-connectors to rac-connectors 证据：`rac/roadmaps/repo-topology/rac-connectors.md`
- **Rename lore-vscode into rac-editors**（documentation）：Rename lore-vscode into rac-editors 证据：`rac/roadmaps/repo-topology/rac-editors.md`
- **Consolidate Language SDKs into rac-sdk**（documentation）：Consolidate Language SDKs into rac-sdk 证据：`rac/roadmaps/repo-topology/rac-sdk.md`
- **Testing & Contributing**（documentation）：This page is for contributors working on RAC itself: how to set up a local environment, run the test suite, and verify a change before opening a pull request. 证据：`docs/testing.md`
- **Demoapp**（source_file）：import { useState } from 'react'; import { CheckItem, CommandPalette, KeyboardHint, Panel, Prompt, TerminalFrame, } from '../components'; import type { CommandPaletteItem } from '../components'; import lanternUrl from '../../design/lantern.png'; ⋮---- interface SectionProps { name: string; note?: string; children: React.ReactNode; } function Section 证据：`rac-localview/src/demo/DemoApp.tsx`
- **Landingapp**（source_file）：import { useEffect, useRef, useState } from 'react'; import { CheckItem, CommandPalette, Panel, Prompt, TerminalFrame, } from '../components'; import type { CommandPaletteItem } from '../components'; import lamplighterUrl from '../../design/lamplighter.png'; import demoUrl from './assets/demo.svg'; import { CopyCommand } from './CopyCommand'; 证据：`rac-localview/src/landing/LandingApp.tsx`
- **Types**（source_file）：export interface CorpusMeta { name: string; rac version?: string; artifact count?: number; sample?: boolean; } export interface Artifact { id: string; aliases: string ; type: string; status: string; title: string; path: string; body html: string; } export interface Relationship { from: string; to: string; type: string; } export interface LoreExport { schema version: string; corpus: CorpusMeta; artifacts: Artifact ; relationships: Relationship ; } 证据：`rac-localview/src/viewer/types.ts`
- **Statusline**（source_file）：HINTS: dict str, tuple tuple str, str , ... = { def key chips pairs: tuple tuple str, str , ... - Text ⋮---- text = Text ⋮---- class StatusLine Horizontal ⋮---- """Key chips left, health chip and link count right.""" def init self - None def compose self - ComposeResult def show hints self, region: str - None ⋮---- pairs = HINTS.get region, HINTS "home" ⋮---- def show summary self, summary: RepositorySummaryState - None 证据：`src/rac/explorer/widgets/statusline.py`
- **The read-access audit log is config-driven ADR-084 , not a flag: enabled**（source_file）：SERVER NAME = "lore" DESC GET ARTIFACT = DESC SEARCH ARTIFACTS = DESC GET RELATED = DESC FIND DECISIONS = DESC GET SUMMARY = def read content path: str - str def resolve root: str, artifact id: str - ResolutionResult ⋮---- entries = build repository index root, recursive=True .artifacts ⋮---- def get artifact root: str, artifact id: str, budget: int - str ⋮---- result = resolve root, artifact id ⋮---- content = read content result.artifact.path ⋮---- payload = { ⋮---- def search artifacts root: str, query: str, artifact type: str None, budget: int - str ⋮---- result = search index entries, query, artifact type=artifact type ⋮---- def find decisions root: str, topic: str, budget: int - str ⋮… 证据：`src/rac/mcp/server.py`
- **Agent Rules**（source_file）：DECISION TYPE = "decision" LIVE STATUS = "accepted" BEGIN PREFIX = " " END MARKER = " " GENERATED HEADER = ⋮---- @dataclass frozen=True class AgentRulesTarget ⋮---- client: str path: str def to dict self - dict TARGETS: tuple AgentRulesTarget, ... = TARGET BY CLIENT = {t.client: t for t in TARGETS} def targets for clients: list str None - list AgentRulesTarget ⋮---- wanted = set clients ⋮---- def unknown clients clients: list str None - list str ⋮---- @dataclass frozen=True class AgentRulesEntry ⋮---- identifier: str title: str category: str None = None ⋮---- @dataclass class AgentRulesProjection ⋮---- entries: list AgentRulesEntry = field default factory=list digest: str = "" ⋮---- def art… 证据：`src/rac/services/agent_rules.py`
- **Export**（source_file）：EDGE TYPE = "relates-to" STATUS ABSENT = "unknown" ⋮---- @dataclass class ExportArtifact ⋮---- id: str aliases: list str type: str status: str title: str path: str body html: str tags: list str = field default factory=list def to dict self - dict ⋮---- @dataclass class ExportRelationship ⋮---- from : str to: str type: str = EDGE TYPE ⋮---- @dataclass class CorpusExport ⋮---- corpus name: str rac version: str artifacts: list ExportArtifact = field default factory=list relationships: list ExportRelationship = field default factory=list ⋮---- @property def artifact count self - int ⋮---- @dataclass class ExportDocument ⋮---- text: str ⋮---- def to dict self, source: str - dict ⋮---- @dataclass… 证据：`src/rac/services/export.py`
- **Improve**（source_file）：def supports improve spec: ArtifactSpec - bool ⋮---- @dataclass class ImprovementResult ⋮---- type: str missing required: list str missing recommended: list str guidance: dict str, list str = field default factory=dict supported: bool = False closest type: str None = None def to dict self - dict def snake section: str - str def improve product product: Product - ImprovementResult ⋮---- artifact type = classify product .type spec = spec for artifact type ⋮---- guidance = { ⋮---- def improve text text: str - ImprovementResult def improve file path: str - ImprovementResult 证据：`src/rac/services/improve.py`
- **Index**（source_file）：@dataclass class IndexEntry ⋮---- id: str type: str title: str None path: str aliases: list str = field default factory=list search sections: list SearchSection = field default factory=list inbound count: int = 0 def to dict self - dict ⋮---- @dataclass class RepositoryIndex ⋮---- directory: str recursive: bool artifacts: list IndexEntry = field default factory=list ⋮---- @property def artifact count self - int ⋮---- def build repository index directory: str, recursive: bool = True - RepositoryIndex ⋮---- entries = list walk corpus directory, recursive=recursive ⋮---- inbound = inbound counts from corpus entries artifacts: list IndexEntry = ⋮---- spec = spec for entry.artifact type 证据：`src/rac/services/index.py`
- **Which optional extra provides the reader for a given file type. HTML/HTM need**（source_file）：class ConversionError RACError class UnsupportedDocument ConversionError ⋮---- @dataclass class IngestResult ⋮---- source path: str converter: str markdown: str ⋮---- @runtime checkable class DocumentConverter Protocol ⋮---- name: str extensions: tuple str, ... def convert self, path: Path - str: ... class MarkdownConverter ⋮---- name = "markdown" extensions: tuple str, ... = ".md", ".markdown" def convert self, path: Path - str class MarkItDownConverter ⋮---- name = "markitdown" extensions: tuple str, ... = ".docx", ".pdf", ".html", ".htm", ".pptx", ".xls", ".xlsx" ⋮---- result = MarkItDown .convert str path ⋮---- Which optional extra provides the reader for a given file type. HTML/HTM nee… 证据：`src/rac/services/ingest.py`
- **Inspect**（source_file）：@dataclass class InspectionResult ⋮---- type: str confidence: float present sections: list str missing sections: list str status: str None = None category: str None = None supersedes: str None = None relationships: dict str, list str = field default factory=dict def to dict self - dict ⋮---- payload = { ⋮---- value = getattr self, key ⋮---- @dataclass class FileInspection ⋮---- path: str ⋮---- @dataclass class DirectoryInspection ⋮---- directory: str recursive: bool files: list FileInspection ⋮---- @property def total files self - int ⋮---- @property def counts self - dict str, int ⋮---- counts = {spec.name: 0 for spec in ARTIFACT SPECS} ⋮---- @property def unknown count self - int def snak… 证据：`src/rac/services/inspect.py`
- **Completeness recommended sections only — required failures are already**（source_file）：ATTENTION INVALID = "invalid-artifact" ATTENTION MISSING RECOMMENDED = "missing-recommended-sections" ATTENTION BROKEN RELATIONSHIP = "broken-relationship" REL ISSUE PHRASE = { ⋮---- @dataclass class AttentionItem ⋮---- path: str identifier: str severity: str code: str message: str def to dict self - dict ⋮---- @dataclass class PortfolioSummary ⋮---- directory: str recursive: bool by type: dict str, int valid artifacts: int invalid artifacts: int recommended slots: int filled slots: int relationships: RelationshipSummary attention: list AttentionItem = field default factory=list unknown paths: list str = field default factory=list relationships ok: bool = True ⋮---- @property def total arti… 证据：`src/rac/services/portfolio.py`
- 其余 20 条证据见 `AI_CONTEXT_PACK.json` 或 `EVIDENCE_INDEX.json`。

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

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

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

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

## 验收标准

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

---

## Doramagic Context Augmentation

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

## Human Manual 骨架

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

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

- **Overview and Core Concepts**：importance `high`
  - source_paths: README.md, docs/index.md, docs/quickstart.md, docs/artifacts.md, docs/relationships.md
- **Architecture and Engine Components**：importance `high`
  - source_paths: src/rac/cli.py, src/rac/core/artifacts.py, src/rac/core/classification.py, src/rac/core/corpus.py, src/rac/core/frontmatter.py
- **Agent Integration, MCP Server, and Authoring Workflows**：importance `high`
  - source_paths: docs/mcp.md, docs/cli.md, docs/repo-workflow.md, docs/watchkeeper.md, docs/security.md
- **Release Engineering, Repository Topology, and Ecosystem**：importance `high`
  - source_paths: CHANGELOG.md, pyproject.toml, packaging/requirements-as-code-shim/pyproject.toml, packaging/requirements-as-code-shim/PUBLISHING.md, docs/ecosystem.md

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

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `11bd3ed72ef784fa70d578bc97746761a3f87da0`
- inspected_files: `README.md`, `pyproject.toml`, `docs/artifacts.md`, `docs/cli.md`, `docs/ecosystem.md`, `docs/examples/rac-validate.sarif.json`, `docs/examples.md`, `docs/governance.md`, `docs/index.md`, `docs/mcp.md`, `docs/okf-profile.md`, `docs/quickstart.md`, `docs/relationships.md`, `docs/repo-workflow.md`, `docs/research/agent-memory-landscape.md`, `docs/research/team-scale-landscape.md`, `docs/security.md`, `docs/testing.md`, `docs/v0.22-housekeeping-runbook.md`, `docs/validation.md`

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

## Doramagic Pitfall Constraints / 踩坑约束

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

### Constraint 1: 来源证据：repo-topology: rac-sdk — consolidate rac-sdk-ts into rac-sdk/ts/

- Trigger: GitHub 社区证据显示该项目存在一个安装相关的待验证问题：repo-topology: rac-sdk — consolidate rac-sdk-ts into rac-sdk/ts/
- Why it matters: 可能增加新用户试用和生产接入成本。
- Evidence: community_evidence:github | https://github.com/itsthelore/rac-core/issues/240 | 来源讨论提到 python 相关条件，需在安装/试用前复核。
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

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

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

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

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

### Constraint 4: 来源证据：repo-topology: rac-ci — consolidate rac-actions + lore-watchkeeper + lore-gatekeeper

- Trigger: GitHub 社区证据显示该项目存在一个维护/版本相关的待验证问题：repo-topology: rac-ci — consolidate rac-actions + lore-watchkeeper + lore-gatekeeper
- Why it matters: 可能增加新用户试用和生产接入成本。
- Evidence: community_evidence:github | https://github.com/itsthelore/rac-core/issues/238 | 来源类型 github_issue 暴露的待验证使用条件。
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 5: 维护活跃度未知

- Trigger: 未记录 last_activity_observed。
- Host AI rule: 补 GitHub 最近 commit、release、issue/PR 响应信号。
- Why it matters: 新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。
- Evidence: evidence.maintainer_signals | https://news.ycombinator.com/item?id=48714880 | last_activity_observed missing
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

- Trigger: no_demo
- Evidence: downstream_validation.risk_items | https://news.ycombinator.com/item?id=48714880 | no_demo; severity=medium
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 7: 存在评分风险

- Trigger: no_demo
- Why it matters: 风险会影响是否适合普通用户安装。
- Evidence: risks.scoring_risks | https://news.ycombinator.com/item?id=48714880 | no_demo; severity=medium
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 8: 来源证据：Epic: growth programme — adoption of Lore / RAC

- Trigger: GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Epic: growth programme — adoption of Lore / RAC
- Why it matters: 可能影响授权、密钥配置或安全边界。
- Evidence: community_evidence:github | https://github.com/itsthelore/rac-core/issues/230 | 来源类型 github_issue 暴露的待验证使用条件。
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 9: issue/PR 响应质量未知

- Trigger: issue_or_pr_quality=unknown。
- Host AI rule: 抽样最近 issue/PR，判断是否长期无人处理。
- Why it matters: 用户无法判断遇到问题后是否有人维护。
- Evidence: evidence.maintainer_signals | https://news.ycombinator.com/item?id=48714880 | issue_or_pr_quality=unknown
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 10: 发布节奏不明确

- Trigger: release_recency=unknown。
- Host AI rule: 确认最近 release/tag 和 README 安装命令是否一致。
- Why it matters: 安装命令和文档可能落后于代码，用户踩坑概率升高。
- Evidence: evidence.maintainer_signals | https://news.ycombinator.com/item?id=48714880 | release_recency=unknown
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。