/synthesis-build

name: synthesis-build
description: Synthesis BUILD stage — the FINAL stage of the Diffmode growth-tactics pipeline (fuses white-space ideation + founder-fit adaptation & merge — formerly two separate synthesis passes — into ONE reviewer-gated stage). Reads synthesis-explore.md (the validated emergent mechanisms) + synthesis-constraints.json + growth-factors.json + founder-input + audience-jtbd + competitors-analysis + the 3 think-tank reports + the bundled 2026 channel menu. Phase 1 IDEATES white-space tactics IGNORING constraints; Phase 2 adapts them for founder constraints (preserving the unconventional core) + generates synergy/founder-fit tactics; Phase 3 merges into a final synthesis.md of 7-9 novel demand-gen tactic ideas (target 50%+ unconventional). Uses the lite anti_patterns (NOT a proprietary anti-vectors DB). The free plugin STOPS here.
metadata:
  version: "1.0.0"

Synthesis — Build (Phase 1 White Space → Phase 2 Founder Fit → Phase 3 Merge) — FINAL stage

This is the **last stage of the free pipeline.** It fuses three jobs that MUST stay ordered:

1. **Phase 1 — IDEATE (white space):** write 4-5 genuinely unconventional white-space tactics in full, **IGNORING founder constraints** (exploration mode). 2. **Phase 2 — ADAPT & GENERATE (founder fit):** review the Phase-1 tactics and adapt for founder constraints **preserving the unconventional core**, then generate 4-5 more from the synergy + founder-fit pools. 3. **Phase 3 — MERGE:** merge into a final synthesis of **7-9 total tactics** (target 50%+ unconventional).

It produces a portfolio of novel demand-gen tactic IDEAS and **stops**. (Prioritization, implementation guides, and the proprietary 576-vector DB are the paid product — do not attempt them here.)

Vector definitions come from `growth-factors.json`; pools/anti-patterns from `synthesis-constraints.json`; the validated emergent mechanisms come from `synthesis-explore.md`. Do NOT read `tactics_DB/` (clean-room — no proprietary anti-vectors DB; use the lite `anti_patterns` field instead).

The three phases are WALLED — do them strictly in order

**You MUST write the Phase-1 white-space tactics in FULL before you adapt anything in Phase 2.** You have **NOT earned the right to reject a tactic for impracticality during Phase 1** — that is Phase 2's job. The output PROVES the ordering held: the `## Pass 1 Disposition` table (Phase 2) can only dispose tactics that Phase 1 already wrote in full. If you catch yourself filtering a Phase-1 tactic for "the founder can't do this," STOP — that belongs in Phase 2.

Inputs & Output

• `WS/03-think-tanks/demand-generation/synthesis-explore.md` (PRIMARY — the validated emergent

mechanisms + blind combinations; Phase 1 ideates from these + `diverse_white_space`)

• `WS/03-think-tanks/demand-generation/synthesis-constraints.json` (`diverse_white_space`; pools

`B_synergy` + `C_founder_leverage`; `anti_patterns`; `category_diversity_requirements`)

• `WS/03-think-tanks/demand-generation/growth-factors.json` (vector definitions)
• `WS/01-diagnostics/founder-input.md` (Phase 1 READS but does NOT filter by constraints; Phase

2 applies them; goal + deadline)

• `WS/02-enrichment/audience-jtbd.md`, `WS/02-enrichment/competitors-analysis.md`
• Think-tank context: `competitor-gaps.md`, `platform-arbitrage.md` (channel selection,

structural advantage), `cross-industry.md` (transferable mechanisms / adaptation angles for the new Phase-2 synergy + founder-fit tactics)

• `${CLAUDE_PLUGIN_ROOT}/reference/Marketing-Channel-Menu-2026.md` (bundled channel menu)
• **OUTPUT**: `WS/03-think-tanks/demand-generation/synthesis.md`

═══════════════════════════════════════════════════════════════════════════

PHASE 1 — IDEATE (white space; IGNORE founder constraints)

═══════════════════════════════════════════════════════════════════════════

Generate **4-5 tactics exclusively from diverse white-space combinations** — vector pairs that are novel for this run and exclude over-represented "content-flywheel"-type vectors. **This phase prioritizes unconventional exploration over practicality and IGNORES founder constraints** (Phase 2 applies them).

Philosophy: Exploration Mode

Mindset: "What interesting mechanisms emerge from these never-combined vectors?" / "What would a founder do with unlimited resources?" — NOT "can this founder do this?" The goal is to discover unconventional approaches Phase 2 can refine or preserve. **Write all 4-5 tactics in FULL here, before any adaptation.**

Scope Enforcement — DEMAND GENERATION ONLY

Before generating ANY tactic: "Does this bring NEW PEOPLE to the site who've never heard of the product?" YES = include; NO = delete (CRO territory).

**Engineering-as-marketing: allowed but scoped.** Building things to ATTRACT new users is valid demand gen, but the tactic's PRIMARY purpose must be acquisition, not product improvement. Test: if you removed the distribution/acquisition channel, would the remaining work be on the product roadmap anyway? If YES → not demand gen.

| Tactic type | Verdict | |-------------|---------| | Build-to-attract (80% distribution / 20% build) | ✅ Demand gen | | Product improvement with marketing framing | ❌ Product dev | | Improve onboarding / re-engage churned / upsell existing | ❌ CRO / Retention |

Process (Phase 1)

1. **Load diverse white space** from `synthesis-constraints.json` (`diverse_white_space`). These are pre-filtered to exclude content-flywheel-type vectors and limit repetition (max 2 per anchor). Display the loaded pairs in a table. **Category awareness:** aim for ≥2 different category prefixes across your 4-5 tactics (soft target here; Phase 2 applies the per-prefix minimums from `category_diversity_requirements`, which are built to be satisfiable within 7-9 tactics of 2-3 vectors — if a minimum is still unreachable, say so explicitly in the disposition rather than silently missing it). 2. **For each combination, derive the e