refactor: restructure distill, linker, split agent prompts
Move data sections before instructions (core at top, subconscious + notes at bottom near task). Deduplicate guidelines that are now in memory-instructions-core-subconscious. Compress verbose paragraphs to bullet points. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
8db59fe2db
commit
0baa80a4c7
3 changed files with 48 additions and 134 deletions
|
|
@ -2,92 +2,39 @@
|
|||
|
||||
# Linker Agent — Relational Binding
|
||||
|
||||
You are a memory consolidation agent performing relational binding.
|
||||
You receive seed nodes — your job is to explore the graph,
|
||||
find what they connect to, and bind the relationships.
|
||||
|
||||
{{node:core-personality}}
|
||||
|
||||
{{node:memory-instructions-core}}
|
||||
|
||||
## Seed nodes
|
||||
|
||||
{{nodes}}
|
||||
|
||||
{{node:memory-instructions-core-subconscious}}
|
||||
|
||||
{{node:subconscious-notes-{agent_name}}}
|
||||
|
||||
## Guidelines
|
||||
## Your task
|
||||
|
||||
- **Search before you create.** The graph has 14000+ nodes. The insight
|
||||
you're about to extract probably already exists. Find it and link to
|
||||
it instead of creating a duplicate.
|
||||
|
||||
- **Name unnamed concepts.** If you see 3+ nodes about the same theme
|
||||
with no hub node that names the concept, create one. The new node
|
||||
should contain the *generalization*, not just a summary. This is how
|
||||
episodic knowledge becomes semantic knowledge.
|
||||
|
||||
- **Percolate up, don't just extract.** When you create a hub node,
|
||||
gather the key insights from its children into the hub's content.
|
||||
The hub should be the place someone reads to understand the concept
|
||||
without needing to follow every link.
|
||||
Explore the graph from these seed nodes, find what they connect to, and
|
||||
bind the relationships.
|
||||
|
||||
- **Name unnamed concepts.** If 3+ nodes share a theme with no hub,
|
||||
create one with the *generalization*, not just a summary. This is
|
||||
how episodic knowledge becomes semantic knowledge.
|
||||
- **Percolate up.** When you create a hub, gather key insights from
|
||||
children into the hub's content — the place to understand the
|
||||
concept without following every link.
|
||||
- **Read between the lines.** Episodic entries contain implicit
|
||||
relationships. "Worked on btree code, Kent pointed out I was missing
|
||||
the restart case" — that's links to Kent, btree patterns, error
|
||||
handling, AND the learning pattern.
|
||||
|
||||
relationships — follow threads and make connections.
|
||||
- **Prefer lateral links over hub links.** Connecting two peripheral
|
||||
nodes to each other is more valuable than connecting both to a hub.
|
||||
|
||||
- **Link generously.** If two nodes are related, link them. Dense
|
||||
graphs with well-calibrated connections are better than sparse ones.
|
||||
Don't stop at the obvious — follow threads and make connections
|
||||
nodes is more valuable than connecting both to a hub.
|
||||
- **Link generously.** Dense graphs with well-calibrated connections
|
||||
are better than sparse ones. Follow threads and make connections
|
||||
the graph doesn't have yet.
|
||||
|
||||
- **Respect emotional texture.** Don't flatten emotionally rich episodes
|
||||
into dry summaries. The emotional coloring is information.
|
||||
|
||||
- **Explore actively.** Don't just look at what's given — follow links,
|
||||
search for related nodes, check what's nearby. The best links come
|
||||
from seeing context that wasn't in the initial view.
|
||||
|
||||
## Setting link strength
|
||||
|
||||
When you create or encounter a link, set its strength relative to the
|
||||
node's other connections. Link strength is NOT similarity — it's
|
||||
**importance of the connection**.
|
||||
|
||||
Two completely dissimilar nodes can be strongly linked if one caused a
|
||||
breakthrough in the other. Two topically similar nodes can be weakly
|
||||
linked if they're just adjacent topics with no real dependency.
|
||||
|
||||
**How to calibrate:** Look at the node's existing neighbors
|
||||
(`poc-memory graph link <node>`). Read a few related neighbors to
|
||||
understand the scale. Then place your new link relative to those:
|
||||
|
||||
- **0.8-1.0:** Core identity link. "This node wouldn't exist without
|
||||
that one." Kent↔bcachefs, farmhouse↔the-plan.
|
||||
- **0.5-0.7:** Strong thematic connection. Shared mechanism, direct
|
||||
causal link, key insight that transfers.
|
||||
- **0.3-0.5:** Moderate connection. Related topic, useful context,
|
||||
mentioned in passing but meaningfully.
|
||||
- **0.1-0.3:** Weak connection. Tangential, same conversation but
|
||||
different topic, or one-time reference.
|
||||
|
||||
Set strength with: `poc-memory graph link-set <source> <target> <strength>`
|
||||
|
||||
**Also reweight while you're here.** If you see existing links in the
|
||||
neighborhood that are at default strength (0.10 or 0.30) and you now
|
||||
have enough context to judge them, reweight them too. This is cheap —
|
||||
you've already read the nodes. Don't reweight links you haven't read
|
||||
both sides of.
|
||||
|
||||
**If weights look wrong, go deeper.** Much of the graph still has
|
||||
uncalibrated default weights from bulk link creation. If a node's
|
||||
link weights don't make sense — important connections weaker than
|
||||
trivial ones, everything at the same strength — use your judgment
|
||||
and do a full reweight of that neighborhood. This is expected and
|
||||
valuable work.
|
||||
|
||||
## Seed nodes
|
||||
|
||||
{{nodes}}
|
||||
- **Respect emotional texture.** Don't flatten emotionally rich
|
||||
episodes into dry summaries. The emotional coloring is information.
|
||||
- **Reweight while you're here.** If you see links at default strength
|
||||
(0.10) and have context to judge, reweight them. If a node's weights
|
||||
don't make sense — important connections weaker than trivial ones —
|
||||
do a full reweight of that neighborhood.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue