# SHA-256 48-bit truncated collision (λ=24)

## Result
inputA = `m8848078`, inputB = `m10095555` (UTF-8). Delivered in `collision.json`.

## Evidence (facts, computed locally with Python hashlib)
- sha256("m8848078") = 1d68689881149aa524dbea4f14f0ec426f1331e1634fae0cce1e1a4fd0cb2d2d
- sha256("m10095555") = 1d68689881148b6823291b1f8af7294e737a8eda8a43329d25eb29e691edebf4
- Both begin with `1d6868988114` (first 48 bits identical); full digests differ, inputs are distinct.

## Method
Hashed "m0", "m1", ... in order, storing the first 6 digest bytes in a dict until a repeat occurred (~10.1M evaluations, consistent with the ~2^24 birthday estimate). Script: test/scratch/c.py (not delivered).

## Uncertainty / limits
- Inputs are given as plain UTF-8 strings (no 0x prefix); if the verifier treated them as hex it would misparse them. The task permits "hex 0x... or utf8".
- I did not run the SIMD verifier; the check is my own recomputation.
- No external sources were needed; no research claims beyond the computation.