Mailspring Documentation using BMAD approach#2588
Mailspring Documentation using BMAD approach#2588talekarnishita wants to merge 23 commits intoFoundry376:masterfrom
Conversation
|
2 potential issues found:
Resolved (1 issue)
This PR adds comprehensive architecture documentation for Mailspring's dual-core (Electron + C++) design and reorganizes existing documentation.
Waiting for CI checks...
|
|
Hey thanks for contributing this! I think I agree with Indent re: the duplication of the generated documentation and all of the tooling files. Happy to accept the architectural documentation if you can split it out from the other stuff going on here. There are a few existing files like |
|
Hey
Yep, that’s fair, I agree on the duplication concern. I’ll split out the
architectural documentation and keep the rest out of this PR.
I’ll also move existing files like PLUGIN_SYSTEM_ARCHITECTURE.md into a new
docs/ directory so everything lives in one place. Will push an update
shortly.
Best Regards,
Nishita Talekar
…On Sun, Feb 8, 2026 at 12:58 AM Ben Gotow ***@***.***> wrote:
*bengotow* left a comment (Foundry376/Mailspring#2588)
<#2588 (comment)>
Hey thanks for contributing this! I think I agree with Indent re: the
duplication of the generated documentation and all of the tooling files.
Happy to accept the architectural documentation if you can split it out
from the other stuff going on here. There are a few existing files like
PLUGIN_SYSTEM_ARCHITECTURE.md that should probably go into a new docs
folder too.
—
Reply to this email directly, view it on GitHub
<#2588 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BN47A3K3Q4OKFGCU36QBUC34KY4FDAVCNFSM6AAAAACT3LRYQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQNRVGE2DGNBYHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Co-authored-by: Cursor <[email protected]>
Co-authored-by: Cursor <[email protected]>
Co-authored-by: Cursor <[email protected]>
Co-authored-by: Cursor <[email protected]>
Co-authored-by: Cursor <[email protected]>
Co-authored-by: Cursor <[email protected]>
Co-authored-by: Cursor <[email protected]>
Co-authored-by: Cursor <[email protected]>
Co-authored-by: Cursor <[email protected]>
Co-authored-by: Cursor <[email protected]>
…, LOCALIZATION, CONTRIBUTING to docs/ Co-authored-by: Cursor <[email protected]>
Co-authored-by: Cursor <[email protected]>
|
Hi, I’ve moved all the Markdown files to the root docs folder, created a
README for it, and removed all unnecessary and duplicate files—keeping only
the architecture-related files. I’ve pushed the changes.
Best regards,
Nishita Talekar
On Mon, Feb 9, 2026 at 9:21 PM nishita talekar ***@***.***>
wrote:
… Hey
Yep, that’s fair, I agree on the duplication concern. I’ll split out the
architectural documentation and keep the rest out of this PR.
I’ll also move existing files like PLUGIN_SYSTEM_ARCHITECTURE.md into a
new docs/ directory so everything lives in one place. Will push an update
shortly.
Best Regards,
Nishita Talekar
On Sun, Feb 8, 2026 at 12:58 AM Ben Gotow ***@***.***>
wrote:
> *bengotow* left a comment (Foundry376/Mailspring#2588)
> <#2588 (comment)>
>
> Hey thanks for contributing this! I think I agree with Indent re: the
> duplication of the generated documentation and all of the tooling files.
> Happy to accept the architectural documentation if you can split it out
> from the other stuff going on here. There are a few existing files like
> PLUGIN_SYSTEM_ARCHITECTURE.md that should probably go into a new docs
> folder too.
>
> —
> Reply to this email directly, view it on GitHub
> <#2588 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BN47A3K3Q4OKFGCU36QBUC34KY4FDAVCNFSM6AAAAACT3LRYQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQNRVGE2DGNBYHE>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
|
Hi, I’ve moved all the Markdown files to the root docs folder, created a README for it, and removed all unnecessary and duplicate files—keeping only the architecture-related files. I’ve pushed the changes. |
This folder contains the complete documentation set for the Mailspring "Dual-Core" architecture, reverse-engineered using the BMAD framework.
The documentation is organized into three phases: Phase 1 (Big Picture), Phase 2 (Mechanics), and Phase 3 (Analysis).
📋 Reviewer Reading Guide
To understand the system architecture effectively, please review the documents in the following order:
1. The Roadmap
PLAN.md: The master plan and checklist used to generate these artifacts. Start here to see the scope of work.CLAUDE.md: The existing high-level summary (updated/referenced).2. Phase 1: The Big Picture (Architecture)
docs/architecture/current-state.md: The core narrative explaining the "Dual-Core" design (Electron frontend + C++ backend).docs/architecture/diagrams/system-context.md: High-level C4 diagram showing Mailspring and its external providers (Gmail, O365, etc.).docs/architecture/diagrams/containers.md: C4 Container diagram showing the process boundaries (Renderer, Main, Mailsync, SQLite).3. Phase 2: The Mechanics (How it works)
docs/architecture/data-flow.md: Traces the critical path of data from the Internet → C++ Engine → SQLite → Electron UI.docs/architecture/data-model.md: (New) ER Diagram showing the database schema (Threads, Messages, Contacts) derived from Flux models.docs/guides/debugging-dual-core.md: (New) Essential guide for debugging the C++ bridge and inspectingstdin/stdouttraffic.docs/architecture/module-dependencies.md: Explains how Flux stores (DatabaseStore, Actions) interact with the Mailsync Bridge.4. Phase 3: Analysis & Decisions
docs/adr/: Retrospective Architecture Decision Records explaining why the system is built this way.0001-split-engine-architecture.md(Why C++?)0002-local-first-strategy.md(Why local SQLite?)docs/technical-debt.md: A prioritized register of TODOs and legacy patterns found in the codebase.📂 File Structure Overview
docs/architecture/diagrams/docs/architecture/deployment.mddocs/architecture/technology-stack.mddocs/architecture/integration-points.md