Make documents visible in the file system #188
Description
While using Reflection, one thing that feels slightly surprising to me as a user is that documents only seem to exist inside the application and can’t be seen or found as files on my system.
Given the local-first nature of the app, my instinctive expectation is that documents would somehow be visible on disk, for example as .md files in a folder. Being able to see them as files helps build a clear mental model of where data lives and how it relates to the rest of the system.
If documents were exposed in the file system, my expectation would be that they behave like real files: editable with other tools, and that changes made outside Reflection are meaningfully picked up by the app. From a user perspective, anything that looks like a normal file invites normal file interactions. At the same time, I understand that supporting this safely might be complex or incompatible with Reflection’s internal model. In that case, keeping documents fully internal is a coherent choice. What matters to me is that this boundary is clear and intentional, rather than surprising.
I’m raising this mainly as a UX perspective: starting from the feeling that “I expected to see my documents as files”, and how that expectation shapes how users understand data ownership in a local-first application.