DRAFT — not a shipped protocol. See design notes.
DRAFT HM26 change DAG element. Deterministic DAG ordering is intended but its exact rule is open; operations remain generic IPLD values.
{
"type": "hm://hyper.media/blob",
"properties": {
"type": {
"value": "HM26Change",
"required": true,
"description": "Distinct draft signed Change type tag."
},
"deps": {
"value": {
"type": "hm://hyper.media/list",
"items": {
"type": "hm://hyper.media/cid"
}
},
"required": true,
"description": "Multiple ancestor Change CIDs; empty for a root. Canonical dependency ordering is open."
},
"ops": {
"value": {
"type": "hm://hyper.media/list",
"items": {
"type": "hm://hyper.media/any"
}
},
"required": true,
"description": "Ordered operations interpreted by the exact function referenced by the consuming resource. Operation shape is provisional."
}
},
"description": "DRAFT HM26 change DAG element. Deterministic DAG ordering is intended but its exact rule is open; operations remain generic IPLD values."
}Learn this in the sync playground
Sync playground extension · 2026-10-23. Teaching prototype; no production protocol or schema adoption.
A change can have multiple dependency arrows. Shared ancestors appear once in the graph, which is why a DAG is more general than a tree. The simulator does not acknowledge a closure with missing, cyclic or cross-resource dependencies.
Read next: Change · DAG · dependency graph · frontier table.
Change
An immutable signed edit with explicit predecessor dependencies.
A selected change-bearing version points to change heads. Each change can depend on multiple earlier changes. The simulator walks valid same-resource dependencies; missing, cross-resource and cyclic dependencies stay unresolved and prevent a completion receipt. Application ordering and the immutable apply contract are separate HM26 design questions.
Do you like what you are reading? Subscribe to receive updates.
Unsubscribe anytime