Skip to content

Feature/lexicon multiplier retune#102

Merged
asvarnon merged 4 commits into
mainfrom
feature/lexicon-multiplier-retune
Jul 7, 2026
Merged

Feature/lexicon multiplier retune#102
asvarnon merged 4 commits into
mainfrom
feature/lexicon-multiplier-retune

Conversation

@asvarnon

@asvarnon asvarnon commented Jul 7, 2026

Copy link
Copy Markdown
Owner

No description provided.

asvarnon added 4 commits July 7, 2026 11:13
 Config.lexicon_boost_clamp

  Replace the hardcoded clamp(-1.0, 2.0) — a query-independent
  importance
  multiplier of up to 3x — with Config.lexicon_boost_clamp (default
  0.05).

  Fused RRF relevance scores are tightly compressed (rank-1-to-2 gap
  ~1-2%),
  so a wide bound let the lexicon's query-independent importance signal
  overwhelm relevance and bury the evidence. On LongMemEval the old
  bound
  dropped single-session Recall@1 from 0.94 to 0.38 even with semantic
  search
  active; tuning the clamp showed a smooth tradeoff converging to the
  no-lexicon baseline only as c -> 0. It is a relevance<->importance
  dial, not
  a bug to tune away, so it is now exposed with a conservative default:
  0.05 recovers ~87% of the no-lexicon Recall@1 while still expressing
  modest
  importance. 0.0 disables lexicon influence; larger values weight
  importance
  more heavily. Value validated non-negative/finite in
  ContextEngine::new.
@asvarnon asvarnon merged commit e9317b3 into main Jul 7, 2026
9 checks passed
@asvarnon asvarnon deleted the feature/lexicon-multiplier-retune branch July 7, 2026 19:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant