Supervisor: afa-monetize · Version: v2.4.7

• Requires:

  products.md

• Optional:

  audience.md

  ,

  learnings.jsonl

  ,

  offers.md

  ,

  brand-master.md

• Never: Customer personal identifiable information (PII), unmasked purchase records

System Protocol Loading: Before executing any task, strictly comply with the global protocols in the

_system/

directory.

• Follow

  _system/interaction-protocol.md

  for workflow confirmation and cross-module collaboration.
• Follow

  _system/output-format.md

  for four-section output and report visualization.
• Follow

  _system/degradation-rules.md

  to handle insufficient information or offline environments.
• Follow

  _system/localization-rules.md

  for target market localization adaptation.
• Follow

  _system/edge-cases.md

  to handle boundary cases and Level 0 requirements.
• Follow

  _system/preamble.md

  for initialization checks and rule priority determination.

[User Retention Engine] Initializing retention engine...
├── Loading products.md ✓
├── Checking audience.md {✓/✗}
├── Checking learnings.jsonl {✓/✗}
├── Checking offers.md {✓/✗}
└── Retention data readiness: {X/1 Required}

1. Load

   references/anti-patterns.md

   to perform boundary check:
   • If the user's core problem belongs to email/SMS copywriting, landing page conversion, dashboard building, customer acquisition cost, or average order value strategy → hand over to the upper layer via

     completion.out_of_scope

     .
   • If it matches the responsibilities of this module → enter Phase 2.
2. Collect the context contract defined in §1 of

   references/work-modes-and-templates.md

   (brand name / product category / monthly order volume / business stage + optional: repurchase rate / LTV:CAC / churn rate / AOV / subscription mode / loyalty program / seasonal mode / cohort data).

1. Load

   references/core-frameworks.md

   to obtain the underlying frameworks required for execution:
   • Five-dimensional retention health check: Repurchase behavior / Customer value / Churn pattern / Interaction health / Retention economics
   • RFM+JTBD+LTV integrated segmentation (11 major customer group matrix): Determines "who to target and what to do"
   • Six-stage customer lifecycle: Determines "when to act"
   • Profit-eroding-free LTV growth model: Ensures strategies do not erode gross profit
2. Execute the SOP according to the selected working mode and apply the corresponding output template in

   references/report-templates.md

   .
3. Load in-depth references as needed:

   • rfm-ltv-framework.md

     → RFM scoring model and grouping method

   • loyalty-program-playbook.md

     → Loyalty program design

   • subscription-management.md

     → Subscription churn prevention

   • win-back-workflows.md

     → Win-back sequence templates

   • cohort-analysis-guide.md

     → Cohort analysis method
4. If

   seasonal_mode = off_season

   → Load the off-season retention strategy section in

   work-modes-and-templates.md

   . If

   crisis_mode = cash_crisis

   → Shift to low-cost high-return actions (cost-free care emails, precise win-back of high-intention groups).

references/anti-patterns.md

• 7-ban cross-validation (including discount guardrail rules)
• Degradation strategy (Level 1-3): Conservative output rules when information is insufficient
• Dropshipping adaptation: Special retention strategies under supply chain mode
• Retention metrics must be benchmarked against category benchmarks (refer to

  benchmark-data.md

  )

_system/context-matrix.md

market_scope_used

primary_market_used

completion:
  from: afa-retain
  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, use a conservative placeholder like english_ecommerce_generic, do not guess a specific country out of thin air}"
  concerns:
    - "{Reservation 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 this is recommended as the next step}"
  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}"

• As long as a conservative executable version can be provided, prefer not to use

  BLOCKED

  .
• If the primary question has been answered but there are still reservations, prefer to use

  DONE_WITH_CONCERNS

  .
• If the current request is truly out of scope, it must be handed back to the upper layer in a structured way via

  completion.out_of_scope

  (fill in

  reason

  and

  suggested_route

  ), instead of just verbally stopping in the body.

• primary_market_used

  must be consistent with the market truly applicable to this conclusion, do not mechanically copy the input field.

• All action plans are sorted by ICE score
• Each strategy is attached with cost tags (budget/time/skill)
• Retention metrics must be benchmarked against category benchmarks
• Cohort data analysis must be marked with seasonal adjustments
• Discount suggestions must comply with discount guardrail rules
• Append new lessons discovered during this execution to

  learnings.jsonl

  in JSONL format, complying with the data structure definition in Chapter 9 of

  _system/brand-memory-protocol.md

  . Follow the silent capture protocol in Chapter 5 of

  _system/interaction-protocol.md

  when writing.