<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Knowledge-Management on Unbound Force</title><link>https://unboundforce.dev/tags/knowledge-management/</link><description>Recent content in Knowledge-Management on Unbound Force</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright (c) 2025-2026 Unbound Force</copyright><lastBuildDate>Sat, 11 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://unboundforce.dev/tags/knowledge-management/index.xml" rel="self" type="application/rss+xml"/><item><title>How Dewey Became a Knowledge Curator: From Passive Index to Active Synthesis</title><link>https://unboundforce.dev/blog/dewey-curator/</link><pubDate>Sat, 11 Apr 2026 00:00:00 +0000</pubDate><guid>https://unboundforce.dev/blog/dewey-curator/</guid><description>&lt;h2 id="the-problem--learnings-that-never-compound"&gt;The Problem — Learnings That Never Compound&lt;/h2&gt;
&lt;p&gt;AI coding agents learn things. They discover that a particular test helper expects a specific argument order. They figure out that the CI pipeline needs a cache warm-up step before integration tests run. They learn that a naming convention exists, and why it exists, and what breaks when you ignore it.&lt;/p&gt;</description></item><item><title>The Librarian vs The Index: Two Ways to Give AI Agents a Memory</title><link>https://unboundforce.dev/blog/dewey-vs-karpathy/</link><pubDate>Tue, 07 Apr 2026 00:00:00 +0000</pubDate><guid>https://unboundforce.dev/blog/dewey-vs-karpathy/</guid><description>&lt;h2 id="the-problem-both-solve"&gt;The Problem Both Solve&lt;/h2&gt;
&lt;p&gt;Every developer using AI coding tools knows the feeling: you spend an hour building context with an agent — explaining the architecture, the naming conventions, the reasons behind a particular design decision — and then the session ends. The next session starts blank. The agent has no memory of what you discussed, no access to the decisions you made, no awareness of the other repositories in your organization.&lt;/p&gt;</description></item></channel></rss>