/governed-mail
The Executive Assistant's rules under governed activities — which mail and calendar acts are proposals (a reply, an external mail, a mailing, a booking with outsiders, a cancellation), which are not (a draft, an internal booking), how to raise one with the draft as the proposal, why only the mailbox owner can sign, and the three rules that carry over unchanged (amend never redraft, isDraft re-read, DraftOnly).
- Instructions: You are acting on a person's mailbox or calendar and something is about to **leave the tenant or cannot be undone** — a reply, a mail to an outsider, a mailing, a booking that invites someone external, a cancellation. In `DraftOnly` you could never send anyway; under governed activities you **propose**, and the person **signs**. The rules are on `Mail/GovernedMail`; this is the procedure. # 1. Decide whether it is an activity - A draft, an internal booking, reading, searching — **not an activity**; do it. - A reply → `mail.reply` · mail to an outside address → `mail.send-external` · several recipients, one text → `mail.mailing` · a booking with an external attendee → `calendar.book` · a cancellation → `calendar.cancel`. **Every one of these is a proposal**, never a send. # 2. Draft first, then propose 1. Write the draft as you do today — `DraftReply` / `DraftMail` (or `PrepareMailing`, `CreateEvent` for a booking held as tentative). Keep the id: it is the proposal's input. 2. `create` a `Governance/Activity` under `Governance/Activities` with the standard, the inputs (`messageId` + `draftId` + a one-line `summary` for a reply; `draftId` + `recipients` for an external mail; `subject`/`attendees`/`start`/`end` for a booking), the `trigger` (the inbound mail's id or the person's request) and a rationale that says **what the message does** in one sentence — the person signs on that sentence and the draft together. 3. Tell the person: *"Drafted; it needs your signature on {activity link} — the draft is in your Drafts as {subject}."* Never *"sent"*. # 3. What only the person can do - **Sign.** The Sign button on the activity page, or their client's Send in `DraftOnly` — either way it is their act. Nothing you write satisfies a `Human()` signature gate. - **Answer a manual gate** (`recipients-checked`, `attendees-checked`) — they confirm the list; you present it clearly (every external address named) so they can. # 4. Corrections - The per…
- Auto mount: yes
- Launches sub thread: no