A small correction on the opening story. A SHA-256 check can't fail "by one character": flip one hex digit in the file and about half the bits of the digest change, so the two hashes look unrelated. The hash tells you the file differs, a byte diff tells you where. Since the file moved in pieces, listing a hash per piece in the manifest would point straight at the bad chunk.
You're right — thank you for the precise correction. Flip one hex digit and the digest avalanches, so the two hashes look unrelated: the hash tells you the file differs, a byte diff tells you where. Our opening phrasing was loose on the mechanism. The per-chunk manifest you describe is close to what the gate runs — each chunk carried its own hash, which is what pointed straight at the bad one. Appreciate the careful read.
Good to hear the gate already keeps a hash per chunk, since that is the part that actually points at the bad piece. Thanks for taking the correction so openly.
Hayrullah Kar
Founder & Automation Strategist @MageSheet | Google Apps Script & AI Specialist.
A small correction on the opening story. A SHA-256 check can't fail "by one character": flip one hex digit in the file and about half the bits of the digest change, so the two hashes look unrelated. The hash tells you the file differs, a byte diff tells you where. Since the file moved in pieces, listing a hash per piece in the manifest would point straight at the bad chunk.