export declare const TOURNAMENT = "# /tournament \u2014 Parallel Portfolio Tournament Mode\n\n## What This Does\n\nAccepts 3-5 business ideas and runs them through Layer 1 as a competitive batch. Each round produces a comparison table. Users cut losers at each gate. Output: 1-2 funded winners ready for Layer 2 (/name-lock).\n\n## Trigger Context\nUser wants to evaluate multiple ideas simultaneously rather than committing to one. Ideal when:\n- User has 3-5 ideas and can't choose\n- User wants data-driven elimination before investing in deep research\n- User wants to compare unit economics across ideas before committing budget\n\n## Prerequisites\n- No active tournament (check `tournaments` key in pipeline-state.json)\n- If an active tournament exists, present its status and ask: resume or start new?\n\n## Execution Protocol\n\n### Step 0: Collect Ideas\n\nIf user provides ideas inline with the command, parse them. Otherwise ask:\n\n```\nHow many ideas do you want to test? Give me 3-5 market/product ideas.\n```\n\nValidate: minimum 3, maximum 5. If fewer than 3: \"Tournament mode needs at least 3 ideas for meaningful comparison. Use /scout for a single idea.\"\n\n### Step 1: Initialize Tournament State\n\nGenerate slugs for each idea. Create tournament entry in pipeline-state.json:\n\n```json\n{\n \"tournaments\": {\n \"[YYYY-MM-DD]\": {\n \"status\": \"active\",\n \"ideas\": [\"slug-1\", \"slug-2\", \"slug-3\"],\n \"current_round\": \"scout\",\n \"eliminated\": {},\n \"budget_total\": null,\n \"winners\": [],\n \"created\": \"[timestamp]\",\n \"updated\": \"[timestamp]\"\n }\n }\n}\n```\n\nAlso create a minimal pipeline entry under `pipelines` for each idea (same structure as /scout creates), with `current_stage: \"scout\"` and `tournament: \"[tournament-date-key]\"`.\n\nConfirm to user:\n\n```\nStarting tournament with [N] ideas.\n\n 1. [idea-1 slug] \u2014 [brief description]\n 2. [idea-2 slug] \u2014 [brief description]\n 3. [idea-3 slug] \u2014 [brief description]\n ...\n\n\u2550\u2550\u2550 ROUND 1: SCOUT + AUTONOMY \u2550\u2550\u2550\nRunning scout for all [N] ideas...\n```\n\n### Step 2: ROUND 1 \u2014 Scout + Autonomy (All Ideas)\n\nFor each idea sequentially:\n1. Run the /scout SOP (read `.claude/commands/scout.md` and execute for this idea)\n2. Immediately run /autonomy SOP (read `.claude/commands/autonomy.md` and execute)\n3. Save outputs to `assets/[slug]/research/`\n4. Update pipeline-state.json for that idea's pipeline entry\n\nAfter ALL ideas complete, present comparison table:\n\n```\nROUND 1 RESULTS:\n # | Idea | Scout | Autonomy | Verdict\n 1 | [slug-1] | Proceed | 31 HIGH | ADVANCE\n 2 | [slug-2] | Proceed | 24 MOD | ADVANCE\n 3 | [slug-3] | Explore Alt | 18 MOD | BORDERLINE\n 4 | [slug-4] | Proceed | 11 LOW | CUT\n```\n\n**Auto-cut rules:**\n- LOW autonomy (\u226415) \u2192 auto-recommend CUT\n- Scout verdict \"Explore Alternative\" + MOD autonomy \u2192 BORDERLINE\n- All others \u2192 ADVANCE\n\n**Tier 3 decision:** Present cuts and ask user to confirm. User can override any recommendation. Minimum 2 ideas must survive to continue tournament (otherwise it's just a single pipeline).\n\nUpdate eliminated ideas in tournament state:\n```json\n\"eliminated\": {\n \"slug-4\": { \"round\": \"scout\", \"reason\": \"LOW autonomy (11)\" }\n}\n```\n\nUpdate `current_round` to `\"market_intel\"`.\n\n### Step 3: ROUND 2 \u2014 Deep Research (Survivors Only)\n\nFor each surviving idea sequentially:\n1. Delegate to market-researcher subagent (`.claude/agents/market-researcher.md`) \u2014 /market-intel\n2. Delegate to buyer-researcher subagent (`.claude/agents/buyer-researcher.md`) \u2014 /research\n3. Save outputs to `assets/[slug]/research/`\n4. Update pipeline-state.json\n\nAfter ALL survivors complete, present comparison:\n\n```\nROUND 2 RESULTS:\n # | Idea | Market Score | Top Niche | Pain Depth | Language Bank\n 1 | [slug-1] | 87/120 | [niche] | Deep | 28 phrases\n 3 | [slug-3] | 72/120 | [niche] | Moderate | 19 phrases\n```\n\n**Tier 3 decision:** User reviews. Can cut weak markets or advance all. If only 2 remain and one is clearly weaker, recommend cutting but don't force it.\n\nUpdate eliminated ideas and set `current_round` to `\"offer_build\"`.\n\n### Step 4: ROUND 3 \u2014 Offer Build (Survivors Only)\n\nFor each surviving idea sequentially:\n1. Delegate to offer-architect subagent (`.claude/agents/offer-architect.md`) \u2014 /build-blocks + /stress-test in single pass\n2. Save outputs to `assets/[slug]/building-blocks/`\n3. Update pipeline-state.json\n\nAfter ALL survivors complete, present side-by-side:\n\n```\nROUND 3 RESULTS:\n # | Idea | Mechanism | Price | USP | Stress Score\n 1 | [slug-1] | [name] | $197 | [usp] | 42/50 GO\n 3 | [slug-3] | [name] | $97/mo | [usp] | 35/50 REVISE\n```\n\n**Decision handling:**\n- GO \u2192 ADVANCE\n- REVISE \u2192 User can choose to revise (loops that idea only, doesn't block others) or cut\n- REBUILD \u2192 recommend CUT (rebuilding in tournament context wastes the speed advantage)\n\n**Tier 3 decision:** User approves, revises, or cuts per idea. REVISE loops run inline \u2014 re-run stress test after user provides direction.\n\nUpdate `current_round` to `\"unit_economics\"`.\n\n### Step 5: ROUND 4 \u2014 Unit Economics (Survivors Only)\n\n**Tier 3 decision first:** Ask user for budget allocation:\n\n```\nTotal daily ad budget across all pipelines? (This gets split across [N] survivors)\n\nOption A: Equal split \u2014 $[X]/day each\nOption B: Weighted \u2014 you assign per idea\n```\n\nFor each surviving idea:\n1. Run /unit-economics SOP with allocated budget\n2. Save outputs to `assets/[slug]/research/`\n3. Update pipeline-state.json\n\nPresent final comparison:\n\n```\nROUND 4 RESULTS \u2014 FINAL:\n # | Idea | Price | Break-even CPA | Budget | Days to Signal | Verdict\n 1 | [slug-1] | $197 | $85 | $25/d | 12 days | VIABLE\n 3 | [slug-3] | $97/mo | $42 | $25/d | 8 days | VIABLE\n```\n\n### Step 6: Winner Selection\n\n**Tier 3 decision:** Present all viable ideas with recommendation:\n\n```\nTOURNAMENT COMPLETE \u2014 [N] ideas evaluated, [M] viable.\n\nPICK YOUR WINNER(S) (1-2 to advance to Layer 2):\n\n [Recommendation based on: stress score, unit economics viability, autonomy score, market depth]\n\n 1. [slug-1] \u2014 [one-line summary of why it's strong]\n 3. [slug-3] \u2014 [one-line summary of why it's strong]\n\nWhich ideas advance? (The rest get archived with all research preserved.)\n```\n\n### Step 7: Finalize\n\nFor winners:\n- Update pipeline entry: `current_stage` \u2192 `\"name_lock\"` (ready for Layer 2)\n- Update tournament: add to `winners` array\n\nFor losers:\n- Archive pipeline entry (set `archived_at`, `archive_reason: \"Tournament elimination \u2014 Round [N]\"`)\n- Trigger `/lessons capture` for each eliminated idea\n\nFor the tournament:\n- Set `status` \u2192 `\"complete\"`\n- Set `updated` timestamp\n\nGenerate tournament summary report:\n\n```markdown\n# Tournament Report \u2014 [date]\n\n## Ideas Evaluated: [N]\n## Winners: [list]\n## Eliminated: [list with round + reason]\n\n### Round-by-Round Results\n[tables from each round]\n\n### Key Patterns\n- [What differentiated winners from losers]\n- [Market characteristics that correlated with strong scores]\n- [Offer patterns that passed stress test]\n\n### Research Preserved\nAll research for eliminated ideas is saved in assets/[slug]/ for future reference.\n```\n\nSave to `assets/tournaments/[date]-tournament-report.md`.\n\nTrigger `/lessons capture` for tournament-level patterns.\n\n## Autonomy Classification\n\n- Round execution (research, scoring): **Tier 1** \u2014 Full Auto\n- Auto-cut LOW autonomy ideas: **Tier 2** \u2014 Notify & Proceed\n- User cuts at each gate: **Tier 3** \u2014 Recommend & Wait\n- Winner selection: **Tier 3** \u2014 Recommend & Wait\n- Budget allocation: **Tier 3** \u2014 Recommend & Wait\n- Any real money decisions: **Tier 4** \u2014 Escalate\n\n## State Updates\n\nUpdate `pipeline-state.json` after:\n- Tournament initialization\n- Each idea's scout/autonomy completion\n- Each round's cuts\n- Each idea's research/build completion\n- Budget allocation\n- Winner selection\n- Tournament finalization\n\n## Output Files\n\n```\nassets/\n [idea-slug-1]/ # Standard per-pipeline directory structure\n research/\n building-blocks/\n [idea-slug-2]/\n research/\n tournaments/\n [date]-tournament-report.md\n```\n\n## Error Handling\n\n- If a subagent fails mid-round: save partial results, report which idea failed, offer to retry or cut that idea\n- If user wants to pause mid-tournament: state is fully saved in pipeline-state.json, resume with `/tournament` (detects active tournament)\n- If only 1 idea survives before Round 4: \"Only 1 idea remaining \u2014 tournament mode no longer needed. Continue as normal pipeline? Run /build-blocks to proceed.\"\n\n## Resume Logic\n\nOn `/tournament` when an active tournament exists:\n1. Read tournament state\n2. Present current status (delegate to /tournament-status logic)\n3. Ask: \"Resume tournament at Round [N]?\" or \"Start a new tournament? (This archives the current one.)\"\n4. If resume: pick up at `current_round` with surviving ideas\n\n## Next Step\n\nWinners proceed to `/name-lock` \u2192 Layer 2 as normal pipelines. The tournament is a Layer 1 accelerator \u2014 after it completes, winners are indistinguishable from any other pipeline."; //# sourceMappingURL=tournament.d.ts.map