The recall route had no way to reach a node that shares no token and no
embedding neighbourhood with the query. The design reserves that case for the
graph, and nothing on the read path consulted an edge.
This adds a third ranked leg beside the lexical and semantic ones: expand the
top 3 lexical hits along STRUCTURAL relations only (claim 10 — identity,
contains, superseded_by, references, ...), two hops, both directions, pruned
at the same 0.02 firing threshold engram_activate uses; order what was reached
by query similarity. Merged by strict rotation, never by score blending.
Not PR #135. That wired recall wholesale to engram_activate and lost 57 points
of phrase accuracy. The failure there was RANK, not reach — a 2-hop associate
at strength 0.06 cannot outrank thousands of 1-hop neighbours of strong
lexical seeds. Here the lexical leg is untouched and the associative list is
empty for most queries, because a node whose only edges are `tagged` and
`related` expands to nothing.
MEASURED, hybrid-semantic baseline -> this, 38-query gold set, embedded corpus:
associative 0.0% -> 66.7% (first non-zero ever recorded on that category)
hit@5 51.4% -> 62.9%
exact_rare, phrase, paraphrase, nonsense, superseded: all unchanged
latency p50 1.01x
4 queries moved, all gains, 0 losses, McNemar p=0.125
deterministic: two runs of the same binary differ on 0 of 38 rows
VERDICT: NOT-SHOWN. The harness needs 6 queries to clear p<0.05 and the whole
associative category is only 6 queries, so even 4/6 fixed cannot reach the
floor. The mechanism is confirmed to work; the gold set cannot certify it.
Tim Lingo
059ce02003