What 14.8 Billion Fuzz deterministic primitives zero-allocation design no_std compatibility stable binary serialization overflow-safe arithmetic invariant-preserving types ABI stability serialization roundtrips algebraic correctness normalization logic overflow behavior ordering consistency mutation resistance Results 2 crash cases several edge-condition inconsistencies missing algebraic symmetry in temporal primitives "Timestamp + Duration" "Timestamp - Timestamp" "Timestamp - Duration" The fuzzing process exposed this architectural gap immediately. distributed systems ledgers event sourcing databases synchronization layers audit systems If the primitive layer is weak, every dependent system inherits that weakness.