Part of Stem. This page defines the tombstone target of a Node.

The resource is deleted: it has no current state, its id stays taken, its name becomes free, and earlier versions remain retrievable.

Fields

field	type	required	meaning
`kind`	literal `tombstone`	yes	Target kind tag.

Rules

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.

Today (HM24)

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.

Example

{"kind": "tombstone"}

Fields

Rules

Today (HM24)

Example

See also