ADR 0035: Rules menu and cross-provider folder moves

Status

Accepted

Context

Sprint 15a and Sprint 15b are one increment. The approved mail-client design package is the requirements baseline. Intake text that says the sprints stay unstarted is not the behavior. Settings and Health was the engineering page. The liquid-glass mail client is the screen. Change iCloud mail is not part of that screen.

Jason named domain and sender maps, approve a sender, block by domain and by sender, and classify-all from a selected message. He did not name a winning rule when those maps disagree, other match fields, importance levels, type values, a numeric accuracy bar, a model, or a standard Outlook rule list. He also did not name which folders are the correct ones, which service receives which folder, or whether initial setup repeats.

He did say a folder can move from one provider to another, and that drag and drop arranges the tree and performs that move. Messages are not part of that drag.

Decision

1. Rules live in a menu on the mail ribbon. They are not a pane on the mail screen, not a triage queue, and not placed under Settings. The parent choice stays open.
2. A rule matches a domain or a sender. Actions are approve (sender only), block (domain or sender), or map to a folder he names. No other match field is stored. No catalog is seeded.
3. When a domain map and a sender map name different folders, the message is not moved. It stays findable. Approve and block stay recorded and do not hide the message.
4. The same rules apply when the client opens stored mail and when he runs them over mail already there. Repeating the run does not drop the message.
5. Dragging a folder on the same account rearranges the tree. Dragging it onto another connected account copies the folder and its mail, and the source is retired only after the destination has every message. A failed copy leaves the source mail in place. No provider pair is hard-coded. Messages are not dragged.
6. Initial setup walks folders that already exist and moves a message only into one existing folder his rule already names. It does not invent folder names and it does not choose a repeat schedule.
7. Settings and Health redirects to the mail client. Send stays off. iCloud stays read-write. The Change iCloud mail form is not on the client, Accounts, or a conversation.

Alternatives

• Seed Outlook rules so the section is not empty — rejected. He has not named them.
• Pick domain-over-sender precedence — rejected. He did not say which rule wins.
• Hard-code Gmail to iCloud as the move — rejected. Any two connected accounts are in scope.
• Keep Settings and Health as the rules page — rejected. That page is not the liquid-glass client.

Consequences

Opening /mail is the client. /inbox/settings and /inbox/mail redirect there. Provider mailbox creation on the remote server is not implied by a stored move; the destination account holds the copied message in Duckbill™ before the source copy is retired. ENABLE_SEND is unchanged.