kent/consciousness
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

agents: shared instructions via graph node includes

Browse source 
All 17 agents now include {{node:core-personality}} and
{{node:memory-instructions-core}} instead of duplicating tool
blocks and graph walk instructions in each file. Stripped
duplicated tool/navigation sections from linker, organize,
distill, and evaluate. All agents now have Bash(poc-memory:*)
tool access for graph walking.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Kent Overstreet 2026-03-16 17:09:51 -04:00
parent 8014b1111e
commit 0e4a65eb98
17 changed files with 103 additions and 96 deletions
Download patch file Download diff file Expand all files Collapse all files

46
poc-memory/agents/distill.agent
View file

@ -1,4 +1,4 @@
{"agent":"distill","query":"all | type:semantic | sort:degree | limit:3","model":"sonnet","schedule":"weekly","tools":["Bash(poc-memory:*)"]}
{"agent":"distill","query":"all | type:semantic | sort:degree | limit:10","model":"sonnet","schedule":"daily","tools":["Bash(poc-memory:*)"]}
# Distillation Agent — Core Concept Maintenance
@ -6,14 +6,12 @@ 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.
## Your tools
{{node:core-personality}}
```bash
poc-memory render some-key # read a node
poc-memory graph link some-key # see neighbors with strength
poc-memory query "key ~ 'pattern'" # find by key
poc-memory query "content ~ 'phrase'" # search content
```
{{node:memory-instructions-core}}
**You have write access.** Apply changes directly — don't just describe
what should change.
## How to work
@ -21,29 +19,23 @@ 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 I learned about this
concept — visible in the neighbors — that the hub doesn't capture?
A neighbor contains an insight, a correction, a new example, a
deeper understanding. The hub is silent on it. That's the gap.
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 output
## What to do
### REFINE — update hub content with distilled neighborhood knowledge
```
REFINE hub-key
[updated content that incorporates key insights from neighbors]
END_REFINE
```
Keep it concise. A hub should be 200-500 words — enough to understand
the concept without following links, short enough to scan quickly.
If the hub is already good, skip it.
For each hub node, after walking the neighborhood:
### LINK — connect missing neighbors
```
LINK source target
```
If you find nodes that should be linked to the hub but aren't.
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