Memory
What SeamTrail remembers about a feature, where each line comes from, and how it stays true.
Each feature has its own memory: short lines about what happened, each with a link to its source.
People and AI assistants read the same memory. So the next teammate, and the next assistant, starts from the same picture.
What is remembered
| Kind | Example |
|---|---|
| Decision | "Refunds stay out of v1, because the bank API is not ready." |
| Fact | "The webhook retries three times." |
| Blocker | "PAY-7 can't start until PAY-4 is on stage." |
| Risk | "The load test may be too small for the new target." |
| Question | "Who owns the refund screen?" |
| Status | "PAY-4 moved to In Review." |
Every line is short: one or two sentences in plain words. When the source is long, SeamTrail keeps a short version. The full text is one click away (more).
Where it comes from
- Your tools. Changes in the tools linked to the feature: ticket moves, ticket descriptions and comments, chat messages, doc edits, pull request comments and more. See Integrations for what each tool sends.
- People. Anyone on the feature can click + Add memory and write one sentence.
- AI assistants. Connected assistants save notes with the
remembertool. See Connect an AI assistant.
Every line keeps its source: a link to the ticket, page, message, pull request or meeting it came from, plus who added it and when.
How sure a line is
Every line says how sure it is.
| Label | Meaning |
|---|---|
| Recorded | A tool recorded it. For example, Jira moved a ticket. |
| Said | A person said or wrote it: a Slack message, a Jira comment, a doc, or + Add memory. |
| Claimed | An AI assistant wrote it, and no person has checked it yet. |
Answers weigh them in that order: recorded, then said, then claimed. A live read of the tool beats any memory.
It stays true
When something stops being true, SeamTrail retires the line. Nothing is deleted. Old lines stay readable in the History tab.
This happens by itself:
- A ticket reaches Done in Jira. The open blockers, risks and questions about it close.
- A "blocked by" link is removed. The line about that blocker closes.
- A later message says a risk is gone, or answers a question. The line closes, and the reason is kept.
You can also close a line yourself: click Resolve when it is no longer true. It stays in history.
One line per thing
Several people and assistants may note the same thing. SeamTrail keeps one line and adds "also noted by" with who and when.
The copy from the source (a Slack message, a Jira comment, a doc) wins over an assistant's summary of it.
Reasons are never guessed
A decision's "because" comes only from the words of its own source. If the source gives no reason, the reason stays empty. SeamTrail never invents one.
When a decision replaces an earlier one
Say Ana decided "We use PostgreSQL". Two days later, Ben's note says "We switch to MongoDB". Here is what happens.
Only the writer is asked. Ben sees Ana's earlier decision: what it was, who decided it, when, and why. Then one question: Replace the earlier decision? It stays in history. He can click Replace it or Not now.
Nothing changes without a yes. There is no "keep both". If Ben does not answer, both lines stay and nothing is replaced. He is reminded once, in his AI assistant.
The earlier author is told, once. If Ben replaces it, Ana's decision moves to history as "replaced by" Ben's note. Ana is told once: in her AI assistant, in the SeamTrail chat ("For you"), and by Slack direct message when Slack is connected.
Nobody else is asked or told. SeamTrail is a messenger, not a referee. The two people talk and decide.
Something said in a tool, like a Slack message, never replaces a decision by itself. The decision's author is told what was said.
Not settled and unconfirmed
Until someone replaces one of them, two lines that disagree are shown like this:
- Not settled: two people disagree, and both are equally sure.
- Unconfirmed: an assistant's note disagrees with a person's decision. The person's decision stands.
Answers in the chat and in your assistant name both sides, with who and when. They never pick one silently.
A note that may belong elsewhere
If a note names a ticket from another feature, SeamTrail still saves it. It tells the writer which feature the ticket is on.
Who can see the memory
Everyone on the feature sees all of its memory. This includes lines from a private Slack channel or a ticket that some of them cannot open.
The control is at linking time: only someone who can open an item can link it. When you link a private Slack channel, SeamTrail warns you first. See Links.
Coming soon
- Public memory: share selected memory with a whole org, workspace or team.
- Personal memory: notes only you can see.