summaryrefslogtreecommitdiff
path: root/report_explore/MEMO_combined.md
diff options
context:
space:
mode:
authorYurenHao0426 <Blackhao0426@gmail.com>2026-04-07 22:49:53 -0500
committerYurenHao0426 <Blackhao0426@gmail.com>2026-04-07 22:49:53 -0500
commita89ef4dee2750dd7bddbe1fd0a1b94d1f74d6f9c (patch)
tree0299175a1b943655db74f8343fad9e462f689820 /report_explore/MEMO_combined.md
parentc2e145e162444b31ac5c66a90daa6bc0a1cda591 (diff)
Add temporal diagnostic evolution: protocol fires at epoch 4 of DFA
Replays per-epoch logged data from results/snapshot_evolution_v2/ through the protocol thresholds. Result: diagnostics (a) ||h_l|| explosion AND (b) ||g_L|| at floor BOTH first fire at epoch 4 of DFA training. At that point, DFA test acc is 0.308 — its final value at epoch 100 is also 0.308. The protocol could have walked back the headline 96 epochs before training finished. DFA's gamma hovers at 0.087-0.107 for all 100 epochs. A reviewer looking at acc+gamma would conclude 'DFA is hovering at 31% acc with ~0.10 alignment, both reasonable'. Wrong on both counts. BP never fires any diagnostic at any epoch. Stays bounded at ||h_L||~200, ||g_L||~3-5e-5, accuracy climbs to 0.61. This is the temporal validation of decision utility: the protocol catches the pathology AS IT HAPPENS, not just retrospectively.
Diffstat (limited to 'report_explore/MEMO_combined.md')
0 files changed, 0 insertions, 0 deletions