https://mdquire.com/en/news/Verified mdquire development notes and future release announcements.enFri, 13 Nov 2026 00:00:00 GMThttps://mdquire.com/en/news/local-files/https://mdquire.com/en/news/local-files/Fri, 13 Nov 2026 00:00:00 GMTPlain 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.https://mdquire.com/en/news/m0-baseline/https://mdquire.com/en/news/m0-baseline/Fri, 13 Nov 2026 00:00:00 GMTThe shell, builders and editor spike passed their Windows and Linux gates; this was not a public release.M0 built the repository and contract foundation, the Electron shell, design tokens and platform builders. It also measured a CodeMirror 6 editor spike against the project’s reference books. ## What the gate established The Windows and Linux installers started, and both platforms updated from a test release. The editor measurements were recorded against the performance targets. The macOS builder script exists, but its build, startup, download notice and measurements remain part of the later macOS verification. ## What it did not establish M0 did not complete the book workflow or produce a signed 1.0 release. M1 is the current milestone. Every build before 1.0 is an unsigned pre-release, and no public artifact is listed on the Development page.https://mdquire.com/en/news/status-model/https://mdquire.com/en/news/status-model/Fri, 13 Nov 2026 00:00:00 GMTComplete, in development, planned and to verify have different meanings across the site.The Development page distinguishes completed work from the milestone currently being implemented and later plans. The labels are tied to evidence rather than a release forecast. ## The four labels Complete means the stated gate has passed on the named platforms. In development identifies current work, not a finished feature set. Planned describes later scope without an availability promise. To verify keeps a platform or capability unavailable until its check passes. ## One status source The milestone table, platform matrix, home-page summary and product JSON read the same status file. The artifact list is empty. A download action will appear only when a real file has a version, operating system, architecture, checksum, signing status and known limits.