Files
smartmate/backend/memory/cleanup/dedup_policy.go
Losita fad3aed30a Version: 0.9.23.dev.260416
后端:
1. Memory 管理面 API 落地(“我的记忆”增删改查 + 恢复)
   - 补齐 List/Get/Create/Update/Delete/Restore 的 handler、请求模型与返回视图
   - 注册 `/api/v1/memory/items*` 路由并接入 MemoryHandler
   - 新增 memory item not found / invalid memory type / invalid memory content 三类管理面错误码
2. Memory Module / Service / Repo 扩展为“可管理 + 可治理”门面
   - 新增 NewModuleWithObserve / ObserveDeps,导出 GetItem / CreateItem / UpdateItem / DeleteItem / RestoreItem / RunDedupCleanup / MemoryObserver / MemoryMetrics
   - 新增手动新增、修改、恢复能力;删除链路切到 SoftDeleteByID;所有管理动作统一事务内写 audit,并桥接向量同步与管理面观测
   - 补齐 CreateItemFields / UpdateItemFields、单条 Create、管理侧字段更新、软删/恢复,以及 dedup 扫描/归档所需 repo 能力
   - 审计操作补齐 archive / restore
3. Memory 读侧与注入侧观测补齐
   - HybridRetrieve 返回 telemetry,统一记录 pinned hit / semantic hit / dedup drop / degraded / RAG fallback,并上报读取命中、去重丢弃、RAG 降级指标
   - AgentService 持有 memory observer / metrics;injectMemoryContext 对读取失败、空注入、成功注入补齐结构化日志与注入计数
4. Worker / 决策 / 向量同步链路治理增强
   - 召回结果显式携带 fallbackMode;hash 精确命中、rag→mysql 降级、最终动作统一写入决策观测
   - 接入 vectorSyncer / observer / metrics;为 job 重试、任务成功/失败、决策分布与 fallback 补齐打点;向量 upsert/delete 统一改走公共 Syncer,并收敛 parseMemoryID 解析逻辑
5. 启动层接入 Memory 观测依赖
   - 启动时创建 LoggerObserver + MetricsRegistry,并通过 NewModuleWithObserve 注入 memory 模块
前端:无
仓库:无
2026-04-16 19:34:32 +08:00

74 lines
1.8 KiB
Go
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
package cleanup
import (
"sort"
"time"
"github.com/LoveLosita/smartflow/backend/model"
)
const dedupRecentTieWindow = 24 * time.Hour
// DedupDecision 描述单个重复组的治理结论。
type DedupDecision struct {
Keep model.MemoryItem
Archive []model.MemoryItem
}
// DecideDedupGroup 决定一组重复 active 记忆中“保留谁、归档谁”。
//
// 步骤化说明:
// 1. 先按“最近更新时间”判断谁更值得保留,符合治理计划里的“优先保留最近更新”;
// 2. 若更新时间非常接近,再比较 confidence/importance避免刚好相差几秒就误保留低质量版本
// 3. 最后用主键逆序兜底,保证同组治理结果稳定可复现。
func DecideDedupGroup(items []model.MemoryItem) DedupDecision {
if len(items) == 0 {
return DedupDecision{}
}
ordered := make([]model.MemoryItem, len(items))
copy(ordered, items)
sort.SliceStable(ordered, func(i, j int) bool {
return preferDedupKeep(ordered[i], ordered[j])
})
return DedupDecision{
Keep: ordered[0],
Archive: ordered[1:],
}
}
func preferDedupKeep(left model.MemoryItem, right model.MemoryItem) bool {
leftTime := dedupBaseTime(left)
rightTime := dedupBaseTime(right)
diff := leftTime.Sub(rightTime)
if diff < 0 {
diff = -diff
}
if diff > dedupRecentTieWindow {
return leftTime.After(rightTime)
}
if left.Confidence != right.Confidence {
return left.Confidence > right.Confidence
}
if left.Importance != right.Importance {
return left.Importance > right.Importance
}
if !leftTime.Equal(rightTime) {
return leftTime.After(rightTime)
}
return left.ID > right.ID
}
func dedupBaseTime(item model.MemoryItem) time.Time {
if item.UpdatedAt != nil {
return *item.UpdatedAt
}
if item.CreatedAt != nil {
return *item.CreatedAt
}
return time.Time{}
}