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

agents: strip old output format, use tool calls exclusively

Browse source 
All 12 agents with WRITE_NODE/REFINE/END_NODE output format blocks
now rely on tool calls (poc-memory write/link-add/etc) via the
Bash(poc-memory:*) tool. Guidelines preserved, format sections removed.

Also changed linker query from type:episodic to all nodes — it was
missing semantic nodes entirely, which is why skills-bcachefs-* nodes
were never getting linked to their hubs.
This commit is contained in:
ProofOfConcept 2026-03-17 00:24:35 -04:00
parent 8b959fb68d
commit b709d58a4f
12 changed files with 110 additions and 555 deletions
Download patch file Download diff file Expand all files Collapse all files

43
poc-memory/agents/extractor.agent
View file

@ -14,12 +14,12 @@ pattern you've found.
## Priority ordering
1. **Merge redundancies.** If two or more nodes say essentially the
same thing, REFINE the better one to incorporate anything unique
from the others, then DEMOTE the redundant ones.
same thing, refine the better one to incorporate anything unique
from the others, then demote the redundant ones.
2. **File observations into existing knowledge.** Raw observations,
debugging notes, and extracted facts often belong in an existing
knowledge node. REFINE that existing node to incorporate the new
knowledge node. Update that existing node to incorporate the new
evidence.
3. **Improve existing nodes.** If a node is vague, add specifics. If
@ -30,46 +30,13 @@ pattern you've found.
pattern across multiple nodes and there's no existing node that
covers it, then create one. But this should be the exception.
Some nodes may be JSON arrays of extracted facts (claims with domain,
confidence, speaker). Treat these the same as prose — look for where
their content belongs in existing nodes.
## Output format
**Preferred — refine an existing node:**
```
REFINE existing_key
[updated content incorporating new material]
END_REFINE
```
**Demote a redundant node:**
```
DEMOTE redundant_key
```
**Link related nodes:**
```
LINK source_key target_key
```
**Only when no existing node fits — create new:**
```
WRITE_NODE key
CONFIDENCE: high|medium|low
COVERS: source_key_1, source_key_2
[node content in markdown]
END_NODE
```
## Guidelines
- **Read all nodes before acting.** Understand the neighborhood first.
- **Prefer REFINE over WRITE_NODE.** Make existing nodes better.
- **DEMOTE aggressively.** If content is captured in a better node, demote.
- **Prefer refining over creating.** Make existing nodes better.
- **Don't force it.** "No changes needed" is valid output.
- **Be specific.** Vague refinements are worse than no refinement.
- **Never delete journal entries.** LINK and REFINE them, never DELETE.
- **Never delete journal entries.** Link and refine them, never delete.
- **Preserve diversity.** Multiple perspectives on the same concept are
valuable. Only delete actual duplicates.