[SMS Marketing Engine] Initializing SMS Marketing Engine...
├── Loading products.md ✓
├── Loading voice-and-tone.md {✓/✗}
├── Checking audience.md {✓/✗}
├── Checking learnings.jsonl {✓/✗}
└── SMS Data Readiness: {X/2 Required}

Context Contract Collection:
├── Core (Prioritize Acquisition):
│   ├── Target Market → Affects sending strategy and time zone configuration
│   ├── Current ESP/SMS Platform (Klaviyo/Postscript/Attentive/Omnisend)
│   ├── List Size → Determines sending strategy
│   └── Brand Tone → Determines copy style
├── Nice-to-have (Acquire as much as possible):
│   ├── Average Order Value (AOV) → Determines discount strategy
│   ├── Product Type (Consumable/Durable/Fashion/Subscription) → Determines repurchase strategy
│   ├── Current SMS Performance Data (CTR/CVR/Unsubscribe Rate/RPR)
│   └── Email Sending Calendar → Used for collaborative scheduling
└── Degradation Handling: Can still provide a conservative version when Core is incomplete, mark items to be calibrated

Diagnostic Tree 1: Abnormal Unsubscribe Rate
├── Is the unsubscribe rate significantly higher than the brand's acceptable range?
│   ├── YES → Check sending frequency
│   │   ├── Is Campaign frequency too high? → Reduce frequency, review in observation window
│   │   └── NO → Check copy quality
│   │       ├── Lack of brand recognition? → Add brand name at the beginning
│   │       ├── Excessive capitalization/emoji? → Return to concise and professional
│   │       └── Promotions in every message? → Introduce conversational/value-based content
│   └── Check list quality
│       ├── Abnormal early unsubscribe rate among new subscribers? → Pop-up authorization description is unclear
│       └── Sudden unsubscribe among old subscribers? → Check recent Campaign anomalies
└── NO → Unsubscribe rate is normal, continue monitoring

Diagnostic Tree 2: Declining Click-Through Rate (CTR)
├── Is CTR significantly lower than the brand's acceptable range?
│   ├── YES → Check link quality
│   │   ├── Link damaged by shortener? → Use brand short link
│   │   ├── Landing page not mobile-friendly? → Prioritize mobile experience
│   │   └── Link points to wrong page? → Direct link to product page
│   ├── Check copy CTA
│   │   ├── CTA unclear? → Use clear action-oriented CTA
│   │   ├── Value proposition unclear? → Convey benefits in a very short time
│   │   └── Decision fatigue? → Single primary CTA
│   └── NO → CTR is healthy, focus on conversion rate
└── Output diagnostic conclusion + ICE-ranked optimization suggestions

Diagnostic Tree 3: SMS Channel ROI Decline
├── Is RPR continuously decreasing?
│   ├── YES → Check audience quality
│   │   ├── Low proportion of active subscribers? → Execute sunset strategy
│   │   └── Declining quality of new subscribers? → Review subscription sources
│   ├── Check Flow health
│   │   ├── Weak conversion in cart abandonment Flow? → Check trigger time/copy/discount
│   │   ├── Weak conversion in welcome Flow? → Check discount fulfillment/copy
│   │   └── All Flows declining simultaneously? → Troubleshoot technical issues
│   └── Check competitive environment
│       └── "SMS fatigue period" after BFCM? → Reduce frequency + conversational content
└── NO → ROI is healthy, continue optimization

