Why the first release starts with the Markdown document loop
Boreal Markdown keeps version 1.0 focused on opening files, previewing documents, editing source text, saving safely, and exporting PDFs.
Markdown users already have files. The first release of Boreal Markdown should respect that reality instead of asking people to move into another system.
The useful iOS job is direct: open a .md file, understand the rendered document, make a small edit, save intentionally, and export something readable.
The P0 loop
Boreal Markdown version 1.0 is scoped around five connected actions:
- open
.mdand.markdownfiles through iOS file access - preview rendered Markdown with clear typography
- edit source text with compact Markdown tools
- keep save state visible so changes do not feel mysterious
- export a clean PDF that can be shared, saved, or printed
That loop is intentionally smaller than a full writing suite or knowledge base. It is also more useful than a generic file previewer because PDF export and source editing are part of the same document surface.
What is deliberately absent
The P0 release is not an AI writer, a hosted note service, a collaboration product, or a vault system. It does not need accounts, hosted sync, cloud document processing, plugins, backlinks, or graph views.
Those features would change the trust model. The first product promise should be quieter: your Markdown file stays your file, and Boreal Markdown helps you read, adjust, and export it on iOS.