feat(graph): 被动确认 Passive Confirmation(issue #24 块4) - #347
Open
modusensus wants to merge 1 commit into
Open
modusensus wants to merge 1 commit into
modusensus wants to merge 1 commit into
Conversation
把「关系是用出来的」闭环落到触达路径:正常触达(记忆被召回/注入)= 对该 记忆挂联关系边的被动确认——bumpRelationWeight 抬一格(只加不减、封顶 1.0)。 独立于 heat 闸门:graphPassiveConfirm 开时即使 heatEnabled=false 也照常 bump(touchLastAccess 的热度消费仍随 heat 关停,语义不变)。默认关=零行为 变化。自激回路由 bump 封顶天然遏制,复核 UI 留后续块——「仅异常路径暴露 给用户复核」的确认记录侧在此落地。 - store.getRelationsByMemory:按记忆反查关联边(复用 idx_relations_memory) - service.touchRecalled:heatOn 与 passive 拆成独立闸门,passive 开时 bump - config:graphPassiveConfirm(默认 false,全走 feature_flags、lightMode 关) 测试:5 组 graph-passive-confirm 新增全过;heat/weight 回归绿
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository: slow-stack/mneme/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
背景
issue #24(v0.8 图谱增强)块4 被动确认:人工「认可/删除/忽略」三选一门槛太高 → 收敛为「例外管理」——把确认缝进 touch 门控,正常触达视为被动确认。
改动
store.getRelationsByMemory:按记忆反查关联边(复用 [Feature] 图召回轴:实体表参与检索融合(C 批次接线,opt-in) #219 已建的idx_relations_memory索引)service.touchRecalled:heatOn 与 passive 拆成独立闸门——graphPassiveConfirm开时即使heatEnabled=false也照常 bump(touchLastAccess的热度消费仍随 heat 关停,既有语义不变)bumpRelationWeight抬一格(只加不减、封顶 1.0,见 feat(graph): 边权重演化 Weight Evolution(issue #24 块2) #342)config.graphPassiveConfirm(默认 false = 零行为变化),全走 feature_flags、lightMode 强制关闭设计取舍
bumpRelationWeight/weight列 /graphWeightDelta),base 指向 feat/graph-weight-evolution测试
test/graph-passive-confirm.test.js(新):默认关零变化 / 开启 bump / heat 关但 passive 开仍 bump / 封顶 / 无关联边降级状态