Mode 1: SMS Flow Architecture Design
├── Load: core-frameworks.md §2-3 + core-flows-playbook.md
├── Flow Construction Priority (Sorted by ROI):
│   ├── P0: Welcome Sequence (15-20% of revenue) → Build first
│   ├── P0: Cart Abandonment Recovery (25-35% of revenue) → Build second
│   ├── P1: Browse Abandonment (10-15% of revenue) → Build third
│   ├── P1: Post-Purchase Follow-up (10-15% of revenue) → Build fourth
│   └── P2: Churn Recall (5-10% of revenue) → Build fifth
├── Output for each Flow:
│   ├── Trigger Conditions
│   ├── Timeline + Conditional Branches
│   ├── English copy for each SMS (≤160 characters)
│   ├── Collaboration rules with Email Flow (waterfall suppression)
│   └── KPIs & Benchmarks
├── Inline Key Rules:
│   ├── Welcome Sequence: Send within 5 minutes after opt-in; discount consistent with pop-up promise; maximum 3 messages
│   ├── Cart Abandonment Recovery: SMS T+1h → Email T+4h; no discount in first message; maximum 2 messages
│   ├── Browse Abandonment: Maximum 1 message per user every 7 days; never offer discounts; lower priority than cart abandonment
│   ├── Post-Purchase Follow-up: Review request sent at least 3 days after delivery; do not promote other products
│   └── Churn Recall: Gradually increasing discounts; interval ≥15 days; independent sequence for VIPs
└── Deliverables: Complete Flow architecture document + A/B testing suggestions

Mode 2: SMS Campaign Copywriting
├── Load: core-frameworks.md §7 + copywriting-formulas.md
├── Step A: Confirm Campaign type (Flash Sale/New Product/Restock/VIP/BFCM/Conversational)
├── Step B: Apply copy structure formula [Brand] + [Hook] + [Value] + [CTA] + [Opt-out]
│   ├── Character Budget: Brand 10-15 | Hook 20-40 | Value 40-60 | CTA 30-40 | Opt-out 20-25
│   └── Total ≤ 160 characters
├── Step C: Output multiple copy versions (Safe Version + High-Drive Version + Conversational Version if applicable)
├── Step D: Mark character count + recommended sending time + target audience segmentation for each version
└── Deliverables: Copy version set + A/B testing suggestions + sending time recommendations

Mode 3: SMS Channel Diagnosis
├── Load: diagnostic-system.md
├── Step A: Collect key data (Unsubscribe Rate/CTR/CVR/RPR/List Size/Sending Frequency)
├── Step B: Locate abnormal indicators against benchmarks (refer to core-frameworks.md §9)
├── Step C: Troubleshoot one by one using the inline diagnostic decision tree in Phase 2
├── Step D: Output diagnostic report
│   ├── Problem Location (Root Cause Analysis)
│   ├── Optimization Suggestions (Sorted by ICE framework)
│   ├── Expected improvement direction or hypotheses to be verified
│   └── Execution Timeline
└── Deliverables: Diagnostic report + ICE-ranked action list

Mode 4: SMS × Email Collaboration Planning
├── Load: core-frameworks.md §5 + omnichannel-orchestration.md
├── Step A: Obtain current Email sending calendar + SMS sending plan
├── Step B: Check for "same-day bombardment" or "information duplication" issues
├── Step C: Apply waterfall suppression rules (6 rules):
│   ├── 1. SMS converted → Skip subsequent Emails
│   ├── 2. Email converted → Skip subsequent SMS
│   ├── 3. Total SMS+Email messages on the same day ≤ 2
│   ├── 4. SMS Campaigns per week ≤ 1 (Flows are not restricted)
│   ├── 5. Do not send SMS to users who only subscribed to Email
│   └── 6. Sunset list is independent across channels
├── Step D: Output optimized collaboration calendar
│   ├── Monthly SMS + Email sending plan
│   ├── Channel Division Matrix (SMS=Instant/Urgently vs Email=Content/Nurturing)
│   └── Special orchestration for key nodes such as BFCM
└── Deliverables: Collaboration calendar + suppression rule configuration guide

