From 451f245cf1d20201d663699d6a3d9b5d78a55336 Mon Sep 17 00:00:00 2001 From: evosoft-ie Date: Sun, 28 Dec 2025 11:55:41 +0000 Subject: [PATCH] Revise guarantees section and add non-aggregation clause Updated section headings for clarity and added a new section on non-aggregation for personnel evaluation. --- spec/guarantees.md | 26 ++++++++++++++++++++++---- 1 file changed, 22 insertions(+), 4 deletions(-) diff --git a/spec/guarantees.md b/spec/guarantees.md index 9ce3da0..4acf2df 100644 --- a/spec/guarantees.md +++ b/spec/guarantees.md @@ -63,7 +63,7 @@ older provenance remains valid in newer versions AILint explicitly does not guarantee: -3.1 Authorship or Ownership +## 3.1 Authorship or Ownership AILint does not: @@ -73,7 +73,7 @@ establish copyright ownership replace attribution requirements -3.2 Detection Accuracy +## 3.2 Detection Accuracy AILint does not guarantee: @@ -85,7 +85,7 @@ identification of specific models or tools Inference is always best-effort. -3.3 Intent or Responsibility +## 3.3 Intent or Responsibility AILint does not: @@ -95,7 +95,7 @@ assign responsibility evaluate ethics or compliance -3.4 Content Quality +## 3.4 Content Quality AILint does not: @@ -105,6 +105,24 @@ assess safety validate factual accuracy +## 3.5 Non-Aggregation for Personnel Evaluation + +AILint guarantees that: + +**The specification does NOT support aggregation for personnel evaluation** + +What this means: +- Tools SHOULD NOT aggregate provenance at developer level +- HR or performance monitoring is out of scope +- Reporting focuses on repository/module scope, not individuals + +**Acknowledgment:** +We cannot technically prevent misuse, but we establish the normative boundary: + +**Aggregating provenance data for performance reviews or hiring decisions is contrary to AILint's purpose.** + +Organizations should establish policies prohibiting such use. + 4. Heuristic Interpretation Disclaimer When explicit provenance is absent: