From 8da3c6b3de1c3a6bcffc49bcbaf4133e3cb31afd Mon Sep 17 00:00:00 2001 From: tegwick Date: Wed, 29 Jul 2026 19:49:51 +0200 Subject: [PATCH] =?UTF-8?q?Fix=20stale=20administrative-correction=20refer?= =?UTF-8?q?ence=20in=20TargetLedgerSpecification=20=C2=A75?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Found while preparing WP-0003-T06 for review: §5's prose still named the unsplit administrative-correction type (renamed to administrative-correction-development/-remission earlier this session) and incorrectly implied both admin-correction types require a reverses pointer, when only credit-reversal and remission-correction do. Co-Authored-By: Claude Sonnet 5 --- specs/TargetLedgerSpecification.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specs/TargetLedgerSpecification.md b/specs/TargetLedgerSpecification.md index 59d7c08..6ab5d35 100644 --- a/specs/TargetLedgerSpecification.md +++ b/specs/TargetLedgerSpecification.md @@ -51,7 +51,7 @@ Reference implementation: `src/target_revenue/hashing.py::entry_hash`, `verify_c ## 5. Corrections without erasure -Per Rule 8, the ledger is append-only. A correction or reversal is always a **new** entry (`credit-reversal`, `remission-correction`, or `administrative-correction`) referencing the entry it corrects via `reverses` — never an edit or deletion of the original. This preserves the audit trail even when the correction is disputed. +Per Rule 8, the ledger is append-only. A correction or reversal is always a **new** entry — `credit-reversal` and `remission-correction` reference the entry they correct via `reverses`; `administrative-correction-development` and `administrative-correction-remission` are generic corrections not tied to a specific prior entry (§2) — never an edit or deletion of the original. This preserves the audit trail even when the correction is disputed. ## 6. Outstanding Target fold (normative definition)