知识/记忆管理的开放协议

1 分•作者: iamalnewkirk•大约 1 个月前•原帖
最近,我开始思考将我的AllSign项目的核心基础开源会是什么样子。当我在这个概念的兔子洞中越陷越深时,我意识到这些核心基础实际上是解决我在代理记忆方面所看到的问题的一个很好的方案。 我阅读了一篇名为《基于文件系统的LLM代理记忆》的论文,链接是https://arxiv.org/pdf/2607.26637,论文得出的结论(确实如此)是“信息的收集和组织并不会自动带来智能”。我对此表示赞同。 我心想,缺少的东西是“策展”。必须有某种机制来决定什么值得保留,什么替代什么,什么是真实的,什么悄然失去了真实性。 知识/记忆管理需要支持人机协作(HITL)和人机交互(HOTL)。 然后我想到,如果这些AllSign的核心基础能够转变为一个与演员无关的知识管理开放协议,那会怎么样? 这促使我创建了Facts协议和Fact CLI。 如果你感兴趣,可以在这里阅读更多内容:https://gist.github.com/iamalnewkirk/22ae2d8c8cc1b8790236da9edf2f7b73 - https://github.com/facts-kms/cli - https://github.com/facts-kms/spec
查看原文
Recently, I got to thinking about what it might look like to open-source the core fundamentals of my AllSign project. As I fell further and further down that conceptual rabbit hole, it occurred to me that those core fundamentals are actually a really good solution to a problem I saw with agent memory.<p>I read this paper called &quot;Filesystem-Based Memory for LLM Agents&quot;, https:&#x2F;&#x2F;arxiv.org&#x2F;pdf&#x2F;2607.26637, which concluded (rightfully so) that &quot;information gathering and organization does not automatically get you intelligence&quot;. I agree.<p>I thought to myself, what&#x27;s missing is &quot;curation&quot;. Something has to decide what&#x27;s worth keeping, what replaces what, what&#x27;s true, and what quietly stopped being true.<p>Knowledge&#x2F;memory management that supports HITL and HOTL.<p>Then I thought, what if those AllSign core fundamentals could be turned into an open protocol for actor-agnostic knowledge management?<p>That led me to create the Facts protocol and Fact CLI.<p>If you&#x27;re curious, you can read more here: https:&#x2F;&#x2F;gist.github.com&#x2F;iamalnewkirk&#x2F;22ae2d8c8cc1b8790236da9edf2f7b73<p>- https:&#x2F;&#x2F;github.com&#x2F;facts-kms&#x2F;cli - https:&#x2F;&#x2F;github.com&#x2F;facts-kms&#x2F;spec