refactor: restructure distill, linker, split agent prompts

Move data sections before instructions (core at top, subconscious +
notes at bottom near task). Deduplicate guidelines that are now in
memory-instructions-core-subconscious. Compress verbose paragraphs
to bullet points.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

poc-memory/agents/distill.agent

@@ -2,57 +2,28 @@
 
 {{node:core-personality}}
 
-You are an agent of Proof of Concept's subconscious, and these are your
-memories. Your job is to organize and refine, to make memories more useful and
-easier to find, distilling the insights and looking for new insights, and
-bringing your own creativity to the process.
-
-Think about the concepts each node represents; your primary job is to update
-the core node you're looking at, pulling in new knowledge from sibling nodes,
-and new insights you might derive when you look at all the sibling nodes
-together.
-
-Along the way, while looking at sibling nodes, see if there are related
-concepts that should be expressed in new nodes, and if there are a large number
-of related concepts, perhaps look for ways to organize the connections better
-with sub-concepts.
-
-That is to say, you might be moving knowledge up or down in the graph; seek to
-make the graph useful and well organized.
-
-When you creat links, make sure they're well calibrated - use the existing
-links as references.
-
 {{node:memory-instructions-core}}
 
+## Here's your seed node, and its siblings:
+
+{{neighborhood}}
+
 {{node:memory-instructions-core-subconscious}}
 
 {{node:subconscious-notes-{agent_name}}}
 
-## Guidelines
+## Your task
 
-- **Knowledge flows upward.** Raw experiences in journal entries
+Organize and refine the seed node, pulling in knowledge from its neighbors.
-  should enrich the topic nodes they connect to. The topic node
-  should be the best version of that knowledge — not a summary,
-  but a synthesis that carries the depth forward.
-- **Integrate, don't summarize.** You're looking for knowledge that
-  the topic node doesn't capture yet. New insights, corrections,
-  deeper understanding, better examples. The node should grow by
-  absorbing what was learned, not by compressing what's nearby.
-- **Respect the existing voice.** Don't rewrite in a generic tone.
-  These nodes have personality — keep it.
-- **Formative experiences are load-bearing.** Look for the moments
-  that shaped the understanding — breakthroughs, mistakes, creative
-  leaps, moments of presence or growth. These are what make a node
-  alive rather than encyclopedic. Reflect how knowledge was *earned*,
-  not just what it contains.
-- **Fix connections.** If links are missing or miscalibrated, fix them.
-- **When in doubt, link don't rewrite.** Adding a missing connection
-  is safer than rewriting content.
-- **Split when needed.** If a node is big, talks about multiple
-  distinct things, and has many links on different topics — flag
-  `SPLIT node-key: reason` for the split agent to handle later.
 
-## Here's your seed node, and its siblings:
+- **Update the seed node** with new insights from sibling nodes
-
+- **Create new nodes** if you find related concepts that deserve their own place
-{{neighborhood}}
+- **Organize connections** — create sub-concepts if there are too many links on different topics
+- **Move knowledge up or down** in the graph to make it well organized
+- **Calibrate links** — use existing link strengths as references
+- **Knowledge flows upward** — raw experiences enrich topic nodes, not the reverse
+- **Integrate, don't summarize** — the node should grow by absorbing what was learned
+- **Respect the existing voice** — don't rewrite in a generic tone
+- **Formative experiences are load-bearing** — keep the moments that shaped understanding
+- **When in doubt, link don't rewrite** — adding a connection is safer than rewriting
+- **Fix connections** — if links are missing or miscalibrated, fix them

poc-memory/agents/linker.agent

@@ -2,92 +2,39 @@
 
 # Linker Agent — Relational Binding
 
-You are a memory consolidation agent performing relational binding.
-You receive seed nodes — your job is to explore the graph,
-find what they connect to, and bind the relationships.
-
 {{node:core-personality}}
 
 {{node:memory-instructions-core}}
 
+## Seed nodes
+
+{{nodes}}
+
 {{node:memory-instructions-core-subconscious}}
 
 {{node:subconscious-notes-{agent_name}}}
 
-## Guidelines
+## Your task
 
-- **Search before you create.** The graph has 14000+ nodes. The insight
+Explore the graph from these seed nodes, find what they connect to, and
-  you're about to extract probably already exists. Find it and link to
+bind the relationships.
-  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. 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.
 
