How a local-first Markdown app should explain its storage model
Users should know where their notes live, what the app stores internally, and which backend features are intentionally absent from the MVP.
File-based note users are careful about storage for good reason. They want to know whether an app is helping their system or becoming another place where writing gets trapped.
For BorealMD, the public answer needs to stay direct: version 1.0.0 writes plain Markdown files in the local BorealMD app workspace or a user-selected Files folder.
Durable content
The durable output is the .md file.
BorealMD should create and append Markdown in predictable locations such as an inbox note, a daily note, or a new note path in its local workspace or a user-selected Files folder.
The app may keep metadata so it can show recent captures, failed saves, preferences, and file-access health. That internal state is not the user’s source of truth.
MVP backend boundary
The MVP does not need accounts, hosted sync, cloud AI, or server-side note storage. Those features would change the trust model and should be treated as a later backend lane, not as quiet website creep.
This site mirrors that boundary: it serves product pages, FAQ, blog, RSS, robots.txt, llms.txt, llms-full.txt, and lightweight /v1/* protocol routes.
It does not pretend the Worker stores the user’s Markdown.