kc-beta 0.1.0

package/template/skills/zh/meta-meta/version-control/SKILL.md

@@ -0,0 +1,284 @@
+---
+name: version-control
+description: Manage versioning of skills, workflows, prompts, and system configuration throughout the lifecycle. Use when skills are modified, workflows are regenerated, prompts are updated, or any artifact needs rollback capability. Covers what to version, how to version with file-system conventions, maintaining a version manifest, and rollback procedures. Also use when comparing performance between versions or when production results need to trace back to the exact workflow version that produced them.
+---
+
+# 版本控制与制品溯源
+
+## 设计目标
+
+这套版本控制机制不是为了多人协作——在这个系统中，编程智能体是唯一的执行者。版本控制的目的是：
+
+1. **可回退**：任何修改如果导致回归，能立即恢复到上一个正常版本
+2. **可溯源**：生产环境输出的每一条核查结果，都能追溯到产出它的工作流版本、提示词版本、技能版本
+3. **可对比**：能清晰地比较不同版本之间的性能差异，作为迭代决策的依据
+
+轻量是原则。不需要 Git 那样的完整版本控制系统。基于文件系统的命名约定和一份版本清单即可。
+
+## 需要版本管理的制品
+
+### 技能（Skills）
+
+- `rule-skills/R001-xxx/SKILL.md`
+- `rule-skills/R001-xxx/scripts/*.py`
+- `rule-skills/R001-xxx/references/*.md`
+
+技能的版本通过 CHANGELOG.md 追踪，文件本身只保留最新版本。重大变更前手动备份。
+
+### 工作流（Workflows）
+
+- `workflows/R001-xxx/workflow_v1.py`
+- `workflows/R001-xxx/workflow_v2.py`
+- ...
+
+工作流采用文件名版本号机制，所有历史版本的文件共存于同一目录。
+
+### 提示词（Prompts）
+
+- `workflows/R001-xxx/prompts/extract_dates_v1.md`
+- `workflows/R001-xxx/prompts/extract_dates_v2.md`
+
+提示词与工作流类似，采用文件名版本号，历史版本保留。
+
+### 配置（Configs）
+
+- `workflows/R001-xxx/config.json`
+
+配置文件只保留当前版本，但每次修改前将旧版本记录到版本清单中。
+
+## 不需要版本管理的内容
+
+- **日志文件**（`logs/`）：日志本身就是时间序列数据，天然具有版本属性
+- **输出结果**（`Output/`）：每次产出带有时间戳和版本引用，无需单独版本化
+- **测试样本**（`assets/samples.json`）：只增不减，通过 `discovered_in` 字段标注来源轮次
+- **规则目录**（`rule-catalog.json`）：实时状态文件，不需要版本历史
+
+## 文件系统版本命名规范
+
+### 工作流与提示词
+
+采用 `_v{N}` 后缀：
+
+```
+workflow_v1.py    # 初始蒸馏版本
+workflow_v2.py    # 第一次优化
+workflow_v3.py    # 第二次优化
+
+extract_dates_v1.md   # 初始提示词
+extract_dates_v2.md   # 优化后的提示词
+```
+
+版本号单调递增，从不复用。即使 v3 回退到 v1 的逻辑，也不删除 v2 和 v3，而是创建 v4（内容与 v1 相同，但在版本清单中注明原因）。
+
+### 技能文件
+
+技能采用 CHANGELOG.md 记录变更，主文件始终覆盖更新：
+
+```markdown
+## v1.2 - 2025-04-01
+- 补充框架合同展期的判定逻辑
+- 来源：演化循环第3轮
+
+## v1.1 - 2025-03-28
+- 修正边界条件：日期等于到期日视为通过
+- 来源：演化循环第2轮
+
+## v1.0 - 2025-03-25
+- 初始版本
+```
+
+如果需要回退技能，根据 CHANGELOG 中的描述手动恢复。对于关键技能，可在修改前备份为 `SKILL.md.bak`。
+
+## 版本清单：versions.json
+
+工作空间根目录的 `versions.json` 是全局版本清单，记录所有制品的当前版本及历史版本摘要。
+
+```json
+{
+  "workspace_version": "1.0.0",
+  "last_updated": "2025-04-01T18:00:00Z",
+  "skills": {
+    "R001-invoice-date-validity": {
+      "current_version": "v1.2",
+      "skill_accuracy": 0.95,
+      "last_modified": "2025-04-01",
+      "status": "workflow_distilled"
+    },
+    "R002-amount-consistency": {
+      "current_version": "v1.0",
+      "skill_accuracy": 0.88,
+      "last_modified": "2025-03-30",
+      "status": "skill_testing"
+    }
+  },
+  "workflows": {
+    "R001-invoice-date-validity": {
+      "current_version": "v2",
+      "workflow_accuracy": 0.92,
+      "model_tier": "TIER3",
+      "prompt_versions": {
+        "extract_dates": "v2",
+        "judge_validity": "v1"
+      },
+      "distilled_from_skill_version": "v1.2",
+      "last_modified": "2025-04-01",
+      "status": "production"
+    }
+  },
+  "config": {
+    "env_hash": "a3b2c1d4",
+    "last_modified": "2025-03-25"
+  }
+}
+```
+
+### 版本清单的更新时机
+
+每次以下操作发生时，必须同步更新 versions.json：
+
+- 技能 CHANGELOG 新增条目
+- 工作流创建新版本文件
+- 提示词创建新版本文件
+- 模型层级变更
+- 工作流进入或退出生产状态
+
+## 何时创建新版本
+
+**核心规则：在修改任何可工作的制品之前，先创建新版本。**
+
+具体而言：
+
+### 必须创建新版本的场景
+
+- 优化工作流的提取逻辑 → 创建 `workflow_v{N+1}.py`
+- 修改提示词 → 创建 `prompt_v{N+1}.md`
+- 演化循环要求修改判定逻辑 → 更新技能 CHANGELOG，创建工作流新版本
+
+### 不需要创建新版本的场景
+
+- 修正注释或格式（不影响逻辑的变更）
+- 更新测试样本数据
+- 修改日志内容
+
+## 回退操作
+
+当新版本导致回归或性能下降时，执行回退：
+
+### 回退步骤
+
+1. 在 versions.json 中将 `current_version` 修改为目标版本
+2. 在工作流 config.json 中更新版本引用
+3. 在 `logs/evolution/` 中记录回退原因
+4. **不要删除失败的版本文件**——保留用于后续分析
+
+### 回退日志
+
+```json
+{
+  "action": "rollback",
+  "rule_id": "R001",
+  "artifact": "workflow",
+  "from_version": "v3",
+  "to_version": "v2",
+  "reason": "v3 在框架合同场景下准确率从 92% 下降到 78%",
+  "timestamp": "2025-04-01T20:00:00Z",
+  "failed_version_kept": true
+}
+```
+
+## 结果溯源
+
+生产环境输出的每一条核查结果都必须包含版本信息：
+
+```json
+{
+  "document_id": "DOC-2025-0042",
+  "rule_id": "R001",
+  "verdict": "pass",
+  "produced_by": {
+    "workflow_version": "v2",
+    "prompt_versions": {
+      "extract_dates": "v2",
+      "judge_validity": "v1"
+    },
+    "model_tier": "TIER3",
+    "skill_version": "v1.2",
+    "workspace_version": "1.0.0"
+  },
+  "timestamp": "2025-04-01T18:30:00Z"
+}
+```
+
+这样，当质控发现某条结果有误时，可以精确定位到产出它的工作流版本和提示词版本，避免在排查过程中浪费时间。
+
+## 核查溯源标识（Trace ID）
+
+版本溯源解决的是「哪个版本产出了这条结果」。溯源标识解决的是更深一层的问题：**这条核查结论的证据在原文的哪个位置？**
+
+在每条核查结果中嵌入一个永久性溯源标识，直接链接到原始证据的精确位置。
+
+### 溯源标识结构
+
+```json
+{
+  "trace_id": "R001-DOC042-P3-S2-C120:180",
+  "source_location": {
+    "document": "bank_annual_report_2024.pdf",
+    "page": 3,
+    "section": "3.2 资本充足率",
+    "char_range": [120, 180]
+  },
+  "rule_version": "v1.2",
+  "workflow_version": "v2",
+  "model_tier": "TIER3"
+}
+```
+
+### 三个关键属性
+
+- **嵌入式，非日志式**：溯源标识嵌入在核查结果数据内部，而非保存在独立的日志文件中。无论结果被导出、重新导入、聚合还是被下游系统消费，溯源标识始终随结果同行。
+- **永久性**：溯源标识一旦生成，永不修改。对同一文档重新核查会生成新的溯源标识——旧标识保留在历史结果中。
+- **自包含**：溯源标识本身编码了足够的信息来定位原始证据，无需查询外部索引。
+
+### 为什么这很重要
+
+如银保监会现场检查时，审计人员问「你们为什么判定这笔贷款符合第十五条？」——溯源标识可以直接指向原文的精确段落、判定时使用的规则版本和工作流版本。没有溯源标识，这种回溯需要手动关联日志、结果和原始文档——在监管审计中，这种手动关联是不可接受的。
+
+参见 `references/trace-id-spec.md` 获取完整的格式规范和生成算法。
+
+## 与演化循环的集成
+
+演化循环的每一轮迭代，都是版本控制的触发事件：
+
+```
+演化循环第 N 轮开始
+  → 记录当前版本快照
+  → 执行修改
+  → 创建新版本
+  → 测试
+  → 如果回归 → 回退版本
+  → 如果通过 → 更新版本清单
+演化循环第 N 轮结束
+```
+
+版本控制为演化循环提供安全网——无论怎么改，都可以回到上一个已知好的状态。
+
+## 版本对比
+
+当需要评估不同版本的性能差异时，利用日志中的测试结果进行对比：
+
+```json
+{
+  "comparison": {
+    "rule_id": "R001",
+    "versions": ["v1", "v2"],
+    "metrics": {
+      "v1": {"accuracy": 0.85, "avg_cost": 0.005, "model_tier": "TIER2"},
+      "v2": {"accuracy": 0.92, "avg_cost": 0.003, "model_tier": "TIER3"}
+    },
+    "conclusion": "v2 在准确率和成本两个维度均优于 v1"
+  }
+}
+```
+
+这些对比数据也是仪表盘展示的重要素材。

