Structured plan folder

This commit is contained in:
Squid committed 2026-11-18 18:44:18 +01:00
1 parent 3b213f4a48
commit e17961e49e
11 files changed
+80

No files matched your search

+18
View File
@@ -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/).
+15
View File
@@ -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/).
+21
View File
@@ -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.
+3
View File
@@ -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/).
+3
View File
@@ -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/).
+5
View File
@@ -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.
+3
View File
@@ -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.
+3
View File
@@ -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/).
+3
View File
@@ -0,0 +1,3 @@
# Risks
Track project risks, assumptions, and potential mitigations here. Link to related area documents instead of repeating their content.
+3
View File
@@ -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.
+3
View File
@@ -0,0 +1,3 @@
# Security
Track security goals, considerations, and open questions here. Keep proposals distinct from confirmed requirements and decisions.