A tombstone must supersede: its Node blob lists the blobs it replaces in prev. A tombstone concurrent with a state-bearing Node blob loses, so an offline edit never silently vanishes; the next writer sees both and decides. A later Node blob with a state target that lists the tombstone in prev undeletes the resource. The space root cannot be tombstoned. Children of a tombstoned node keep their ids and parents; listings hide them, and a client may offer to move or delete them. Deleting a resource never unshares bytes that peers already hold; it stops the resource being served as current.

A Ref with genesisBlob and empty heads and no republish. Alive versus deleted is decided by comparing the newest tombstone timestamp with the newest alive timestamp, a last-writer-wins rule on unvalidated clocks. Stem decides by causal order instead.