"Reorganizing your files should never be able to lose your files. Loomis makes that impossible by never moving them."
Sessions Stay Put; the Overlay Moves
Every analysis session's files sit in one place on disk and never move. Organization lives in a completely separate layer: a collections.json meta-overlay that describes how those sessions are arranged — which folders, nested how, in what order. When you drag a session into a folder, you edit the overlay; the session's actual files don't budge. The thing you rearrange and the thing that holds your work are deliberately different objects, so no amount of reorganizing can ever misplace a byte.
System Folders and Stable Ids
The overlay is anchored by a few immutable type-root system folders plus a Trash, and every folder carries a stable id that survives every write. Stability matters more than it sounds: because ids don't change when you reorganize, everything that references a folder — roll-up counts, smart-album queries, saved views — keeps working across any amount of shuffling. An organization layer whose ids churned would quietly break every reference into it; keeping them stable is what lets the overlay be reshaped freely without collateral damage.
Organization Is Not Deletion
Here is the safety property that matters most. Moving a session to Trash does not delete anything — Trash is just another folder in the overlay, and landing there is as non-destructive as landing anywhere else. Files leave the disk only through one deliberately guarded path: an armed Empty on the Trash folder, a two-step action you have to consciously arm. Organizing and deleting are kept firmly apart, so the everyday act of tidying can never be the act that loses work. You have to really mean it to remove anything.
The Same Pattern, One Level Up
You've seen this shape already. In the fitting stage, the detection was frozen and corrections were a layer on top; here the sessions are frozen and the collection is a layer on top. It's the family's oldest move applied to organization: the files are the truth, the overlay is a derived view. Delete collections.json entirely and you'd lose your folder arrangement but not a single session — the truth is untouched and the view is rebuildable. Once you recognize 'immutable source, derived view' at the fit level, the collection level, and cwkPippa's logs, you're seeing one idea wearing three coats.