CASE STUDIES
Engineering case studies and product evidence.
Blackbox case studies document the technical problem, the implementation, the negative controls or test evidence, and the remaining boundary for a specific product capability. External customer results are identified separately when customer evidence exists.
What an engineering case study claims here
Each study documents a specific product capability through four lenses: the engineering problem it answers, the implementation as it currently stands, the negative controls or test evidence that exercise it, and the boundary of what the evidence does and does not establish. The claim is scoped to the tested surface, not extended to the whole product or to any deployment.
Evidence class is stated, not implied
We keep three things distinct that are routinely blurred elsewhere. Engineering evidence is what a tested surface demonstrates in the repository. A customer result is a separate class, identified separately and only where customer evidence actually exists. Certification and legal admissibility are a third class, which these studies do not assert. Reading which class a statement belongs to is the first act of reading it honestly.
The boundary is part of the evidence
Every study ends on what remains separately evidenced — customer deployment, filesystem-specific durability, certification, integration activation. That section is not a disclaimer bolted on; it is the honest edge of the claim. A result that cannot name its own limit is not yet evidence, and a reader is entitled to see the limit as plainly as the capability.
Portable evidence verification architecture
Receipt chains, deterministic hashing, detached signatures, release verification and large-corpus stress testing across the current evidentiary substrate.
Read case studyDURABLE RECEIPTSReceipt continuity under partial writes, concurrency and corruption
Crash-safe append, chain-head serialization, torn-tail handling and explicit corruption behavior in the current receipt store.
Read case studyPORTABLE RELEASESDetached release verification
Declared payload universes, manifest binding, detached signatures and adversarial release checks outside the originating runtime.
Read case studyHISTORICAL CUSTODYLegacy receipt migration without rewriting history
Non-destructive migration preparation that preserves legacy bytes, cryptographic boundary state and explicit activation limits.
Read case study