Erasure Tombstone — history
The dated record of how Erasure Tombstone got here, begun on 2026-11-13 when the spec’s tombstones moved out of it because a reader does not need them to use the spec today; everything smaller is in git log -- atoms/erasure-tombstone.md.
Decisions
- 2026-11-01 — Drafted as the extraction nine compositions name. Chose: one record per destruction — destroyed pattern, destroyed id, destruction instant, authority kind and reference, actor — with no content of the destroyed record and no state, three actions (record, read one, list a window), the destroying pattern calling [Record Destruction] in the transaction that deletes, two authority kinds every deployment keeps and others it may add, and stated default caps a deployment may override. The record is named erasure tombstone in full, since GRACE-lang already calls a deleted rule’s label a tombstone. Over: a tombstone that also deletes, judges lawfulness, or keeps any field of the destroyed record. Because: Scott’s interview of 2026-11-01 and his ruling the same day that a host’s bounds take a stated default a deployment may override; the atom carries exactly what the nine compositions’ extraction-pending facts need, and nothing a deletion would have to forget.
Deleted rules
The spec’s tombstones, moved here from the page on 2026-11-13 because the spec is done (GRACE-lang Hard invariant 25 and Hard invariant 27, since v0.71): each Deleted: line byte for byte and in the page’s order, under the heading it stood under there. A tombstone carries no obligation, and each still reserves its label: no rule of Erasure Tombstone may carry it again.
Structure › Operations
Deleted: Operation 17. Term matching erasure tombstone owns it.
Generation acceptance › Conformance checks
Deleted: Check 5.1. Execution Contract Database 6 owns it: a purge another specification declares is answered by that specification's records.