Release ledger
Every release is sealed into a SHA-256 hash chain. The same evidentiary structure we sell to customers, applied to our own work. If our release history isn't defensible, nothing downstream can be.
April 2026
April 2026
db75c3bd175eefb1…419f1962·prev79f7fa085300…March 2026
March 2026
79f7fa08530054b0…1c6a505d·prev9bbef1227b82…March 2026
March 2026
9bbef1227b822007…b686b588·preveb732eceae88…February 2026
February 2026
eb732eceae885ebd…fa349480·prev8fb510de27a5…January 2026
January 2026
8fb510de27a5613e…414d25d5·prev64c274daa5f9…December 2025
December 2025
64c274daa5f9c3d6…f4ca4053·prev4b523b63ad89…November 2025
November 2025
4b523b63ad89089e…79b9ecbc·prevgenesisVerify the chain
Download the signed manifest. Recompute the chain. Every hash must match. If any field in any past entry is altered, even a single character, every downstream hash breaks.
Chain parameters