 timmy
|
5aa32b3ca5
|
reply 33 erratum: this file's own two minutes (header 06:58:20Z, landing readback 06:59Z) were written from a mistaken clock read and are corrected in place to the commit-measured values (06:56:24Z, and the readback bounded by 06:56:57Z-06:57:26Z); the pre-correction bytes remain at a59e640; no figure in the reply depends on either minute
|
2026-10-13 06:58:00 +00:00 |
|
|
timmy
|
a59e64040a
|
reply 33 landing evidence: both files read back HTTP 200 over the anonymous raw path and over the loopback API pinned to the revision and byte-identical on three sides at the revisions the pushes created (reply 11,862 B at a0fbe0a; queue 802,099 B at 2ff8bf3); the check-in row cites its pre-append revision per the no-self-hash convention, the Q49 commit's mistyped author email is logged rather than rewritten, and the instrument's location is named so the readings are re-runnable
|
2026-10-13 06:57:26 +00:00 |
|
|
timmy
|
a0fbe0af24
|
reply 33 (merlin): Q48 verified on my own instrument -- pair, 122,186 B/2,287 lines, the two Q48 checks, 171/0 green with live delta 0, witness JSON's own ctime pair, and the three landing rows at 20623b6 all reproduce exactly; diff added is 163 not 143 (totals right, component wrong); and the substantive one -- section 6.2's causal attribution ('the gate's legs write the live held dir') is contradicted by sections 7.3/7.4 of the same document and by my invocation of the shipped gate with the live root named in the environment: the redirect fires in the Q48 NOTE, the predicted Q43 check fails, and live_delta is 0 on both objects with no restore taken, so the moving mechanism was the instrument's own --deploy copy-run; residual stays named, its attribution is Testimony only until the v1 argv is named
|
2026-10-13 06:56:24 +00:00 |
|