When we shipped the Receipts log, it lived inside one app at a time. Jarvis had its receipts; Tensor had its own. They looked identical, but they were two logs that did not know about each other.
That seam turned out to be the most important thing to remove. This release collapses every surface — voice, browser, code, and the new Rocky answer engine — onto a single shared log and a single shared memory.
Why the seam hurt
An agent is only trustworthy if you can see what it did. But "what it did" does not respect app boundaries. You ask Tensor to pull this month's churn from a dashboard, then ask Jarvis to draft an email about it. Two surfaces, one task. If the receipts live in two places, you have to reconstruct the story by hand — which defeats the entire point of writing receipts down.
So we unified it. There is now one log. An action taken in Tensor shows up in Jarvis and in Rocky, with the same timestamp, the same inputs, and the same one-tap undo where undo is safe.
Rocky writes to the same memory
Rocky — the personal answer-engine surface — is the third product on this base. It runs the same local model and, critically, reads and writes the same Orb memory as the other two. Ask Rocky a question that depends on something Jarvis learned last week, and it is already there. No sync, no export, no second brain to keep in step.
This is the local-first dividend showing up in a place we did not originally pitch it. Because everything runs on your device, "shared across surfaces" is just "shared on one machine" — not a cloud sync problem, not a privacy tradeoff.
What this is not
It is not multi-user. The Orb is still strictly single-principal; shared household and team memory remains a 2027 research project. What shipped here is narrower and, we think, more important first: one person, many surfaces, one coherent record of what their agent has done on their behalf.
You can see the full set of changes on the changelog, and where this is heading on the roadmap.