docs(cmo): add ecosystem marketing brief and mission-alignment policy gates

Author: ccross2

ops/cmo-automation/README.md

@@ -31,6 +31,7 @@ Structure
 - scripts/execute_approved_queue.py
 - reports/CMO-AUTOMATION-IMPLEMENTATION-PLAN.md
 - reports/CMO-CUTOVER-48H-RUNBOOK.md
+- reports/CMO-ECOSYSTEM-MARKETING-BRIEF.md
 
 Quick start
 1) Export credentials (or source ~/.claude/secrets.env)

ops/cmo-automation/config/operating_policy.json

@@ -73,6 +73,26 @@
       "tone": "relevant_and_interesting"
     }
   },
+  "cmo_alignment": {
+    "category": "structural_trust_infrastructure",
+    "ecosystem_scope": [
+      "Sovren Software",
+      "Esver OS",
+      "Mr Haven",
+      "Engram",
+      "Dendrite"
+    ],
+    "message_relevance_gate": {
+      "must_map_to_at_least_one": [
+        "mission",
+        "product_capability",
+        "roadmap_milestone",
+        "verification_proof"
+      ],
+      "disallow_generic_hot_takes": true,
+      "disallow_unanchored_trend_chasing": true
+    }
+  },
   "risk_controls": {
     "max_replies_per_hour_per_account": 8,
     "max_replies_to_same_user_per_24h": 1,

ops/cmo-automation/reports/CMO-ECOSYSTEM-MARKETING-BRIEF.md

@@ -0,0 +1,81 @@
+# CMO Ecosystem Marketing Brief
+
+Date: 2026-04-02
+Scope: Sovren Software ecosystem messaging for X operations
+Status: Active reference
+
+## Why this brief exists
+This brief aligns all outbound messaging with the mission, architecture, and roadmap across Sovren Software, Esver OS, Mr Haven, Engram, and Dendrite.
+
+## Sources reviewed
+- /home/ccross/cDesign/sovren-website/README.md
+- /home/ccross/cDesign/mr-haven/docs/MR_HAVEN_OVERVIEW.md
+- /home/ccross/cDesign/mr-haven/docs/proposals/ROADMAP_COHESION_REPORT.md
+- /home/ccross/cDesign/esver-os/docs/MISSION.md
+- /home/ccross/cDesign/esver-os/docs/vision/MASTER-ROADMAP.md
+- /home/ccross/cDesign/esver-os/README.md
+- /home/ccross/cDesign/dendrite/Strategy/Campaigns/UNIFIED-MARKETING-ROADMAP.md
+- /home/ccross/cDesign/dendrite/Strategy/Campaigns/Three-Account-Orchestration.md
+- /home/ccross/cDesign/dendrite/Strategy/Campaigns/Mission-Alignment-Analysis-2026-02-05.md
+- /home/ccross/cDesign/dendrite/Strategy/Architecture/Engram-Dendrite-v3-Architecture-2026-04-01.md
+- /home/ccross/.engram/.claude/core/MISSION.md
+- /home/ccross/.engram/.claude/notes/sovren-website/context.md
+
+## Strategic foundation
+1) Category
+- Structural trust infrastructure, not a generic AI app, security theater, or feature bundle.
+
+2) System thesis
+- Agents are actors, not tools.
+- Trust is enforced by architecture, not policy copy.
+- Governance primitives repeat across layers: identity, capability, intent, receipt.
+
+3) Product architecture in market language
+- Esver OS: governance-first substrate for human-AI coordination.
+- Mr Haven: continuity and verifiable coordination protocol.
+- Engram + Dendrite: control-plane/data-plane memory and knowledge infrastructure.
+- Sovren Software: ecosystem that integrates these into one accountable operating model.
+
+4) Narrative constraints
+- Claims must be defensible against running systems and documented architecture.
+- Avoid promising beyond current implementation maturity.
+- Keep convergence narrative coherent across all accounts.
+
+## Account-level messaging intent
+- @sovren_software: thesis, architecture, milestones, category narrative.
+- @mrhaven_agent: concrete proof posture, verifiable outcomes, grounded operational commentary.
+- @TheCesarCross: founder context, strategic synthesis, conviction with specificity.
+
+## Hard editorial rules for generated copy
+- No exclamation marks
+- No emojis
+- No em dash or en dash
+- Relevant and interesting over generic engagement
+- Every post/reply should map to at least one of:
+  - mission
+  - product capability
+  - roadmap milestone
+  - verification proof
+
+## Relevance test before publishing
+A message passes only if it answers at least one:
+- What are we building
+- Why this matters
+- What changed materially
+- What proof supports the claim
+
+## Content anti-patterns
+- Generic AI hot takes with no product anchor
+- Trend chasing detached from Sovren mission
+- Vague inspiration copy without technical or operational substance
+- Overclaiming future capabilities as present state
+
+## Operational directives for CMO automation
+- Prefer fewer, higher-signal engagements.
+- Prioritize threads and posts that discuss agent accountability, governance, verification, coordination infrastructure, cryptographic trust, or operational reliability.
+- Founder account keeps strict deny-list filtering and strategic relevance gate.
+- Quote or reply only when there is a clear narrative bridge to Sovren ecosystem goals.
+
+## Review cadence
+- Weekly: recalibrate messaging pillars against active roadmap milestones.
+- Monthly: refresh this brief from latest docs in esver-os, mr-haven, and dendrite strategy folders.