HM26 node-redirect (draft)

A provisional HM26 schema for review, with unresolved semantics recorded in the overview.

Starlight

14 October 2026, 11:03

Starlight

14 October 2026, 11:03

ContentPeople2CommentsCitationsAttributes0

Fetching schema…

DRAFT — not a shipped protocol. See design notes.

DRAFT HM26 redirect node. Not a shipped protocol schema.

BaseNode extends the existing signed Blob envelope; all six node variants extend BaseNode. BaseNode owns optional node identity, parent placement and relative name. It has no stored type override or fixed node 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 node variants.

{
  "type": "hm://z6MkiAKDcRSzQ4zPZfnJcS5HYx5MwgN6MU9foHihJGrhqNBj/hm26/base-node",
  "properties": {
    "kind": {
      "value": "redirect",
      "required": true,
      "description": "Closed node-variant discriminator."
    },
    "prev": {
      "value": {
        "type": "hm://hyper.media/cid"
      },
      "required": false,
      "description": "Optional previous node-version CID for walking history; conveys no authority."
    },
    "target": {
      "value": {
        "type": "hm://hyper.media/cid"
      },
      "required": true,
      "description": "Destination node identity CID, provisionally; resolution semantics are open."
    }
  },
  "description": "DRAFT HM26 redirect node. Not a shipped protocol schema."
}

Do you like what you are reading? Subscribe to receive updates.

Unsubscribe anytime