coulomb/target-revenue
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix stale administrative-correction reference in TargetLedgerSpecification §5

Browse source 
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 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-07-29 19:49:51 +02:00
parent ba5a4175b0
commit 8da3c6b3de
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
specs/TargetLedgerSpecification.md
View file

@ -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)