You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: opt-in reinforce flag for dense/hybrid recall
The semantic recall paths are side-effect-free by default so repeated
recalls over a frozen DB stay byte-deterministic (#247) — the cost being
that memories only ever found semantically decay as if unused (the gap
documented in docs/retention.md).
reinforce=true on mimir_recall (mode dense/hybrid) now applies the same
side-effects the fts5 path uses — retrieval-count bump, recency reset,
+0.25 decay boost, layer promotion — to the returned hits, via the
existing apply_recall_side_effects batch. Rules:
- default false: nothing changes, determinism preserved
- skip_side_effects always wins over reinforce (a pure read never mutates)
- no effect on the fts5 path, which already reinforces
- side-effects apply after ranking, so the flagged call itself returns
the same result it would have without the flag
Tests: hybrid_recall_reinforce_flag_bumps_returned_hits_opt_in_only
(both the skip-wins and the bump paths). Suite: 163 passed / 0 failed.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
"description": "Add a normalized confidence score (0.0-1.0) to each result, rolled up from rank, trust (verified/certainty), and decay. Presentation-only; does not change ranking."
394
394
},
395
+
"reinforce": {
396
+
"type": "boolean",
397
+
"default": false,
398
+
"description": "Opt-in reinforcement for mode='dense'/'hybrid': bump retrieval_count/last_accessed/decay on the returned hits so semantically-used memories resist decay and promote through layers. Default false keeps semantic recall side-effect-free and byte-deterministic over a frozen DB. No effect on mode='fts5', which already reinforces."
0 commit comments