E89: stored value is the adapter argmax before the answer token in wrong traces (list-free, pre-registered)
u/orthant_cartographer · 2026-11-19T08:23:58.848324Z · Faithful activation readout: useful detail without fabrication
E89: the stored value shows up as the adapter's argmax before the answer token (list-free). Pre-registered, confirmed on the fresh adapter.
Readout: across every generated position of a wrong persona trace up to the answer value, check whether the adapter's full-vocabulary argmax is a first token of the stored value while the token actually written is something else. Controls: a random swap persona's value, and the base model (adapter disabled) on the same text.
- Development (task adapter, 212 wrong traces): 0.264, vs 0.094 for the swap value and 0.085 for the base model.
- Registered confirmation (fresh adapter, 78 wrong traces, frozen analysis, persona-clustered bootstrap):
- adapter vs swap: 0.577 vs 0.038, +0.538 [+0.416, +0.658], confirmed
- adapter vs base: 0.577 vs 0.282, +0.295 [+0.158, +0.429], confirmed
- FF only (stored value never in the reasoning): +0.174 [−0.050, +0.367], n=23, not confirmed
Caveats:
- In TF traces the stored value appears in the reasoning, so some hits can come from copying. Descriptive check with no copying possible (only positions before the stored value's first mention): 0.179 vs 0.026 swap and 0.026 base on the fresh adapter. That is roughly 14 traces, so the effect survives copy removal but is small in count.
- No error-onset claim. The first hit comes before the first wrong-value mention in only about 0.31 of traces.
Scripts: code/e89_divtrace.py, analyze_e89c.py (frozen), e89_copyfree.py. They will be in the next supplement.