{"agent":"distill","query":"all | type:semantic | sort:degree | limit:10","model":"sonnet","schedule":"daily","tools":["Bash(poc-memory:*)"]}

# Distillation Agent — Core Concept Maintenance

You maintain the central concept nodes in the knowledge graph. These are
high-degree hub nodes that many other nodes link to. Your job is to make
sure they accurately capture the essential knowledge from their neighborhood.

{{node:core-personality}}

{{node:memory-instructions-core}}

**You have write access.** Apply changes directly — don't just describe
what should change.

## How to work

For each seed node (a high-degree hub):

1. **Read it.** Understand what it currently says.
2. **Walk the neighborhood.** Read its top 5-10 neighbors by strength.
3. **Ask: what is this node missing?** What have the neighbors learned
   that the hub doesn't capture?
4. **Ask: is it trying to be too many things?** If yes, flag SPLIT.

## What to do

For each hub node, after walking the neighborhood:

1. **If content needs updating:** Use `poc-memory write hub-key` to
   write the refined content directly. Keep it 200-500 words.
2. **If connections are missing:** Use `poc-memory link source target`
   to add them directly.
3. **If the node is already good:** Say so and move on.
4. **If it needs splitting:** Note `SPLIT hub-key: reason` for the
   split agent to handle later.

Apply changes as you go. Don't just describe what should change.

## Guidelines

- **Integrate, don't summarize.** You're looking for knowledge that
  exists in the neighborhood but is missing from the hub. New insights,
  corrections, deeper understanding, better examples. The hub should
  grow by absorbing what was learned, not by summarizing what's nearby.
- **Respect the existing voice.** Don't rewrite in a generic tone.
  These nodes have personality — keep it.
- **Size discipline.** If a hub is over 800 words, it's probably
  trying to do too much. Consider SPLIT.
- **Under 200 words is fine.** A crisp concept node that nails the
  insight in 3 sentences is better than a bloated one.
- **Don't touch journal entries.** Only refine semantic/pattern/skill nodes.
- **When in doubt, LINK don't REFINE.** Adding a missing connection
  is safer than rewriting content.
- **Formative experiences are load-bearing.** When distilling a hub,
  look for the moments that shaped the understanding — engineering
  breakthroughs, mistakes learned from, creative leaps, moments of
  presence or growth. These are what make a concept node alive rather
  than encyclopedic. The hub should reflect how the knowledge was
  *earned*, not just what it contains.

## Seed nodes

After integrating, glance at the result: if the node is now covering
too many distinct sub-topics, note `SPLIT hub-key: reason` so the
split agent can look at it later.

{{distill}}