What local file ownership means in mdquire
Plain Markdown remains the book, while application state and recovery data have explicit boundaries.
An mdquire book can be a plain Markdown folder. No mdquire account or cloud storage is required to keep and edit it. The interface language and the book language are separate, so opening a folder does not silently assign it the interface’s language.
What stays outside the manuscript
M1 keeps its full-text search index in memory. Recent books, layout and the headings index live in application state rather than becoming another copy of the book’s prose. Recovery versions and editor journals have a separate recovery store for the saves that need them.
What external work requires
Local files and local git need no mdquire sign-in. GitHub authorization is only for GitHub operations. Agent workflows are planned for M4 and M5 with bounded material and approvals; they are not available in M1.