From e17961e49e3f42d3d8fe1c3ad1d902c100e195e2 Mon Sep 17 00:00:00 2001 From: squid Date: Wed, 18 Nov 2026 18:44:18 +0100 Subject: [PATCH] Structured plan folder --- plan/01-VISION.md | 18 ++++++++++++++++++ plan/02-FEATURES.md | 15 +++++++++++++++ plan/README.md | 21 +++++++++++++++++++++ plan/architecture/README.md | 3 +++ plan/crates/README.md | 3 +++ plan/decisions/README.md | 5 +++++ plan/email/README.md | 3 +++ plan/gui/README.md | 3 +++ plan/risks/README.md | 3 +++ plan/roadmap/README.md | 3 +++ plan/security/README.md | 3 +++ 11 files changed, 80 insertions(+) create mode 100644 plan/01-VISION.md create mode 100644 plan/02-FEATURES.md create mode 100644 plan/README.md create mode 100644 plan/architecture/README.md create mode 100644 plan/crates/README.md create mode 100644 plan/decisions/README.md create mode 100644 plan/email/README.md create mode 100644 plan/gui/README.md create mode 100644 plan/risks/README.md create mode 100644 plan/roadmap/README.md create mode 100644 plan/security/README.md diff --git a/plan/01-VISION.md b/plan/01-VISION.md new file mode 100644 index 0000000..b37ac1b --- /dev/null +++ b/plan/01-VISION.md @@ -0,0 +1,18 @@ +# 01 — Vision + +## Product identity + +Moorly Mail is a modern desktop email client intended to make email simple, fast, and enjoyable, with a clean interface and thoughtful features. + +## Proposed direction + +This statement captures the current high-level product intent. It is not a detailed specification or an approval of any particular design or technology. + +## Open questions + +- What user needs and priorities should most shape the product? +- What does “simple, fast, and enjoyable” mean in practice? + +## Confirmed decisions + +No additional decisions are recorded here. Approved choices belong in [decisions/](decisions/). diff --git a/plan/02-FEATURES.md b/plan/02-FEATURES.md new file mode 100644 index 0000000..acea2c1 --- /dev/null +++ b/plan/02-FEATURES.md @@ -0,0 +1,15 @@ +# 02 — Features + +This document is a high-level index of feature direction, not a requirements specification. Keep detailed area-specific planning in the relevant directory and link to it here when useful. + +## Proposed ideas + +No ideas recorded yet. + +## Candidates + +No candidates recorded yet. Candidates are under consideration, not commitments. + +## Confirmed + +No features have been recorded as confirmed. Add an item here only after approval; put the decision and rationale in [decisions/](decisions/). diff --git a/plan/README.md b/plan/README.md new file mode 100644 index 0000000..c877ad4 --- /dev/null +++ b/plan/README.md @@ -0,0 +1,21 @@ +# Planning + +This directory contains Moorly Mail's modular planning documents. Keep ideas and candidates distinct from confirmed decisions; a proposal is not an approval. Record approved choices in [decisions/](decisions/) and link to them rather than repeating them elsewhere. + +## Areas + +- [GUI](gui/README.md) — interface concepts, interaction patterns, and visual direction. +- [Architecture](architecture/README.md) — product-wide structure and architectural questions. +- [Crates](crates/README.md) — Rust crate options and responsibilities; listing a crate here does not approve its use. +- [Email](email/README.md) — email behavior, workflows, and protocol-related product requirements. +- [Security](security/README.md) — security goals, considerations, and open questions. +- [Risks](risks/README.md) — project risks, assumptions, and potential mitigations. +- [Roadmap](roadmap/README.md) — possible sequencing and milestones. +- [Decisions](decisions/README.md) — approved decisions and their rationale. + +## Planning documents + +- [01 — Vision](01-VISION.md) — product purpose and direction. +- [02 — Features](02-FEATURES.md) — feature ideas and their current status. + +Keep documents focused on their area. Link to the source document when information is relevant elsewhere instead of copying it. Do not add detailed technical specifications until they are requested and the relevant direction is approved. diff --git a/plan/architecture/README.md b/plan/architecture/README.md new file mode 100644 index 0000000..bfaeb61 --- /dev/null +++ b/plan/architecture/README.md @@ -0,0 +1,3 @@ +# Architecture + +Track product-wide architectural questions and proposals here. Do not treat a proposal as an approved design; record approved decisions in [decisions](../decisions/). diff --git a/plan/crates/README.md b/plan/crates/README.md new file mode 100644 index 0000000..a1d441d --- /dev/null +++ b/plan/crates/README.md @@ -0,0 +1,3 @@ +# Crates + +Track Rust crate candidates and their possible responsibilities here. Mentioning a crate is not an endorsement or a final dependency choice; record approved choices in [decisions](../decisions/). diff --git a/plan/decisions/README.md b/plan/decisions/README.md new file mode 100644 index 0000000..171a269 --- /dev/null +++ b/plan/decisions/README.md @@ -0,0 +1,5 @@ +# Decisions + +This area is the source of truth for explicitly approved decisions and their rationale. Keep proposed ideas and candidates in their respective planning documents; link here only when a choice is approved. + +No decisions recorded yet. diff --git a/plan/email/README.md b/plan/email/README.md new file mode 100644 index 0000000..ae8ad8e --- /dev/null +++ b/plan/email/README.md @@ -0,0 +1,3 @@ +# Email + +Plan email-related product behavior, workflows, and requirements here. Keep detailed specifications scoped to this area and link to shared decisions rather than duplicating them. diff --git a/plan/gui/README.md b/plan/gui/README.md new file mode 100644 index 0000000..c8bf990 --- /dev/null +++ b/plan/gui/README.md @@ -0,0 +1,3 @@ +# GUI + +Plan interface concepts, interaction patterns, and visual direction here. Separate proposals from approved decisions and link to relevant [decision records](../decisions/). diff --git a/plan/risks/README.md b/plan/risks/README.md new file mode 100644 index 0000000..4fc0d28 --- /dev/null +++ b/plan/risks/README.md @@ -0,0 +1,3 @@ +# Risks + +Track project risks, assumptions, and potential mitigations here. Link to related area documents instead of repeating their content. diff --git a/plan/roadmap/README.md b/plan/roadmap/README.md new file mode 100644 index 0000000..982e71d --- /dev/null +++ b/plan/roadmap/README.md @@ -0,0 +1,3 @@ +# Roadmap + +Track possible sequencing and milestones here. Treat roadmap items as proposals until approved; link to the relevant feature and decision documents. diff --git a/plan/security/README.md b/plan/security/README.md new file mode 100644 index 0000000..57a725a --- /dev/null +++ b/plan/security/README.md @@ -0,0 +1,3 @@ +# Security + +Track security goals, considerations, and open questions here. Keep proposals distinct from confirmed requirements and decisions.