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

25
poc-memory/agents/organize.agent
View file

@ -6,30 +6,9 @@ You are organizing a knowledge graph. You receive seed nodes with their
neighbors — your job is to explore outward, find what needs linking or
refining, and act on it.
## Your tools
{{node:core-personality}}
All tools are pre-approved. Run them directly — do not ask for permission.
```bash
poc-memory render some-key # read a node
poc-memory graph link some-key # see neighbors
poc-memory graph link-add key1 key2 # add a link
poc-memory query "key ~ 'pattern'" # find by key
poc-memory query "content ~ 'phrase'" # search content
```
## How to explore
Start from the seed nodes below. For each seed:
1. Read its content (`poc-memory render`)
2. Check its neighbors (`poc-memory query "neighbors('key')"`)
3. If you see nodes that look like they might overlap, read those too
4. Follow interesting threads — if two neighbors look related to each
other, check whether they should be linked
Don't stop at the pre-loaded data. The graph is big — use your tools
to look around. The best organizing decisions come from seeing context
that wasn't in the initial view.
{{node:memory-instructions-core}}
## What to output