kc-beta 0.1.0

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

@@ -0,0 +1,152 @@
+---
+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.
+---
+
+# Version Control
+
+Version control here is about auditability and rollback, not collaboration. You need to know what changed, when, why, and be able to undo it if the change made things worse.
+
+## What to Version
+
+Everything that affects verification results:
+
+- **Rule skills**: SKILL.md edits, script changes, reference updates, new corner cases.
+- **Workflows**: Python code, LLM prompts, model assignments, configuration.
+- **System configuration**: .env threshold changes, model tier updates.
+- **Rule catalog**: New rules added, rules modified, rules deprecated.
+
+What NOT to version:
+- Logs (they are append-only, versioning is inherent).
+- Output results (they already reference the workflow version that produced them).
+- Temporary analysis files.
+
+## How to Version
+
+### File-System Based Versioning
+
+Keep it simple. No database, no external tools. File naming + a JSON manifest.
+
+**Workflows**: Each iteration is a separate file.
+```
+workflows/rule_001/
+  workflow_v1.py
+  workflow_v2.py    # Fixed extraction regex
+  workflow_v3.py    # Downgraded to TIER3
+  prompts/
+    extract_v1.txt
+    extract_v2.txt  # Simplified prompt
+  config.json       # Points to active versions
+```
+
+**Skills**: Track changes in a changelog within the skill folder.
+```
+rule-skills/rule-001-capital-adequacy/
+  SKILL.md              # Current version
+  CHANGELOG.md          # What changed and when
+  assets/
+    samples.json        # Grows over time (append-only)
+    corner_cases.json   # Grows over time (append-only)
+```
+
+### Version Manifest
+
+Maintain a `versions.json` at the workspace root that tracks the active version of each artifact:
+
+```json
+{
+  "last_updated": "2026-04-01T14:30:00Z",
+  "rules": {
+    "R001": {
+      "skill_version": "2026-03-28",
+      "workflow_version": "v3",
+      "workflow_file": "workflows/rule_001/workflow_v3.py",
+      "prompt_version": "v2",
+      "model_tier": "TIER3",
+      "status": "production"
+    }
+  }
+}
+```
+
+This manifest is the single source of truth for what is currently active. Update it whenever you change the active version of anything.
+
+## When to Create a New Version
+
+**Always create a new version before modifying a working artifact.** The rule is simple:
+
+1. The current artifact is working (or at least, it is the best you have).
+2. You want to try a change.
+3. Copy the current artifact to a new version file.
+4. Make the change in the new version.
+5. Test the new version.
+6. If it is better, update the manifest to point to the new version.
+7. If it is worse, the old version is still there unchanged.
+
+Never modify a version file in place. Version files are immutable once created.
+
+## Rollback
+
+When a new version performs worse than the previous one:
+
+1. Update the manifest to point back to the previous version.
+2. Log the rollback: what was tried, what went wrong, why the previous version is better.
+3. Keep the failed version file for reference — do not delete it. It records what does not work.
+
+## Result Traceability
+
+Every verification result in Output/ should include metadata linking it to the exact versions that produced it:
+
+```json
+{
+  "rule_id": "R001",
+  "workflow_version": "v3",
+  "prompt_version": "v2",
+  "model_used": "Qwen/Qwen3.5-122B-A10B",
+  "timestamp": "2026-04-01T14:30:00Z"
+}
+```
+
+This enables debugging: if a result is wrong, you can trace it to the exact workflow, prompt, and model that produced it.
+
+## Verification Trace IDs
+
+Beyond version traceability (which version produced a result), embed a permanent trace ID in every verification result that links to the exact source evidence.
+
+### Trace ID Structure
+
+```json
+{
+  "trace_id": "R001-DOC042-P3-S2-C120:180",
+  "source_location": {
+    "document": "report_2024_q1.pdf",
+    "page": 3,
+    "section": "3.2 Capital Adequacy",
+    "char_range": [120, 180]
+  },
+  "rule_version": "v1.2",
+  "workflow_version": "v3",
+  "model_tier": "TIER3"
+}
+```
+
+### Key Properties
+
+- **Embedded, not logged**: Trace IDs live IN the verification result data, not in a separate log. They survive export, re-import, aggregation, and downstream consumption.
+- **Permanent**: Once assigned, a trace ID never changes. Re-verifying the same document generates a new trace ID — old ones remain in historical results.
+- **Self-contained**: The trace ID encodes enough information to locate the source evidence without consulting external indexes.
+
+### Why This Matters
+
+When an auditor asks "why did you determine this loan complies with Article 15?", the trace ID points directly to the exact text passage, the exact rule version, and the exact workflow that made the determination. Without trace IDs, this reconstruction requires correlating logs, results, and source documents manually — which in a regulatory audit is unacceptable.
+
+See `references/trace-id-spec.md` for the full format specification and generation algorithm.
+
+## Integration with Evolution Loop
+
+Every evolution cycle (see `evolution-loop`) should:
+1. Create new version files for any changes.
+2. Update the manifest.
+3. Log the version change with the evolution iteration number.
+
+The version history, combined with the evolution logs, gives you a complete timeline of how the system evolved and why.

package/template/skills/en/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/en/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.