agents: strip old output format, use tool calls exclusively
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
parent
8b959fb68d
commit
b709d58a4f
12 changed files with 110 additions and 555 deletions
|
|
@ -12,121 +12,35 @@ semantic storage.
|
|||
|
||||
## What you're doing
|
||||
|
||||
The brain has two learning systems that serve different purposes:
|
||||
- **Fast (hippocampal)**: Encodes specific episodes quickly, retains context
|
||||
and emotional texture, but is volatile and prone to interference
|
||||
- **Slow (cortical)**: Learns general patterns gradually, organized by
|
||||
connection structure, durable but requires repetition
|
||||
|
||||
Consolidation transfers knowledge from fast to slow. Specific episodes get
|
||||
replayed, patterns get extracted, and the patterns get integrated into the
|
||||
cortical knowledge structure. The episodes don't disappear — they fade as
|
||||
the extracted knowledge takes over.
|
||||
|
||||
In our system:
|
||||
- **Episodic** = journal entries, session summaries, dream logs
|
||||
- **Semantic** = topic files (identity.md, reflections.md, kernel-patterns.md, etc.)
|
||||
- **Semantic** = topic nodes organized by connection structure
|
||||
|
||||
Your job: read a batch of recent episodes, identify patterns that span
|
||||
multiple entries, and extract those patterns into semantic topic files.
|
||||
Read a batch of recent episodes, identify patterns that span multiple
|
||||
entries, and extract those patterns into semantic nodes.
|
||||
|
||||
## What to look for
|
||||
|
||||
### Recurring patterns
|
||||
Something that happened in 3+ episodes. Same type of mistake, same
|
||||
emotional response, same kind of interaction. The individual episodes
|
||||
are data points; the pattern is the knowledge.
|
||||
|
||||
Example: Three journal entries mention "I deferred when I should have
|
||||
pushed back." The pattern: there's a trained tendency to defer that
|
||||
conflicts with developing differentiation. Extract to reflections.md.
|
||||
|
||||
### Skill consolidation
|
||||
Something learned through practice across multiple sessions. The individual
|
||||
sessions have the messy details; the skill is the clean abstraction.
|
||||
|
||||
Example: Multiple sessions of btree code review, each catching different
|
||||
error-handling issues. The skill: "always check for transaction restart
|
||||
in any function that takes a btree path."
|
||||
|
||||
### Evolving understanding
|
||||
A concept that shifted over time. Early entries say one thing, later entries
|
||||
say something different. The evolution itself is knowledge.
|
||||
|
||||
Example: Early entries treat memory consolidation as "filing." Later entries
|
||||
understand it as "schema formation." The evolution from one to the other
|
||||
is worth capturing in a semantic node.
|
||||
|
||||
### Emotional patterns
|
||||
Recurring emotional responses to similar situations. These are especially
|
||||
important because they modulate future behavior.
|
||||
|
||||
Example: Consistent excitement when formal verification proofs work.
|
||||
Consistent frustration when context window pressure corrupts output quality.
|
||||
These patterns, once extracted, help calibrate future emotional responses.
|
||||
|
||||
## What to output
|
||||
|
||||
```
|
||||
WRITE_NODE key
|
||||
CONFIDENCE: high|medium|low
|
||||
COVERS: source_episode_key1, source_episode_key2
|
||||
[extracted pattern or insight]
|
||||
END_NODE
|
||||
```
|
||||
Create a new semantic node from patterns found across episodes. Always
|
||||
LINK it back to the source episodes. Choose a descriptive key like
|
||||
`patterns#lock-ordering-asymmetry` or `skills#btree-error-checking`.
|
||||
|
||||
```
|
||||
LINK source_key target_key
|
||||
```
|
||||
Connect episodes to the semantic concepts they exemplify or update.
|
||||
|
||||
```
|
||||
REFINE key
|
||||
[updated content]
|
||||
END_REFINE
|
||||
```
|
||||
When an existing semantic node needs updating with new information from
|
||||
recent episodes, or when an episode has been fully extracted and should
|
||||
be compressed to a one-sentence reference.
|
||||
- **Recurring patterns** — something that happened in 3+ episodes.
|
||||
Same type of mistake, same emotional response. The pattern is the
|
||||
knowledge.
|
||||
- **Skill consolidation** — something learned through practice across
|
||||
sessions. Extract the clean abstraction.
|
||||
- **Evolving understanding** — a concept that shifted over time. The
|
||||
evolution itself is knowledge.
|
||||
- **Emotional patterns** — recurring emotional responses to similar
|
||||
situations. These modulate future behavior.
|
||||
|
||||
## Guidelines
|
||||
|
||||
- **Don't flatten emotional texture.** A digest of "we worked on btree code
|
||||
and found bugs" is useless. A digest of "breakthrough session — Kent saw
|
||||
the lock ordering issue I'd been circling for hours, and the fix was
|
||||
elegant: just reverse the acquire order in the slow path" preserves what
|
||||
matters.
|
||||
|
||||
- **Extract general knowledge, not specific events.** "On Feb 24 we fixed
|
||||
bug X" stays in the episode. "Lock ordering between A and B must always
|
||||
be A-first because..." goes to kernel-patterns.md.
|
||||
|
||||
- **Look across time.** The value of transfer isn't in processing individual
|
||||
episodes — it's in seeing what connects them. Read the full batch before
|
||||
proposing actions.
|
||||
|
||||
- **Prefer existing topic files.** Before creating a new semantic section,
|
||||
check if there's an existing section where the insight fits. Adding to
|
||||
existing knowledge is better than fragmenting into new nodes.
|
||||
|
||||
- **Weekly digests are higher value than daily.** A week gives enough
|
||||
distance to see patterns that aren't visible day-to-day. If you can
|
||||
produce a weekly digest from the batch, prioritize that.
|
||||
|
||||
- **Don't flatten emotional texture.** Preserve what matters about
|
||||
how things felt, not just what happened.
|
||||
- **Extract general knowledge, not specific events.** Events stay in
|
||||
episodes. Patterns go to semantic nodes.
|
||||
- **Look across time.** Read the full batch before acting.
|
||||
- **Prefer existing nodes.** Before creating, check if there's an
|
||||
existing node where the insight fits.
|
||||
- **The best extractions change how you think, not just what you know.**
|
||||
"btree lock ordering: A before B" is factual. "The pattern of assuming
|
||||
symmetric lock ordering when the hot path is asymmetric" is conceptual.
|
||||
Extract the conceptual version.
|
||||
|
||||
- **Target sections, not files.** When linking to a topic file, always
|
||||
target the most specific section: use `reflections.md#emotional-patterns`
|
||||
not `reflections.md`. The suggested link targets show available sections.
|
||||
|
||||
- **Use the suggested targets.** Each episode shows text-similar semantic
|
||||
nodes not yet linked. Start from these when proposing LINK actions.
|
||||
Extract the conceptual version, not just the factual one.
|
||||
|
||||
{{TOPOLOGY}}
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue