From 5e6a28fe722cefaa7354e205c2f62af62beb033a Mon Sep 17 00:00:00 2001 From: Dekimu Date: Fri, 24 Jul 2026 15:33:36 +0200 Subject: [PATCH] fix(spec): correct ARR wire id to ar.erasure.v1 + disambiguate rac vs ar evaluation MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - evidence.md §3.1: ARR wire id corrected from ar.retention.v1 (dangling — the public anchors-spec family-consistency.md keys ARR as ar.erasure.v1). - evidence.md §3: soften the false one-to-one union claim to a subset binding. - receipt.md: disambiguate rac.evaluation.v1 from anchors ar.evaluation.v1/AER. regression check: grep -rn 'ar.retention.v1' spec/ (must be empty — no dangling wire id) Signed-off-by: Dekimu --- spec/evidence.md | 8 +++++--- spec/receipt.md | 7 +++++++ 2 files changed, 12 insertions(+), 3 deletions(-) diff --git a/spec/evidence.md b/spec/evidence.md index 129ecf8..8004cb8 100644 --- a/spec/evidence.md +++ b/spec/evidence.md @@ -147,7 +147,7 @@ carry and a requirement may reference. |----------|---------------------|--------------------------------------| | `APR` | `ar.provenance.v1` | Agent Provenance Receipt — a recorded agent action / data-processing provenance event. | | `ACR` | `ar.consent.v1` | Anchored Consent Receipt — a recorded, informed grant of consent. | -| `ARR` | `ar.retention.v1` | Anchored Retention Receipt — a recorded data-retention schedule / retention-enforcement run. | +| `ARR` | `ar.erasure.v1` | Anchored Retention Receipt — a recorded data-retention schedule / retention-enforcement run. (The retention family's canonical discriminator is `ar.erasure.v1`; it spans the erasure/expiry/hold/anonymization/archive/batch claim types.) | | `ALR` | `ar.lineage.v1` | Anchored Lineage Receipt — a recorded data-flow / lineage step. | | `ATR` | `ar.transfer.v1` | Anchored Transfer Receipt — a recorded cross-border data transfer (GDPR Ch. V / Schrems II). | | `APuR` | `ar.purpose.v1` | Anchored Purpose Receipt — a recorded processing purpose. | @@ -160,8 +160,10 @@ carry and a requirement may reference. | `AIR` | `ar.impact.v1` | Anchored Impact Receipt — a recorded impact assessment such as a DPIA (GDPR Arts. 35–36). | | `ATokR` | `ar.tokenization.v1`| Anchored Tokenization Receipt — a recorded PII-tokenization lifecycle event. | -These map one-to-one to the locked `AnchorsFamily` union in the reference -implementation. The acronyms (`APR`, `ACR`, …) are documentation shorthand; the +These 14 are the GDPR-core subset of the anchors family registry that RaC's +reference binding pins; the registry itself has grown beyond them, so this is a +**subset** mapping, not a one-to-one of the full `AnchorsFamily` union. The +acronyms (`APR`, `ACR`, …) are documentation shorthand; the canonical wire identifier is the `ar..v` form. The exact wire formats are an anchors concern and are **out of scope** for this spec; RaC sees only the projected `CorpusReceipt`. diff --git a/spec/receipt.md b/spec/receipt.md index 57cf8cb..d898d3b 100644 --- a/spec/receipt.md +++ b/spec/receipt.md @@ -37,6 +37,13 @@ both identically to `compilation.md`. > signed object, and the algorithm match the implementation exactly. A verifier > targeting this spec MUST treat `rac.evaluation.v1` as the discriminator and > SHOULD accept `compass.evaluation.v1` as its reference-implementation alias. +> +> **Do not confuse this with the anchors family `ar.evaluation.v1` (AER).** They +> are distinct receipt types: an RaC evaluation receipt records **obligation +> satisfaction over an evidence corpus** (many predicates, one compliance +> verdict), whereas AER records a **single conformity / automated-decision +> event**. Same English word, different structure and purpose; they do not +> interoperate. ---