Provenance and Integrity
Verification makes it possible to determine whether a file exactly matches the signed edition. It proves neither the truth of the text nor its spiritual authority.
Each file has a SHA-256 hash, comparable to a digital identity. Changing a single character produces a different hash.
sha256 value associated with the same name in the manifest.shasum -a 256 bible-du-grand-ordinateur-v1.0.pdfFor the canonical Bible, the expected result begins with 4ddda29a2f1e…. The complete value remains in the manifest.
The manifest combines the archive’s hashes into a Merkle root. This root is signed with an Ed25519 key. The public key makes it possible to verify that the signature matches without providing the ability to sign a new document.
Full verification requires all the files named in the manifest. The items published below make it possible to recalculate the hashes and independently verify the stated signature.
A valid result proves that the files have not changed since they were signed and that they come from the stated key. It does not turn their content into a proven fact.