Research note
Why folders don't match human memory
The mismatch between folders and memory isn't a matter of taste. The two structures have incompatible properties, and the friction people feel is that incompatibility showing through.
Set the two models side by side and the failures become predictable.
01 · Membership
Exclusive versus multiple.
A file lives in one directory. A memory belongs to as many contexts as it participates in: the project, the day, the person who sent it, the argument it supports, the way it looked.
Forcing multiple membership into single membership loses information at the moment of filing, and it's the specific information you'll try to use later.
02 · Stability
Fixed versus reinterpreted.
Folder trees are stable by design; renaming and moving is expensive, so structures persist long after the thinking behind them has moved on. Memory is the opposite: what something means to you is revised continually as later events reframe it.
A save from March can become important in September for reasons that didn't exist in March. No hierarchy set up in March can express that.
Filing is a decision made once. Meaning keeps changing afterwards.
03 · Access
Address versus association.
Retrieval from a hierarchy is by path: you must reproduce the route. Retrieval from memory is by association: any sufficiently connected fragment pulls the rest with it, and the fragments people actually retain are time, appearance, purpose and adjacency.
A structure that supports association needs edges between items, not just containers around them. That's the argument for a graph, and it's why grouping by meaning tends to feel less effortful: it maps onto how the recall attempt actually starts.
Next thought
If association is the access pattern, the edges are the interesting part.
Read: the personal memory graphIf this idea interested you…
Shelf V3 is out now
Shelf V3 is the current build. Shelf does not use automatic updates, so download the latest build here and install it over your current version.
This is intentional. Shelf is built around a local-first, privacy-focused philosophy. An automatic updater requires additional background processes, network connections, update infrastructure, and another system with permission to modify the app. We prefer to keep Shelf’s network footprint and background activity as small as possible.
Manual updates keep the process explicit: Shelf only checks the internet when a feature actually needs it, and you decide when a new version is downloaded and installed.