- OQ-BL-03 RESOLVED: BLAKE3's presence traced to pure iroh-blobs
inheritance; with that rejected the multi-hash framing dissolves.
Three tiers: canonical git-blob-sha-256 (git oids + every other
consumer share one address domain — cross-consumer dedup free),
tolerated git-blob-sha-1 (protocol necessity, git's hardened-SHA-1
threat model), conditional BLAKE3 (only if a bao-like chunk-tree
encoding is ever adopted; confined to that encoding layer)
- Principle 2 rewritten (one canonical hash, git-family derivation);
alkgit consumer entry updated (the 'hash conflict' was an artifact
of the BLAKE3 inheritance); p2p section notes strengthened dedup
- OQ-BL-04: verification options no longer BLAKE3-mandatory; chunk-
tree encoding note — verified wholes register under the canonical
hash so chunked and whole-file paths dedup together
- POC register: #2 absorbed into #1 (postamble abstraction + SHA-1
tolerance are #1's trait work); #3 gains the sqlite-vs-fs
micro-benchmark pull-out
- AGENTS.md convention 5 aligned (canonical git-family derivation)
glm-5.3-flash
cde279b76d