export declare const FEEDBACK = "# /feedback \u2014 Optimizer Feedback Loop\n\n## What This Does\n\nReceives real-world validation data and routes iteration to the correct layer and component.\n\n## Trigger Context\nUser provides real-world data: conversion rates, feedback, refund reasons, engagement metrics, testimonials, or qualitative observations.\n\n## Execution Protocol\n\n**DELEGATE TO SUBAGENT: `optimizer`**\n\n### Step 0: Verify Prerequisites\nRead `pipeline-state.json`. Confirm an active pipeline exists with deployed assets (at least one of: `qa_gate.status == \"complete\"`, `validation_tier_1.status` is not \"pending\", or `traffic_agent` has active channels). If no assets are deployed, stop:\n```\nFEEDBACK BLOCKED \u2014 No deployed assets to analyze.\nComplete deployment first, then return with real-world data.\n```\n\n### Step 1: Receive the data\nUser pastes or describes results. Accept any format \u2014 numbers, screenshots described, qualitative feedback, email replies, survey responses, **organic data** (GSC metrics, AI citation results, content decay observations).\n\n### Step 2: Delegate to optimizer subagent\nInvoke `optimizer` subagent with:\n1. Raw validation data from user\n2. Current pipeline state (from `pipeline-state.json`)\n3. Promise-Product Alignment Report path (from `assets/[market-name]/product/`)\n4. All relevant asset file paths (campaigns, copy, product architecture)\n5. Revenue phase status (if revenue_phase is set): current phase, what gate is next, days since deployment\n\nThe subagent will:\n- Classify the signal using its 8-row diagnosis table (covers: no traffic, traffic/no signups, signups/no opens, opens/no clicks, clicks/no conversions, high refunds, low completion, everything working)\n- Use the Alignment Report to pinpoint specific components\n- Produce a 5-point iteration plan per issue (what to change, which file, which SOP, expected impact, measurement)\n- Save validation report to `assets/[market-name]/validation/`\n\n### Step 3: Process subagent output\n1. Read the validation report and iteration plan from the subagent\n2. Route the iteration to the correct command:\n   - Layer 1 issue \u2192 `/build-blocks` + `/stress-test`\n   - Layer 2 asset issue \u2192 fix specific file, re-run `/qa`\n   - Traffic issue \u2192 `/creative-test`, `/funnel-optimize`, or `/channels`\n   - Scale mode \u2192 `/scale`\n   - Revenue stall (signal but no sale after 14+ days) \u2192 `/bold-action` for credibility gap, or `/build-blocks` for offer revision\n   - Revenue regression (had sales, lost them) \u2192 `/unit-economics` recalculation + `/stress-test` re-evaluation\n\n### Step 4: Update pipeline-state.json\n- Add iteration entry to `iteration_history` array with: `{date, data_received, diagnosis, route, iteration_plan_file}`\n- Update current stage if iteration changes the pipeline position\n\n### Step 5: Present the iteration plan\nShow user: what was diagnosed, what changes are needed, which command to run next. Tier 3 \u2014 wait for user approval before executing the iteration.\n\n## Output\nIteration routing decision. Updated files. Pipeline state updated.\n\n## Next Step\nRe-run the specific SOP that was identified as the weak link, then re-validate.";
//# sourceMappingURL=feedback.d.ts.map