Viewing an earlier version does not roll back the project.
01
Keep originals and revisions together
Edit a note without losing its original submission. Deactivate it to exclude it from active reads, reactivate it when needed, or archive and restore it. These changes create revisions. Concurrent updates are checked so one edit cannot silently overwrite another.
02
Follow the evidence in the timeline
The dated history shows original contributions and what arrived afterward. A note’s version history shows later edits and status changes. New contributions record the authenticated connection, account and receipt time; older notes may have unknown origin. This identifies who saved a contribution, not necessarily who made its decision.
03
Keep access tied to the project
Agents receive active knowledge in the project you authorized. Revoke a connection when it is no longer needed. HTTPS protects transport and Cloudflare D1 encrypts stored data at rest. This is not end-to-end encryption: authorized services and clients can read the content they receive.
The useful details
The submission timeline is not a reconstruction of the full active project at a past date. Archiving a note is reversible; deleting a project permanently erases its notes, revisions and project access.
One memory. More ways to use it.
Give your next session a head start.
Copy one brief. Connect the project. Verify the first save.