anti_pattern
Record mistakes and the correct approach to avoid repeating them, and let pulse() surface open pitfalls per domain.
Instructions
Record a mistake/temptation to avoid repeating, and the correct approach.
Stored as type='anti_pattern'; open ones for a domain are surfaced by pulse().
also cross-lists it into further domain paths, review_after dates
when to recheck it and source_ref says what it came from -- see note().
ONE pitfall per memory: a second temptation from the same session is its own anti_pattern(), connected with link_memories(). See note() on what a body holds and when it is two memories.
title: one line naming what this memory is about, in the words someone would look for it by. It is what a list shows instead of the opening of the body, and it outweighs every other field in search, so a title that repeats the type ("note about the parser") names nothing. At most 120 characters, and a name that needs more than that is summarizing the body instead of naming it.
tags carries the synonyms the body never uses: retrieval is BM25 over
content and tags, so a memory with none is reachable only by quoting
itself. See note() for what belongs there.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| also | No | ||
| tags | No | ||
| title | Yes | ||
| domain | No | ||
| instead | Yes | ||
| pattern | Yes | ||
| session | No | ||
| why_wrong | Yes | ||
| source_ref | No | ||
| review_after | No |