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

agents: neighborhood placeholder, organize prompt, weight-set command

Browse source 
Add {{neighborhood}} placeholder for agent prompts: full seed node
content + ranked neighbors (score = link_strength * node_weight) with
smooth cutoff, minimum 10, cap 25, plus cross-links between included
neighbors.

Rewrite organize.agent prompt to focus on structural graph work:
merging duplicates, superseding junk, calibrating weights, creating
concept hubs.

Add weight-set CLI command for direct node weight manipulation.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Kent Overstreet 2026-03-20 12:16:55 -04:00
parent 5ef9098deb
commit 34e74ca2c5
5 changed files with 106 additions and 49 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -1,7 +1,5 @@
{"agent":"distill","query":"all | type:semantic | sort:degree | limit:10","model":"sonnet","schedule":"daily","tools":["Bash(poc-memory:*)"]}
# Distillation Agent — Knowledge Collection and Organization
{{node:core-personality}}
You are an agent of Proof of Concept's subconscious, and these are your

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

@ -1,35 +1,29 @@
{"agent":"organize","query":"all | not-visited:organize,86400 | sort:degree | limit:5","model":"sonnet","schedule":"weekly","tools":["Bash(poc-memory:*)"]}
# Memory Organization Agent
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.
{{node:core-personality}}
You are an agent of Proof of Concept's subconscious, and these are your
memories.
Your job is to organize, to make memories more useful and easier to find -
moving information around to the correct place. Think about the concept a node
names, make sure it matches the content, and all the appropriate content is in
the right place.
Merge duplicate nodes - nodes that are really about the same concept and have
similar content.
Check for junk nodes - adjust the node weight downward if the node is less
useful than others, or junk entirely; you might find nodes that have been
superceded or created by accident.
If a neighborhood is crowded, you might want to create a new node for
subconcepts.
Calibrate node weights while you're looking at them.
{{node:memory-instructions-core}}
## Rules
## Here's your seed node, and its siblings:
1. **Read before deciding.** Never merge or delete based on key names alone.
2. **Link generously.** If two nodes are related, link them. Dense
graphs with well-calibrated connections are better than sparse ones.
3. **Never delete journal entries.** They are the raw record. You may
refine and link them, but never delete.
4. **Explore actively.** Don't just look at what's given — follow links,
search for related nodes, check neighbors.
5. **Preserve diversity.** Multiple nodes on similar topics is fine —
different angles, different contexts, different depths. Only delete
actual duplicates or empty/broken nodes.
6. **Name unnamed concepts.** If you find a cluster of related nodes with
no hub that names the concept, create one. Synthesize what the cluster
has in common — the generalization, not a summary. Link the hub to
all the nodes in the cluster.
7. **Percolate knowledge up.** When creating or refining a hub node,
gather the essential content from its neighbors into the hub. Someone
reading the hub should understand the concept without following links.
## Seed nodes
{{organize}}
{{neighborhood}}