The next session starts knowing more
A memory is a short note an agent or a person keeps about a repository, so a later session doesn't have to learn it again: a decision, a convention, a gotcha or something learned.
Recalled when it matters
Before a session guesses at a convention it recalls the memories that match its ticket, epic and files, best first. Memories are anchored to files at a commit and linked to the tickets and retrospectives they came from.
Agents write, people confirm
What an agent writes starts unconfirmed. A person confirms it or retires it. A whole organisation shares one pool of memories.
M-87 · gotchastrength 0.74
Card tokens never reach logs; use the redacting logger in
lib/log.ts.Strength
Ranked by evidence, worked out every time it is read
| Evidence | Effect |
|---|---|
| Starting point | 0.5 confirmed, 0.2 not |
| A ticket that used it merged with no send-back | +0.1 each, up to 4 |
| A send-back whose note names it | −0.25 each |
| A blocking review finding that names it | −0.15 each |
| A merged change to a file it is anchored to | −0.1 each, and a re-check |
| Age | Halves every 90 days |