hash is the load-bearing field: an opaque <algorithm>:<hex> content
digest of the model bytes (the CLI writes sha256:…). path is a
convenience for humans reading the file and is never compared — paths move,
and a comparison on one would reject a valid map for the wrong reason while
accepting an edited file at the same path.
Which model a set of claims was derived from.
hash is the load-bearing field: an opaque
<algorithm>:<hex>content digest of the model bytes (the CLI writessha256:…). path is a convenience for humans reading the file and is never compared — paths move, and a comparison on one would reject a valid map for the wrong reason while accepting an edited file at the same path.