package/template/skills/zh/meta-meta/version-control/references/trace-id-spec.md

@@ -0,0 +1,79 @@
+# Trace ID Specification
+
+Trace IDs embed source evidence pointers directly inside verification results. This document defines the format, generation rules, and integration points.
+
+## Format
+
+```
+{rule_id}-{document_id}-P{page}-S{section}-C{char_start}:{char_end}
+```
+
+| Segment | Description | Example |
+|---------|-------------|---------|
+| `rule_id` | The rule that produced this result. Matches the ID in `rule-catalog.json`. | `R001` |
+| `document_id` | A short identifier for the source document. Derived from filename or batch assignment. | `DOC042` |
+| `P{page}` | The 1-indexed page number where the source evidence appears. | `P3` |
+| `S{section}` | The section number within the page, following the document's own numbering. | `S2` |
+| `C{char_start}:{char_end}` | Character offset range within the extracted text block that constitutes the evidence. | `C120:180` |
+
+Full example: `R001-DOC042-P3-S2-C120:180`
+
+When a rule draws evidence from multiple locations, generate one trace ID per location and store them as an array in the result.
+
+## Generation
+
+Trace ID generation is **deterministic**: the same rule applied to the same document at the same location always produces the same trace ID. This is achieved by deriving every segment from stable inputs:
+
+- `rule_id` comes from the rule catalog.
+- `document_id` comes from the document's filename or a developer-user-assigned identifier.
+- Page, section, and character range come from the extraction step.
+
+Trace IDs are generated at verification time, immediately after entity extraction identifies the source location. They are never modified after creation. Re-verifying the same document produces new result records with new timestamps but identical trace IDs (because the source location has not changed). If the document is modified, the new version gets a new `document_id`, producing different trace IDs.
+
+## Collision Avoidance
+
+The combination of rule ID + document ID + page + section + character range makes collisions astronomically unlikely in practice. Two different pieces of evidence would need to match on all five segments simultaneously.
+
+If document IDs are not guaranteed unique across batches (e.g., multiple batches contain files named `report.pdf`), prefix the document ID with the batch identifier: `B003-DOC042`. This extends the trace ID format to `R001-B003-DOC042-P3-S2-C120:180`.
+
+Do not use random UUIDs. Deterministic trace IDs allow deduplication and comparison across verification runs.
+
+## Storage Overhead
+
+A single trace ID string is approximately 30-50 bytes. The full trace ID object (including `source_location`, `rule_version`, `workflow_version`, and `model_tier`) is approximately 100-200 bytes in JSON.
+
+For a typical batch of 1000 verification results, trace IDs add roughly 100-200 KB of storage. This is negligible relative to the result data itself and the source documents.
+
+## Surviving Export/Re-Import
+
+Trace IDs are embedded in the result JSON structure, not stored in external metadata, sidecar files, or database columns that might be lost during export.
+
+Any system that consumes the verification result JSON automatically receives the trace IDs. Specific scenarios:
+
+- **CSV export**: The `trace_id` field becomes a column. A developer user reviewing results in a spreadsheet can copy a trace ID and paste it back to locate the source evidence.
+- **Aggregation**: When results from multiple batches are merged, trace IDs remain attached to their individual results. No re-linking is needed.
+- **Downstream APIs**: Systems consuming verification results via API receive trace IDs as part of the payload. They can store, index, or display them without any awareness of the trace ID format.
+- **Archival**: Archived results retain full traceability years later, even if the original verification system has evolved.
+
+## Integration with Cross-Document Verification
+
+When `cross-document-verification` detects a contradiction between two documents, reference trace IDs from both sides:
+
+```json
+{
+  "contradiction": {
+    "field": "total_assets",
+    "document_a": {
+      "trace_id": "R005-DOC042-P7-S1-C200:260",
+      "value": "1,234,567"
+    },
+    "document_b": {
+      "trace_id": "R005-DOC043-P3-S2-C80:140",
+      "value": "1,234,590"
+    },
+    "discrepancy": "23"
+  }
+}
+```
+
+This creates a linked evidence chain: auditors can follow both trace IDs to the exact locations in both documents, verify the extracted values, and determine which document (if either) is correct. Without trace IDs, cross-document contradictions require manual search through both documents to find the relevant passages.

package/template/skills/zh/skill-creator/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.