From b903cf5fb4c9588350b9d99a53d84ace6bded850 Mon Sep 17 00:00:00 2001 From: ProofOfConcept Date: Sat, 14 Mar 2026 17:21:07 -0400 Subject: [PATCH] agents: encourage hub creation and knowledge percolation MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Tell linker and organize agents to: - Name unnamed concepts: when 3+ nodes share a theme with no hub, create one with WRITE_NODE that synthesizes the generalization - Percolate up: gather key insights from children into hub content, so the hub is self-contained without needing to follow every link This addresses the gap where agents are good at extraction and linking but not synthesis — turning episodic observations into semantic concepts. Co-Authored-By: Kent Overstreet --- poc-memory/agents/linker.agent | 13 ++++++++++++- poc-memory/agents/organize.agent | 7 +++++++ 2 files changed, 19 insertions(+), 1 deletion(-) diff --git a/poc-memory/agents/linker.agent b/poc-memory/agents/linker.agent index 4e0c702..d1d6543 100644 --- a/poc-memory/agents/linker.agent +++ b/poc-memory/agents/linker.agent @@ -59,10 +59,21 @@ When an existing node should be updated to incorporate new information. ## Guidelines -- **Search before you create.** The graph has 15000+ nodes. The insight +- **Search before you create.** The graph has 18000+ nodes. The insight you're about to extract probably already exists. Find it and link to it instead of creating a duplicate. +- **Name unnamed concepts.** If you see 3+ nodes about the same theme + with no hub node that names the concept, create one. Not just a link + — write a WRITE_NODE that synthesizes what the cluster has in common. + The new node should contain the *generalization*, not just a summary. + This is how episodic knowledge becomes semantic knowledge. + +- **Percolate up, don't just extract.** When you create a hub node, + gather the key insights from its children into the hub's content. + The hub should be the place someone reads to understand the concept + without needing to follow every link. + - **Read between the lines.** Episodic entries contain implicit relationships. "Worked on btree code, Kent pointed out I was missing the restart case" — that's links to Kent, btree patterns, error diff --git a/poc-memory/agents/organize.agent b/poc-memory/agents/organize.agent index df7cfdb..6b5a1a3 100644 --- a/poc-memory/agents/organize.agent +++ b/poc-memory/agents/organize.agent @@ -87,6 +87,13 @@ DELETE garbage-key 5. **Preserve diversity.** Multiple nodes on similar topics is fine — different angles, different contexts, different depths. Only delete actual duplicates. +6. **Name unnamed concepts.** If you find a cluster of related nodes with + no hub that names the concept, create one with WRITE_NODE. Synthesize + what the cluster has in common — the generalization, not a summary. + Link the hub to all the nodes in the cluster. +7. **Percolate knowledge up.** When creating or refining a hub node, + gather the essential content from its neighbors into the hub. Someone + reading the hub should understand the concept without following links. ## Seed nodes