History & outcomes

History is this Workspace's record of what changed, when, and whether you or Mesh did it — and it is mostly for Mesh. There is no History screen to browse: Mesh reads the record, and you get it by asking. Outcome rows in chat are the separate, immediate proof that Mesh's saved work landed.

Three signals answer three questions

Play-by-play: The live steps while Mesh works: searching, reading, creating. Progress, not proof, and it disappears once the response settles.
Outcome: A row under Mesh's answer proving a change really saved. Creations and edits get a row; small changes such as renames and filing do not.
History: The lasting record of changes in this Workspace, yours and Mesh's alike. Mesh reads it for you when you ask.

Recorded in full

Nine things keep a record, split across this section and the next, and the two lists are the whole of it. These four keep the wording itself, before and after every change:

Notes: Every edit to the body, block by block, with the wording before and after. Created, renamed, and deleted are kept too.
Topic Hub pages: The writing on a Topic's Hub page is kept exactly the way a Note's body is.
Map: Topics added, renamed, moved, reordered, and removed, named and placed as they were; a removal also counts the Topics that went with it. Map Context keeps its wording before and after each edit.
Saved Commands: Created, renamed, deleted - and an edit keeps the whole name, description, and instruction as they read before and after.

Recorded as events

These five keep what happened, not what is inside: added, renamed, deleted, and for filing and flags, what moved where.

Topic filing: Every item put into a Topic or taken out of one, naming both the item and the Topic. Filing that happened on its own is marked as automatic.
Library sources: What is inside a source is never recorded - only its arrival, its name changes, and its removal.
Images: No picture-by-picture record: an edit saves as a new Image and the original stays as it was.
Videos: Added, renamed, deleted, nothing more.
Board flags: Added, renamed, deleted, and changes to what a flag rides or which Board page it sits on. Comment-only edits are not History.

What History does not record

Everything else leaves no entry:

The Board drawing itself: Ink, shapes, text, placed pictures, and Board pages. Flags are the one Board thing recorded, and the toolbar's Undo works on the drawing in front of you, not on History.
Chats: Every chat is saved and reopenable on its own; conversations are just not History entries.
Memory and the scratchpad: Memory keeps its own two cards you can read anytime, and the scratchpad lives with its chat.
Settings: A Workspace's name and its three switches, the Board background, the Workspace color, Appearance, your Profile, and your plan.

Every entry names who did it

Who made a change is recorded, not guessed. Every entry carries the same four things:

Who: you, or Mesh.
When: the exact time the change saved.
What: the item's kind and its name as it read at that moment, plus its old name when the change was a rename.
The detail for that kind: the wording before and after, the Map change, or the plain event.

Note: Entries outlive the item they describe, so History can still answer where did my Note go, and who deleted it? long after the Note is gone. What it cannot hand back is the contents: a deletion entry keeps the name only.

Ask, read, and put something back

Ask. What changed today?, What did you edit in this Note?, When was this renamed?, What happened to the Topic that was here? Mesh starts with the newest and narrows from there: to one kind of change, to you or to itself, to a single item, or to a stretch of time.
Have Mesh read it. Mesh opens one entry and tells you what it holds in plain words - the wording before and after, the Map change, or the event.
Ask for it back. Mesh takes the old wording out of that entry, checks how the item reads right now, and makes the edit again.

Note: This is not version history, and there is no restore button anywhere in the app. Nothing rolls back on its own: Mesh redoes the change as an ordinary edit, which then lands in History as its own entry. It can only put back what an entry kept - Note and Hub wording, Map structure and Map Context, a Command's text.

The one place you can see it without asking

On The Home screen, the information button on a Workspace card ends with a Recent list: up to three lines such as Mesh edited Symmetry or You added Tessellations, each with how long ago. A chat you were just in can take one of those lines. It is a peek, not the record - no wording, no filing, no detail.

Outcomes stay with the response

The row sits at the bottom of the response that did the work, grouped into Created and then Edited. A single item shows as its own chip; several collapse into a count you can open. Opening a chip gives you the card, and a Board card offers Go to board while the frame is still there; moving it doesn't break the jump. Once it is deleted the card says so and the button goes quiet.

The practical trust loop

Watch the play-by-play while Mesh works; it shows what is happening right now.
When the outcome card appears, that's your proof the change saved.
Come back later and ask Mesh what changed and when.
And when the exact current wording matters, open the item and read it.

Tip: Name the item when you ask. What did you change in the Symmetry Note yesterday? gets you an exact before-and-after; what happened? gets you a list.