Credibility Stack
BuiltSignature capability
The report documents a strategy that failed and was shut down, and makes no forward performance claim. It is written to be checked, not to persuade.
What it is
Two halves. The provenance spine gives every result a content hash over a canonical serialization, chained into an append-only journal alongside config fingerprints, so any figure can be traced and replayed. The due-diligence report is a factual record of combined_sleeve_v1: validated, deployed, failed its own pre-registered acceptance battery, retired.
Highlights
- Every hash covers a canonical serialization, and floats are rejected before hashing rather than silently coerced, so a caller bug fails loud instead of producing an unreproducible digest.
- Append-only hash-chained journal with verify and replay, so a figure quoted in a report can be traced back to the run that produced it.
- The due-diligence report states that every figure was recomputed from the project environment rather than quoted from a prior report, with two independent reproductions agreeing to three decimal places.
- Written for an allocator and operational due-diligence audience, in the register such a reader expects.
Tech · Python, canonical serialization, SHA-256 hash chaining, deterministic replay, pytest.