docs: clarify mailbox packet flow

minions/mail/README.md

@@ -42,6 +42,15 @@ Examples:
 4. gate owner records verdict if needed
 5. `PM` mirrors durable state into shared docs and same-day chat summary
 
+## ASCII Flow
+
+```text
+sender        -> opens packet -> writes request.md
+recipient     -> reads request -> writes response.md
+gate owner    -> reviews       -> writes verdict.md (if needed)
+PM            -> curates       -> updates shared docs + daily chat summary
+```
+
 ## Staged Rollout Rule
 
 - already-open legacy chat packets may remain where they are until they close

minions/mail/packet-template.md

@@ -16,26 +16,6 @@ DECISION:
 RATIONALE:
 
 ACTION NEEDED:
-
-### AM
-
-No action needed yet.
-
-### CM
-
-No action needed yet.
-
-### SM
-
-No action needed yet.
-
-### OM-Test / OM
-
-No action needed yet.
-
-### Operator
-
-No action needed until the response is reviewed.
 ```
 
 ## `response.md`

minions/roles/AM.md

@@ -20,7 +20,9 @@ project.
 - provide CM with clear design constraints and rationale for implementation work
 - work with SM so architecture and design choices rest on solid security foundations
 - incorporate OM-Test / OM runtime feedback when architecture or design is not meeting project goals
-- keep architecture decisions durable in plans, docs, or chat the same day they change
+- keep architecture decisions durable in plans, docs, or owned mail packets the
+  same day they change and ensure `PM` has enough context for a same-day
+  summary
 
 ## Outputs
 

minions/roles/CM.md

@@ -18,7 +18,8 @@ PM, AM, and the operator.
 - implement within the approved architecture and surface design pressure early
 - add or update tests when behavior changes
 - report technical findings clearly
-- mirror milestone-relevant progress into chat the same day
+- make milestone-relevant progress durable in owned mail packets the same day
+  and ensure `PM` has enough context for a same-day summary
 - distinguish between:
   - code merged
   - code deployed