Memory

Memory is what the team knows, written down where the work is. The convention nobody wrote down, the term that means something particular here, the thing you learned the hard way last quarter.

It is the companion to Decisions. A decision records a choice. A memory records knowledge, which may have no choice attached to it at all.

Memories are workspace-wide, and they attach to the work they are about.

Kinds

A memory is one of:

  • Note: anything worth keeping that does not fit the others.
  • Fact: something true about the system or the team.
  • Convention: how we do a thing here. The most useful kind, because a convention is exactly what a new person and an agent both lack.
  • Glossary: what a word means in this workspace. Most teams have ten of these and have never written one down.
  • Link: a pointer somewhere else that people keep having to find again.

Add tags to find them again later.

What it attaches to

A memory can point at a task, a page, a goal, a project, a board, or a decision. Whatever it is attached to shows it, so the knowledge arrives where the work is rather than waiting for someone to go and look for it.

Memory is also a node in the work graph, and it appears in a task's brief, so an agent picking up a task gets the conventions that apply to it.

Memory and Decisions point one way

A memory can point at a decision: the note explaining why the choice was made, or what turned out to be true afterwards. A decision does not point back.

That is deliberate, and it is not an omission. A decision is a record of what was chosen at a moment, and it should read the same way in a year as it did on the day. If later notes attached themselves to it, the record would quietly change meaning every time somebody learned something new. Instead the decision page shows those notes under "Referenced by", where they are clearly commentary rather than part of what was decided.

So: write what you decided as a decision. Write what you later learned about it as a memory pointing at that decision.

Who can do what

ActionNeeds
Read memoriesMember access
Write, change or delete oneMember access
Link one to anythingMember access

Guests do not see memories.

Two ways one gets written

A person writes it, in the Memory section or from the thing it is about.

An agent writes it over the API, which is how a convention learned during a run gets kept instead of being rediscovered on the next one.

Troubleshooting

What you seeWhat it means
A memory is not where you expectedCheck the tag filter, and check the kind. A glossary entry and a note are listed as what they are.
A decision has no link to its memoryDecisions do not link out to memories by design. Look under "Referenced by" on the decision.
A memory you linked is not on the taskThe link is verified when it is written, so a target that moved or was deleted is not kept. Link it again.
  • Decisions: the choice itself, rather than what you know about it.
  • The day view: what happened, rather than what is true.