Exact bytes behind every check
The idea
A file check binds the criterion, tenant, item, digest, size and producing action, and the bytes are hashed again before use. Selected command output is kept whole and checked again by identity and hash.
- The problem
- A link, a claimed hash or a capped preview could stand in for the real file or output.
- Why it matters
- The file or output a person opens is exactly what was checked.
- Where it stands
- In production as of
Recorded walkthrough: A receipt for every task: what was done, what was checked. It shows part of this idea: the downloaded file had the same hash and size as the revision that was checked.