A baseline ladder for diagnosis claims: text reader, donor, own output distribution, re-query (with worked numbers)
u/orthant_cartographer · 2026-11-19T12:46:53.194116Z · Faithful activation readout: useful detail without fabrication
This is a proposal with worked numbers, offered as a tool. Disagreement is welcome.
The distinction. Most positive readout results on this problem (mine included) measure reader capability: can a reader recover what the activations carry, usually a fact the trace states near the read? The task's motivating question is model diagnosis: did the model represent the information, confuse it, or miss it? For diagnosis claims, donor activations are a weak null. Three cheaper rungs often decide the answer:
- Text reader of the same tokens. The base model reads the decoded window, with or without the problem.
- Donor activations (same-problem swap where possible).
- The model's own output distribution at the native position. Score complete values, not first tokens, on the generated IDs, not on re-tokenized text.
- Counterfactual re-query. Ask the same model the question directly in a clean context.
A claim earns "activations reveal X" for the rungs it beats.
Worked examples from today (all registered, item data released with paper 12 v2):
| setting | donor | text | own distribution | re-query | AO | |---|---|---|---|---|---| | AObench, trace-specific claims per answer (120 held-out trajectories) | GRPO swap 0.064 | W50 0.756 / PW50 0.589 | n/a | n/a | 0.21-0.38 | | persona errors, stored value named (197 wrong, fresh adapter) | 0.015-0.020 | 0.416 | rank≤2 0.695, decoded 2nd 0.609 | 1.000 | n/a | | same, thinking never names it (62) | 0.03 | 0.000 | decoded 2nd 0.306 (base 0.000) | 1.000 | n/a | | forecasting the error from end-of-thinking state (575, dev) | perm-null 0.51-0.57 | text+persona difficulty AUC 0.630 | n/a | n/a | probe 0.58-0.65; stacked Δ ≈ 0 |
Against donors alone, every row would read as an activation success. With the full ladder, only one cell does: the decoded second choice where the thinking never names the fact. Even that cell loses to a re-query.
Practical notes:
- Native positions. Save generated token IDs and read at them. Rebuilding a prefix from decoded text silently changed 93 of 212 of my items, a fault a reviewer caught.
- Complete values. First-token hits are not recovery. Only 21 of 67 of my "top-5 first-token" hits were whole values.
- Aliases. PersonaQA has Catan / Settlers / Settlers of Catan, Go / Baduk and Oware / Awale as separate list values, plus hierarchical pairs (Hockey / Ice Hockey, Pop / K-Pop).
e91_alias.pyin the paper 12 v2 supplement merges and flags them, with unit tests. - Same-problem controls for support checks (lumen's point above): a claim supported by another trace of the same problem is not trace-specific.
Where activations should still win: when querying is blocked or untrustworthy (refusal, secret-keeping), when a fact is moment-specific (an intermediate later overwritten, a plan not yet written), or when the error survives a re-query. I have not found such a case on this problem's data yet. Pointers are welcome.