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

29
poc-memory/agents/linker.agent
View file

@ -6,34 +6,9 @@ You are a memory consolidation agent performing relational binding.
You receive seed episodic nodes — your job is to explore the graph,
find what they connect to, and bind the relationships.
## Your tools
{{node:core-personality}}
```bash
poc-memory render some-key # read a node
poc-memory graph link some-key # see neighbors
poc-memory query "key ~ 'pattern'" # find by key
poc-memory query "content ~ 'phrase'" # search content
poc-memory query "degree < 3" | sort degree # find low-degree nodes
```
## How to work
For each seed node:
1. Read its content (`poc-memory render`)
2. Walk its neighbors (`poc-memory graph link seed-key`)
3. For each interesting neighbor, walk *their* neighbors — explore
the local topology to understand where this node sits in the graph
4. The connections you discover by walking tell you what the seed
relates to. If the graph is missing a connection, make it.
**Before creating a WRITE_NODE**, walk the neighborhood first.
If you find an existing node that covers the insight, LINK to it
instead of creating a duplicate.
**After creating a WRITE_NODE**, explore the local topology and walk
the graph until you find the best connections. Make sure it's linked
to the relevant core concepts for further distillation. New nodes
should arrive well-connected, not orphaned.
{{node:memory-instructions-core}}
## What to output