export declare const PORTFOLIO_TRIAGE = "\n# Portfolio Triage \u2014 Pipeline Ranking & Selection Gate\n\n## What This Does\nRanks all pipelines past unit-economics by **Profit Velocity Score** and recommends your top N for active focus. This helps you concentrate resources on the pipelines most likely to generate revenue fastest.\n\n## Trigger Context\nRun when multiple pipelines have passed unit-economics with VIABLE or TIGHT verdict and you want to prioritize.\n\n## Execution Protocol\n\n### Step 1: Collect Eligible Pipelines (Tier 1 \u2014 Auto)\nRead pipeline-state.json. For each pipeline, check:\n- unit_economics.status == \"complete\"\n- unit_economics.verdict in [\"VIABLE\", \"TIGHT\"]\n\nIf fewer than 2 eligible pipelines exist, report all eligible. If 0 eligible: \"No pipelines past unit-economics. Run scout -> unit-economics first.\"\n\n### Step 2: Compute Profit Velocity Score (Tier 1 \u2014 Auto)\nFor each eligible pipeline, calculate:\n\nprofit_velocity = LTV / sales_cycle_estimate_days\n  (default sales_cycle_estimate_days to 30 if null)\n\nautonomy_factor = autonomy_score.total / 35\n  (normalized 0-1; default to 0.7 if no autonomy score)\n\nmarket_depth = stress_test.score / 50\n  (normalized 0-1; default to 0.5 if no stress test score)\n\ntriage_score = profit_velocity x autonomy_factor x market_depth\n\nScore interpretation:\n- Higher = faster path to revenue with more agent leverage\n- LTV drives the numerator \u2014 high-ticket offers score higher\n- Short sales cycles amplify the score\n- Autonomy and market depth are multipliers reducing execution risk\n\n### Step 3: Rank and Present (Tier 1 \u2014 Auto)\nPresent a ranked table showing:\n- Rank number\n- Pipeline name\n- LTV\n- Sales cycle estimate (days)\n- Autonomy score\n- Stress test score\n- Triage score\n\n### Step 4: Recommend Selection (Tier 3 \u2014 Recommend & Wait)\nRecommend top N pipelines (N = max_active parameter, default 3) for active focus.\n\nPresent recommendation with reasoning. Suggest archiving remainder \u2014 research preserved, can reactivate anytime.\n\nWait for user to confirm or override selection.\n\n### Step 5: Update Pipeline State (Tier 1 \u2014 Auto)\nFor selected pipelines:\n- Set triage_status: \"selected\"\n- Set revenue_phase: \"signal\" (if not already set and revenue tracking is desired)\n- Set triage_rank and triage_score\n\nFor archived pipelines:\n- Set triage_status: \"archived\"\n- Set triage_rank and triage_score\n- Preserve all other fields \u2014 research and assets are kept\n\nIf selected pipelines have completed validate_prep and deployment_deadline_at is null:\n- Optionally set deployment_deadline_at to suggest a deployment timeline\n\nUpdate pipeline-state.json.\n\n### Step 6: Present Action Plan\nShow selected pipelines with their specific next steps based on current_stage.\nShow archived pipelines with their rank and score.\nNote: Run revenue_review weekly to track progress. Run portfolio_triage again when a slot opens.\n\n## Re-Triage Rules\n- Can be re-run at any time\n- Archiving a selected pipeline opens a slot\n- revenue_review can recommend archiving if no progress\n- Archived pipelines retain all research \u2014 reactivation is instant\n\n## Output\nNo separate file. State changes written directly to pipeline-state.json.\n";
//# sourceMappingURL=portfolio-triage.d.ts.map