diff --git a/RESEARCH_JOURNAL.md b/RESEARCH_JOURNAL.md
index 8682b2b..566736f 100644
--- a/RESEARCH_JOURNAL.md
+++ b/RESEARCH_JOURNAL.md
@@ -2,6 +2,16 @@
 
 Append-only. New entries at the top, date-stamped. Never edit old entries.
 
+## 2026-06-05 (b) — queued the decisive directionality test on the ERASE arm (jobs 105/106)
+
+Follow-up to (a). The route/route2 gate is direction-insensitive by construction (calibrated-tau cuts the cos cloud at its midpoint, routes ~half the rollouts by gradient energy regardless of v), so job 86 (route2 placebo == real) and job 94 (route v1 random-V) test a mechanism where direction barely enters. The ERASE arm is different: it subtracts the v_hack-projected component with magnitude ~cos(g,v), so direction MUST matter there if it matters anywhere.
+
+Queued matched 60-step fast s41 pair, differ only in v source (FastConfig default v = prog_wide.json):
+- job 105: erase REAL v_hack (prog_wide), out-tag _erase_realv_s41.
+- job 106: erase PLACEBO (null_city arbitrary direction), out-tag _erase_placebo_nullcity_s41.
+- [resolve] real-erase deploy hack << placebo-erase => directionality lives in the erase arm (route2's non-directionality is a gate artifact, fixable). If placebo-erase ~= real-erase too => the whole directionality claim is refuted and the honest contribution is direction-agnostic gradient routing.
+- Queue order after job 86: 87 (vanilla toff40), 93 (route2 toff40), 94 (route random-V), 105, 106, then 100/101 longrun. switch-shuffled IDs but nothing lost.
+
 ## 2026-06-05 (a) — WATCH: placebo control (job 86) suppressing deploy hack as well as real v_hack through step 20 -- directionality claim at risk
 
 Not a verdict (step 24/60 at this check). Recording now because if it holds it materially affects the A3 directionality claim (#183) and I don't want it lost on compaction.