export declare const TRAFFIC_STRATEGY = "# /traffic-strategy \u2014 Traffic Strategy Engine\n\n## What This Does\n\nAnalyzes your market, buyer, campaign assets, and budget to create a channel-specific traffic strategy.\n\n## Trigger Context\nAfter Campaign Deployment Engine has produced assets. Assets exist but no traffic is flowing yet.\n\n## Prerequisites\n- Campaign assets built (landing pages, emails, ad copy from /deploy)\n- Buyer Research Package (personas, awareness level, sophistication level)\n- Platform Decision (from /platform)\n- Product Blueprint (from /product)\n- User-provided budget constraint (ask if not provided)\n\n## Execution Protocol\n\n**DELEGATE TO SUBAGENT: `traffic-agent` (task_type: \"traffic_strategy_research\")**\n\n### Step 0: Gather inputs\nCollect and pass to subagent:\n- Building Blocks document (`assets/[market-name]/building-blocks/building-blocks.md`)\n- Buyer Research Package (`assets/[market-name]/research/buyer-research-package.md`)\n- Unit Economics guardrails (from `pipeline-state.json`)\n- Platform decision (`assets/[market-name]/research/platform-decision.md`)\n- Dream 100 data (if `/dream-100` has run: `assets/[market-name]/traffic/dream-100/dream-100-analysis.md`)\n- User-provided budget constraint (ask if not provided)\n\n### Step 1: Invoke traffic-agent subagent\nThe subagent will run 5-8 web searches for channel benchmarks, score channels across 5 dimensions, allocate budget via 70/20/10 rule, set KPI targets, and define the testing sequence.\n\n### Step 2: Receive and save output\nThe subagent returns the Traffic Strategy Document. Save to `assets/[market-name]/traffic/traffic-strategy.md`.\n\nThe document must include these EXACT deliverables:\n\n **A. Channel Scorecard** \u2014 completed matrix with numerical scores and evidence for each dimension. Include an **Organic** row scoring organic search/content as a channel (Buyer Presence, Intent Strength, Creative-Channel Fit, Cost Efficiency, Scalability). This row is informational \u2014 organic runs parallel via `/content-engine`, not competing for paid budget.\n\n **B. Budget Allocation Table (copy-paste ready):**\n ```\n MONTHLY BUDGET: $[total] (PAID CHANNELS ONLY)\n\n PROVEN (70%): [Channel] $[amount]/month $[amount]/day\n TESTING (20%): [Channel] $[amount]/month $[amount]/day\n EXPERIMENT (10%): [Channel] $[amount]/month $[amount]/day\n\n ORGANIC (parallel \u2014 no budget allocation, runs via /content-engine):\n Status: [active/not started]\n Channel: SEO + AI citations\n Monthly cost: $0 (time investment only)\n Expected timeline: 3-6 months to compound\n ```\n\n **C. KPI Target Card (reference during every analytics review):**\n ```\n TARGET METRICS:\n Break-even CPA: $[exact number] (= offer price \u00D7 margin threshold)\n Target CPA: $[exact number] (= break-even \u00D7 0.7 for profit margin)\n Target ROAS: [X.X]x minimum\n CTR floor: [X.X]% (below this = kill creative)\n Landing page conv rate target: [X]%\n Daily conversion target: [X] sales/day at $[budget]/day\n ```\n\n **D. Testing Sequence (week-by-week launch plan):**\n ```\n WEEK 1: Launch [channel] with [X] creative variations at $[X]/day each\n Kill threshold: [specific metric and number]\n Advance threshold: [specific metric and number]\n WEEK 2: Advance winners to validation. Launch [X] new variations.\n Start [testing channel] with [X] variations at $[X]/day.\n WEEK 3: Scale validated winners. Analyze testing channel signal.\n WEEK 4: Full analytics review. Rebalance 70/20/10 if needed.\n ```\n\n Save to `assets/[market-name]/traffic/traffic-strategy.md`\n\n7. **Update pipeline-state.json** with traffic strategy data.\n\n## Autonomy\nTier 2 \u2014 Notify & Proceed for strategy creation.\nTier 3 \u2014 Recommend & Wait for budget decisions above $100/day.\n\n## Next Step\n`/channels` to set up campaigns, or `/creative-test` to begin testing."; //# sourceMappingURL=traffic-strategy.d.ts.map