What changed in the product, in the order it happened, including the decisions that made it smaller. Written for people using it, not as an engineering diary.
Putting your vault in a sync folder would quietly copy it to someone else's servers, and disk encryption doesn't prevent that. It now checks at startup and stops rather than warning.
"We'll check that recall is good" was an intention. It's now a gate with a threshold: one real vault, one assistant, and a demonstrated loop of remembering, correcting and deleting across sessions. The test.
Reading memories quickly depends on the files being readable as-is. Rather than half-build it, we've documented the gap and recommend your operating system's own disk encryption. Why, in detail.
Proving who's connecting is designed; deciding what a given person is allowed to read isn't. The team tier won't ship before that exists, so it stays listed as unavailable rather than "coming soon".
Space management moves memories between faster and slower storage based on what you've actually used recently. Anything marked private is excluded from leaving your machine before that decision is made, and moving something is never the same as forgetting it.