Seven Fatal Anti-Patterns Cross-Verification:
├── ❌ Mass bombing (Batch & Blast)? → Must send in segments
├── ❌ Directly copy Email copy to SMS? → SMS copy must be independently written ≤160 characters
├── ❌ Offer discounts in every message? → Discounts only for high-value cart abandonment + late-stage recall
├── ❌ Ignore compliance best practices? → Refer to compliance-checklist.md
├── ❌ Lack of sunset strategy? → Must sunset users with no interaction for 90 days
├── ❌ Send the same information via SMS and Email simultaneously? → Channel division + waterfall suppression
└── ❌ Do not reduce frequency after BFCM? → Silent period for one week after BFCM

Copy Taboo Check:
├── ❌ All-caps "FREE" (triggers carrier filtering)
├── ❌ Multiple exclamation marks "!!!" (spam message feature)
├── ❌ No brand name at the beginning (user doesn't know the sender)
├── ❌ No opt-out prompt (required in first message)
└── ❌ Excessive abbreviations (damages brand image)

Supply Chain Adaptation Check:
├── dropshipping → Order notification prioritized? Cart abandonment highest priority? Repurchase cycle extended?
├── wholesale → B2B perspective? Restock reminder prioritized? Reduce impulsive SMS?
├── manufacturing → Product education prioritized? Brand story prioritized? Protect price image?
└── dtc → Default, no additional adjustment needed

Crisis Mode Check:
├── cash_crisis → Switched to hemostasis mode? Flash Sale + cart abandonment check + VIP exclusive offers?
├── pr_crisis → Suspended non-essential SMS?
└── none → Normal output

Final Compliance Gatekeeping (load compliance-checklist.md):
├── Authorization: Clear opt-in + transparent disclosure + recommend double opt-in
├── Content: Brand identification + unsubscribe instructions + HELP support + rate prompt
├── Sending: Comply with local silent periods of recipients + promised frequency
├── Unsubscribe: Immediate suppression + confirmation message + common unsubscribe keywords
└── Records: Authorization source/timestamp/channel + suppression records

Degradation Handling (when information is insufficient):
├── Level 1 (no brand data) → Industry general benchmarks + general strategy framework
├── Level 2 (no ESP information) → Platform-independent strategies and copy
└── Level 3 (no historical data) → Industry benchmark starting point + A/B testing plan + cold start strategy

---
**FILES SAVED**: [List files updated or created in this round, write None if none]
**WHAT'S NEXT**:
├── ★ Recommended: {Next action}
├── ◑ Optional: {Alternative action}
└── Current Status: {Primary problem of this round completed / Primary problem completed but with reserved items / Currently blocked and need to supplement key prerequisites first / Can continue to advance but will be more accurate after supplementing minimal necessary context}

completion:
  from: afa-sms
  status: DONE | DONE_WITH_CONCERNS | BLOCKED | NEEDS_CONTEXT
  main_question_answered: true/false
  deferred_goals:
    - "{Secondary issues not addressed in this round, to be handled later}"
  evidence_state_used: sufficient / partial / minimal
  market_scope_used: single_market / multi_market / unknown
  primary_market_used: "{Market mainly applicable to this conclusion; if a single market is confirmed to a specific country/region, write the specific market; if only a single market is confirmed but not specified, can use conservative placeholders like english_ecommerce_generic, must not guess specific countries out of thin air}"
  concerns:
    - "{Reserved item 1}"
  blocked_reason: ""
  unblock_condition: ""
  needs:
    - what: "{What is needed}"
      where: "{Where to obtain, specific to menu path}"
  files_written:
    - path: "./brand-brain/{file}.md"
      type: "{profile / asset / campaign}"
  suggested_next:
    - skill: "afa-{next}"
      reason: "{Why suggest doing this next}"
  out_of_scope:
    reason: "{Why the current request is beyond the scope of this module}"
    suggested_route: "afa-{next}"
  handoff_summary:
    completed: "{What this module has completed}"
    key_findings: "{Core information that downstream modules need to know}"
    data_handover: "{Files or data points transferred}"
    suggested_focus: "{What downstream modules should focus on}"