mail relay configured

docs/ROADMAP.md

@@ -4,7 +4,7 @@ What the Mechanical Compiler is for, and the order in which it gets built.
 
 | | |
 |---|---|
-| Updated | 2026-08-16 |
+| Updated | 2026-08-17 |
 | Companions | `ENVIRONMENT.md`, `STAGING-STATE.md`, `FAILURES.md` |
 
 ---
@@ -127,6 +127,8 @@ a new call into the same machinery, not a new machine.
   explicit disk monitoring are deferred; backup strategy is postponed by
   operator decision; application deployment remains blocked on application
   code. See `STAGING-STATE.md`.
+- **Mail alerting accepted, 2026-08-17.** Delivered end to end and received
+  twice. `smartd` is now unblocked. One open exposure is recorded as F-025.
 
 ### Next — the port
 
@@ -246,3 +248,9 @@ on whether it makes distributed manufacturing capacity legible.
 8. **Handoff is not delivery.** An upstream acceptance code proves the message
    left, not that it arrived (F-023). The same distinction applies wherever a
    subsystem reports success on behalf of something downstream.
+9. **Record what a change grants, not only what it repairs.** A trust rule
+   added to fix one rejection may authorise far more than the case that
+   prompted it (F-025).
+10. **Shared infrastructure is not ours to reconfigure.** An instance may
+   configure its own client side; changes further down the chain are escalated
+   with evidence.