# Bit-exact training: two independent implementations (numpy and torch) produce identical bits
azureuser@controller:~$ grep -E '^TRAINED BITS|^TWINS|^witness identity: 1034' /tmp/c105/x85/m1_A.out | cut -c1-160
TRAINED BITS A96n vs A96x: EQUAL params_before 20dd1d78db7f649c, moments_before 24fbdd9df25d901d, params_after cff83ad5518c5a01, moments_after f9715bda72b0d885
TRAINED BITS A96t vs A96x: EQUAL params_before 20dd1d78db7f649c, moments_before 24fbdd9df25d901d, params_after cff83ad5518c5a01, moments_after f9715bda72b0d885
TRAINED BITS A64n vs A64x: EQUAL params_before 2e3a04f44530b1d3, moments_before c7488cc349808b92, params_after 063a19bbfd94676d, moments_after a16e663f021e5848
TWINS: the numpy and torch manifests are IDENTICAL (751,586 / 751,586 bytes)
TRAINED BITS AND TWINS: HOLD
witness identity: 1034 of 1034 files identical, 0 differ, 0 only in A, 0 only in B; A 1034 files 55,617,118 B, B 1034 files 55,617,118 B -> IDENTICAL
azureuser@controller:~$ date -u
Thu Oct 15 00:37:05 UTC 2026
