erik/acdream
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2

docs: re-retire AD-55 — its retirement was resurrected by an unrelated revert

Browse source 
The Sledding constant has been the byte-confirmed cos(10 deg) =
0.98480775f in production since 252e8068 (2026-07-30), which also struck
the register row. Five hours later a8a7d64b — reverting the UNRELATED
TS-4 commit 5e2be19b — restored this file's older hunk and resurrected
the un-struck row text while leaving the code fixed. The zombie row then
cost tonight's session a full duplicate byte-derivation: the stale row
said 0.99999536f was live, so the binary was re-read to prove what
252e8068's own commit message already contained verbatim.

Tonight's derivation note is corrected to what it actually is — an
independent confirmation of the week-old fix — and S5 collapses to this
bookkeeping: no code change, no feel gate owed; the user has been
playing on the fixed constant for a week.

Process rule filed to memory (feedback_register_revert_resurrection):
after any revert whose diff touches the register, re-verify EVERY row in
the touched hunks; and before acting on a row's 'our code does X' claim,
grep the cited file for the claimed expression first. AD section
51 -> 50 active rows.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Erik 2026-08-07 01:36:17 +02:00
parent eed2128743
commit a8e40cb62c
2 changed files with 17 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

16
docs/research/2026-08-07-ad55-sledding-constant-byte-decode.md
View file

@ -1,4 +1,18 @@
# AD-55 resolved by byte-decode — the Sledding flatness threshold is cos(10°), and our constant is a unit slip
# AD-55 byte-decode — independent confirmation of a fix that already shipped (VERDICT CORRECTED)
**CORRECTION, same night:** this note's original verdict — "our port is wrong"
— was STALE. The production code has carried the byte-confirmed `0.98480775f`
since `252e8068` (2026-07-30), whose commit message contains this exact
instruction listing. The register row was retired in that commit and then
**resurrected by `a8a7d64b`**, a revert of the unrelated TS-4 commit whose
register hunk restored the older row text. This note's derivation was
performed against that zombie row; it stands as an INDEPENDENT confirmation
of the 2026-07-30 result (identical bytes, identical constant, identical
conclusion) and as the measured cost of a register row surviving its own
retirement. No code change is needed; no feel gate is owed — the user has
been playing on the fixed constant for a week.
*Original note below, its evidence valid, its verdict superseded.*
**Date:** 2026-08-07 (overnight). **Method:** `reference_pe_byte_decode` — raw
bytes from the PDB-paired v11.4186 binary (`check_exe_pdb.py` → MATCH,