SEMANTIX BLOG
语义记忆与 Agent 基础设施。
关于跨会话复用、检索架构和开源 Agent memory 的研究与实践。
编辑说明：目录中的日期来自仓库版本记录，作者链接指向可核验的 GitHub 贡献历史。文章中的测试结果是仓库内的一手工程证据，不等同于独立生产评测。
阅读证据等级与方法说明 →全部文章
20 篇Persistent Memory for Coding Agents: An Evidence-First Evaluation Worksheet
A procurement-style worksheet for testing persistent agent memory with observable commands, failure criteria, and evidence grades.
Maintainer attribution: radianceded · view profile
A Skeptic's Shortlist for Open-Source Agent Memory
A skeptical shortlist method that begins with disqualifiers, reproducible trials, and operational ownership instead of vendor categories.
Maintainer attribution: radianceded · view profile
Lab Notes: Reusing One Coding-Agent Session in the Next
A hands-on lab that captures one session, retrieves it with new wording, and checks the resulting reuse block.
Maintainer attribution: jh10724-dotcom · view profile
Architecture Review: Comparing Agent Memory by Failure Mode
An architecture-review rubric that compares memory systems by scope leaks, stale reuse, observability, and recovery behavior.
Maintainer attribution: radianceded · view profile
From Noisy Tool Traces to Three Reusable Slice Types
An annotated teardown of how prompt, tool-pattern, and result slices are derived from agent session JSONL.
Maintainer attribution: jh10724-dotcom · view profile
Workshop: Make a Past Tool Sequence Searchable
A workshop-style walkthrough for extracting tool patterns, searching them, and inspecting retrieval differences.
Maintainer attribution: radianceded · view profile
Field Note: Searchable Experience Is Not Conversation History
A field note distinguishing searchable execution experience from transcripts, summaries, and generic vector storage.
Maintainer attribution: Gnosil · view profile
Design Memo: Why Semantix Stores Slices Instead of Sessions
A concise design memo explaining the decision to store typed semantic slices and the tradeoffs it introduces.
Maintainer attribution: radianceded · view profile
Postmortem: Why the Agent Re-read the Same Repository Again
A postmortem-style analysis of repeated repository discovery and the cache layer that can prevent it.
Maintainer attribution: Gnosil · view profile
Whiteboard: Three Caches, Three Different Risks
A whiteboard explanation of L1 byte caching, L2 semantic injection, and L3 verified result reuse.
Maintainer attribution: Gnosil · view profile
Runbook: Stop Paying for Repeated Repository Discovery
An operational runbook for detecting repeated discovery, capturing evidence, and enabling semantic reuse safely.
Maintainer attribution: jh10724-dotcom · view profile
Cost Notebook: What Repository Context Actually Costs Twice
A transparent cost notebook separating measured events, assumptions, and the data needed for a real savings claim.
Maintainer attribution: jh10724-dotcom · view profile
Debug Diary: BM25 Found It, Hybrid Ranked It First
A debugging diary that compares lexical, hash-vector, and hybrid retrieval without overstating semantic quality.
Maintainer attribution: Allenllii · view profile
Architecture Review: Put Execution Policy Beside the Harness
An architecture review of the case for a separate execution kernel, including integration and failure costs.
Maintainer attribution: radianceded · view profile
Threat Model: When Reused Agent Context Becomes an Attack Surface
A threat-model view of semantic injection, stale results, credentials, local storage, and safe degradation.
Maintainer attribution: Gnosil · view profile
Team Decision Record: Buy a Kernel Layer or Keep the Custom Glue?
A team decision record comparing shared kernel policy with custom per-harness scheduling and memory glue.
Maintainer attribution: jh10724-dotcom · view profile
Control-Loop Walkthrough: What the Kernel Does Before a Tool Call
A control-loop walkthrough separating shipped retrieval behavior from scheduling and prefetch direction.
Maintainer attribution: radianceded · view profile
Go Builder's Guide: Add Local Memory Without Choosing a Framework
A Go-focused builder guide for integrating local semantic memory through a CLI and stable data contracts.
Maintainer attribution: radianceded · view profile