DRAFT — not a shipped protocol. See design notes.
DRAFT HM26 tombstone resource. Not a shipped protocol schema.
BaseResource extends the existing signed Blob envelope; all six resource variants extend BaseResource. BaseResource owns optional resource identity, parent placement and relative name. It has no stored type override or fixed resource type tag. The inherited Blob envelope still requires a stored string type; arbitrary strings satisfy that structural constraint. Whether HM26 should eliminate the inherited field is an open envelope-design question. No replacement dispatch mechanism is introduced. Required kind selects the six closed resource variants.
{
"type": "hm://z6MkiAKDcRSzQ4zPZfnJcS5HYx5MwgN6MU9foHihJGrhqNBj/hm26/base-resource",
"properties": {
"kind": {
"value": "tombstone",
"required": true,
"description": "Closed resource-variant discriminator."
},
"prev": {
"value": {
"type": "hm://hyper.media/cid"
},
"required": false,
"description": "Optional previous resource-version CID for walking history; conveys no authority."
}
},
"description": "DRAFT HM26 tombstone resource. Not a shipped protocol schema."
}Learn this in the sync playground
Sync playground extension · 2026-10-23. Teaching prototype; no production protocol or schema adoption.
A tombstone is still an immutable selected statement that can be synchronized. It does not erase blobs already held by another peer. Its history breadcrumb must not be confused with permission or automatic containment; deletion and revival semantics remain separate from transport.
Read next: Ref · selected version · Stored bytes · Reference.
Do you like what you are reading? Subscribe to receive updates.
Unsubscribe anytime