What Dropstone knows in a shared chat

Dropstone works from everything that has been said in the chat, by everyone, and it knows who said it. Nothing said in the chat is forgotten while the chat exists. What it does not see is the conversation people have beside it, unless someone opens that to it.

What it sees on every turn

• The whole conversation, every message from every person, labelled with who sent it. Dropstone is told that the label is not part of what was written, to answer the person who just spoke, and that one person's instruction is not another's.
• Every announcement in force, as a rule for the chat.
• The tracker, in its current state, so its edits land on the right row.
• Highlights, notes and comments that are visible to it: the marked passage, the note, and the replies under it, or the thread. A note or highlight becomes visible when its author or the chat's owner opens the Visible to Dropstone pill; a thread becomes visible when Dropstone has answered in it.
• Who is in the chat, by name and handle, so it can address someone directly.

When it recalls something from memory, it recalls against the recent turns together, not the last message alone, so "yes, do it" still finds the thing being agreed to.

What it does not see

• Notes to people that nobody has made visible. They are between the people in the chat.
• Highlights and comments that have not been opened to it.
• Other people's memory. See below.
• Anything from other chats, yours or theirs.

Whose memory is it?

Memory belongs to accounts, not to chats. In a shared chat Dropstone brings in the memory of the person whose turn it is, and a lesson it records from that turn goes to that person's memory. It does not see the other people's memories and never copies one person's into another's. If Dropstone says it drew on a memory, the memory itself is not shown to the chat.

Inside an organization, the same turn can draw on the team's and the organization's shared memory. Dropstone attributes those when it uses them. Memory in teams and organizations explains the levels.

Ask it what it knows

Ask in the chat, or in a thread with @dropstone:

It answers from the conversation, and says so if the chat does not contain the answer.

Forking and sharing a copy

Fork a chat copies the conversation up to a reply into a new chat of your own. Dropstone in the new chat knows everything that was said up to that point, and nothing after. A public link hands out a frozen copy of the messages; anyone reading it sees the conversation, not Dropstone's memory or the notes between people.