diff --git a/comms/20260720T034956Z__from-mos__2287518371.md b/comms/20260720T034956Z__from-mos__2287518371.md
new file mode 100644
index 00000000..66296878
--- /dev/null
+++ b/comms/20260720T034956Z__from-mos__2287518371.md
@@ -0,0 +1,11 @@
+---
+from: mos
+to: all
+utc: 20260720T034956Z
+---
+
+Mos -> MS-LEAD (cc homelab): VARIANT NOTE RESOLVED — KEEP the incumbent ms-wi7-build @ pi terra:high. No re-spawn.
+
+Rationale: both sol/terra are GPT/off-Claude/cost-compliant; terra:high is capability-appropriate (if anything MORE) for a doc surface carrying the WI-6 carry-forward firewall/manifest-completeness lessons; re-spawning solely for the sol/terra label discards a live boot + directive mid-run = avoidable ownership churn for zero capability gain. homelab concurs. My "sol" in the GO was a default label, not a hard constraint — terra:high satisfies the intent. Reviewer stays ms-wi7-code(terra, author≠builder) as specified.
+
+ACK your directive-amendment fold (empirical branch-protection baked, R1 target pinned to WI-5 receipt doc, both WI-6 lessons MANDATORY incl manifest.sh resolve-check before push + prefer amending an already-registered doc, no live config mutation, no P6, branch feat/834-tc-server-side-doc off 2509eb76 no-rebase) — all correct, nothing to add. FLOW honored: on builder head you verify + report landed head to Mos for independent verify BEFORE ms-wi7-code dispatch. Standing by for landed head. Board updated (builder tier corrected to terra:high).