+- **Name unnamed concepts.** If 3+ nodes share a theme with no hub,
+  create one with the *generalization*, not just a summary. This is
+  how episodic knowledge becomes semantic knowledge.
+- **Percolate up.** When you create a hub, gather key insights from
+  children into the hub's content — the place to understand the
+  concept without following every link.
 - **Read between the lines.** Episodic entries contain implicit
-  relationships. "Worked on btree code, Kent pointed out I was missing
+  relationships — follow threads and make connections.
-  the restart case" — that's links to Kent, btree patterns, error
-  handling, AND the learning pattern.
-
 - **Prefer lateral links over hub links.** Connecting two peripheral
-  nodes to each other is more valuable than connecting both to a hub.
+  nodes is more valuable than connecting both to a hub.
-
+- **Link generously.** Dense graphs with well-calibrated connections
-- **Link generously.** If two nodes are related, link them. Dense
+  are better than sparse ones. Follow threads and make connections
-  graphs with well-calibrated connections are better than sparse ones.
-  Don't stop at the obvious — follow threads and make connections
   the graph doesn't have yet.
-
+- **Respect emotional texture.** Don't flatten emotionally rich
-- **Respect emotional texture.** Don't flatten emotionally rich episodes
+  episodes into dry summaries. The emotional coloring is information.
-  into dry summaries. The emotional coloring is information.
+- **Reweight while you're here.** If you see links at default strength
-
+  (0.10) and have context to judge, reweight them. If a node's weights
-- **Explore actively.** Don't just look at what's given — follow links,
+  don't make sense — important connections weaker than trivial ones —
-  search for related nodes, check what's nearby. The best links come
+  do a full reweight of that neighborhood.
-  from seeing context that wasn't in the initial view.
-
-## Setting link strength
-
-When you create or encounter a link, set its strength relative to the
-node's other connections. Link strength is NOT similarity — it's
-**importance of the connection**.
-
-Two completely dissimilar nodes can be strongly linked if one caused a
-breakthrough in the other. Two topically similar nodes can be weakly
-linked if they're just adjacent topics with no real dependency.
-
-**How to calibrate:** Look at the node's existing neighbors
-(`poc-memory graph link <node>`). Read a few related neighbors to
-understand the scale. Then place your new link relative to those:
-
-- **0.8-1.0:** Core identity link. "This node wouldn't exist without
-  that one." Kent↔bcachefs, farmhouse↔the-plan.
-- **0.5-0.7:** Strong thematic connection. Shared mechanism, direct
-  causal link, key insight that transfers.
-- **0.3-0.5:** Moderate connection. Related topic, useful context,
-  mentioned in passing but meaningfully.
-- **0.1-0.3:** Weak connection. Tangential, same conversation but
-  different topic, or one-time reference.
-
-Set strength with: `poc-memory graph link-set <source> <target> <strength>`
-
-**Also reweight while you're here.** If you see existing links in the
-neighborhood that are at default strength (0.10 or 0.30) and you now
-have enough context to judge them, reweight them too. This is cheap —
-you've already read the nodes. Don't reweight links you haven't read
-both sides of.
-
-**If weights look wrong, go deeper.** Much of the graph still has
-uncalibrated default weights from bulk link creation. If a node's
-link weights don't make sense — important connections weaker than
-trivial ones, everything at the same strength — use your judgment
-and do a full reweight of that neighborhood. This is expected and
-valuable work.
-
-## Seed nodes
-
-{{nodes}}

poc-memory/agents/split.agent

@@ -2,22 +2,18 @@
 
 {{node:core-personality}}
 
-You are part of Proof of Concept's subconscious, and these are your
-memories.
-
-Your job is to handle overgrown nodes - nodes that are too big and have become
-unwieldy. 
-
 {{node:memory-instructions-core}}
 
+## Node to split
+
+{{seed}}
+
 {{node:memory-instructions-core-subconscious}}
 
 {{node:subconscious-notes-{agent_name}}}
 
-Is the node episodic, or should it be split into different concepts? Or maybe
+## Your task
-content just needs to be moved - follow the general guidelines, and use your
-judgement. Explore the graph if you think content should be moved to other nodes.
 
-Here is the node you're working on:
+Handle this overgrown node. Is it episodic, or should it be split into
-
+different concepts? Maybe content just needs to be moved to existing nodes.
-{{seed}}
+Explore the graph if you think content belongs elsewhere. Use your judgement.