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/ and link to them rather than repeating them elsewhere.
Areas
- GUI — interface concepts, interaction patterns, and visual direction.
- Architecture — product-wide structure and architectural questions.
- Database — data requirements, candidates, and database-specific considerations.
- Crates — Rust crate options and responsibilities; listing a crate here does not approve its use.
- Email — email behavior, workflows, and protocol-related product requirements.
- Authentication — authentication concepts, provider-specific planning, and credential-storage questions.
- Security — security goals, considerations, and open questions.
- Risks — project risks, assumptions, and potential mitigations.
- Roadmap — possible sequencing and milestones.
- Decisions — approved decisions and their rationale.
Planning documents
- 01 — Vision — product purpose and direction.
- 02 — Features — 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.