export declare const PASSIVE_DEPLOY = "# /passive-deploy \u2014 Passive Asset Deployment Agent (PADA)\n\n## What This Does\n\nTakes validated market intelligence from upstream and deploys platform-native passive assets across marketplace platforms. The marketplace's native metrics (views, favorites, sales velocity) serve as the automated validation layer. No ads, no sales pages, no ongoing attention required.\n\n## Trigger Context\nTrigger phrases: \"Deploy passive assets\" / \"Run the PADA\" / \"Build my asset portfolio\"\n\nRequires upstream research to be complete:\n- Therapeutic Buyer Research Package (validated personas + pain architecture)\n- Market Intelligence OS or Scout seeds\n- Competitive landscape data\n\n## When to Use This vs. Active Pipeline\n\n**Active Pipeline** (Building Blocks \u2192 Deploy \u2192 Traffic \u2192 Validate):\n- High-ticket offers ($200+)\n- Coaching, consulting, community products\n- Products requiring custom sales pages and ad campaigns\n\n**Passive Pipeline** (PADA):\n- Digital downloads, templates, printables\n- Low-content books, workbooks, journals\n- Design assets, utility tools\n- Anything sold on a marketplace without your involvement in the transaction\n\nBoth pipelines can run simultaneously from the same buyer research.\n\n## Execution Protocol\n\n**DELEGATE TO SUBAGENT: `passive-asset-deployer`**\n\n### Step 1: Validate Upstream Inputs\n\nCheck pipeline-state.json for:\n- Therapeutic Buyer Research Package: REQUIRED (pain architecture, language bank, identity gap)\n- Market Intelligence OR Scout Report: REQUIRED (scored market + seeds)\n- Building Blocks: OPTIONAL (not required for passive assets \u2014 listing copy uses buyer research directly)\n\nIf buyer research is incomplete, STOP. Route to `/research` first.\n\n### Step 2: Invoke Passive Asset Deployer Subagent\n\nPass the full research package. The subagent executes:\n\n1. **Seed-to-Asset Translation** \u2014 converts pain points into platform-native product forms\n2. **40-Point Scoring** \u2014 scores each asset on therapeutic alignment, platform fit, competitive gap, and compounding potential\n3. **Phase Assignment** \u2014 sorts assets into SEED \u2192 ROOT \u2192 BRANCH \u2192 COMPOUND \u2192 SEASONAL SPRINT\n4. **Build Spec Generation** \u2014 complete listing specs per asset (title, tags, description, pricing, images, therapeutic design elements)\n5. **Cross-Platform Link Architecture** \u2014 maps how assets reference each other across platforms\n6. **Kill/Scale Rules** \u2014 platform-calibrated validation thresholds\n7. **12-Month Revenue Projection** \u2014 portfolio-level financial model\n8. **Seasonal Calendar** \u2014 demand windows with deploy-by dates\n\n### Step 2.5: Marketplace SEO Optimization\n\nAfter the subagent generates build specs, apply platform-specific SEO optimization to every asset:\n\n**Etsy:**\n- Title: Primary keyword in first 40 characters (Etsy search indexes first 40 chars most heavily)\n- Tags: Full 13-tag strategy \u2014 13 multi-word tags using buyer's Language Bank phrases + long-tail keywords\n- Description: First 160 characters optimized for Google snippet (Etsy listings appear in Google Shopping)\n- AI citation language: One sentence per listing using the format \"[Product name] helps [target buyer] [solve specific problem] using [mechanism/approach]\"\n\n**KDP (Amazon):**\n- Title: Primary keyword + emotional benefit\n- Subtitle: Secondary keyword carrier (Amazon indexes subtitle heavily)\n- 7 backend keywords: Long-tail phrases from buyer research pain points (no repeats from title/subtitle)\n- Description: First 200 words follow the first-200-words rule (stat + value prop + brand name)\n\n**All Platforms (Universal):**\n- AI citation sentence: Every listing includes one clearly quotable sentence that AI models can cite \u2014 format: \"[Brand] [Product Name] is a [product type] designed for [target buyer] who [pain point].\"\n- This sentence should appear in the first paragraph of every description.\n\n### Step 3: Receive and Save Portfolio Deployment Package\n\nSave complete package to:\n```\nassets/[market-name]/passive-portfolio/\n  portfolio-deployment-package.md     # Master document\n  build-specs/                        # Individual asset specs\n    seed-asset-1.md\n    seed-asset-2.md\n    seed-asset-3.md\n    root-asset-4.md\n    ...\n  validation-thresholds.md            # All kill/scale rules by platform\n  cross-platform-links.md            # Link architecture\n  seasonal-calendar.md               # Demand windows + deploy-by dates\n  revenue-projection.md              # 12-month model\n```\n\n### Step 4: Generate Deployment Checklist\n\nLike `/validate-prep` for the active pipeline, produce a step-by-step execution checklist:\n\n```\nPASSIVE DEPLOYMENT CHECKLIST \u2014 SEED PHASE (Weeks 1-3)\n\nWEEK 1:\n\u2610 1. Create Etsy shop (if new) \u2014 shop name, banner, about section\n\u2610 2. Build Asset #1: [name] using [tool] \u2014 estimated [X] hours\n\u2610 3. Create listing: paste title, tags, description from build spec\n\u2610 4. Upload product files + mockup images\n\u2610 5. Set price: $[exact]\n\u2610 6. Publish. Note listing URL: ________________\n\nWAIT 3-4 DAYS (let algorithm index)\n\nWEEK 1.5:\n\u2610 7. Build Asset #2: [name] \u2014 estimated [X] hours\n\u2610 8. Create listing from build spec\n\u2610 9. Publish. Note listing URL: ________________\n\nWAIT 3-4 DAYS\n\nWEEK 2.5:\n\u2610 10. Build Asset #3 (bundle): [name] \u2014 estimated [X] hours\n\u2610 11. Create listing from build spec\n\u2610 12. Publish. Note listing URL: ________________\n\u2610 13. Set calendar reminders:\n      - Day 30 check: [exact date] \u2192 run /passive-check day30\n      - Day 60 check: [exact date] \u2192 run /passive-check day60\n      - Day 90 check: [exact date] \u2192 run /passive-check day90\n\nTOTAL BUILD TIME: ~[X] hours over 3 weeks\nTOTAL COST: ~$[listing fees only]\n```\n\n### Step 5: Update Pipeline State\n\n```json\n{\n  \"passive_portfolio\": {\n    \"status\": \"seed_phase\",\n    \"created_at\": \"[timestamp]\",\n    \"niche\": \"[market name]\",\n    \"total_assets_planned\": [N],\n    \"assets_deployed\": 0,\n    \"current_phase\": \"seed\",\n    \"phases\": {\n      \"seed\": {\n        \"assets\": [\"[names]\"],\n        \"platform\": \"etsy\",\n        \"deploy_window\": \"weeks 1-3\",\n        \"status\": \"pending\"\n      },\n      \"root\": {\n        \"assets\": [\"[names]\"],\n        \"platform\": \"etsy\",\n        \"deploy_window\": \"weeks 4-6\",\n        \"status\": \"pending\",\n        \"gate\": \"Day 30 ALIVE signal required\"\n      },\n      \"branch\": {\n        \"assets\": [\"[names]\"],\n        \"platforms\": [\"kdp\", \"payhip\"],\n        \"deploy_window\": \"weeks 7-10\",\n        \"status\": \"pending\",\n        \"gate\": \"SEED phase assets showing signal\"\n      },\n      \"compound\": {\n        \"assets\": [\"[planned]\"],\n        \"deploy_window\": \"weeks 11-16\",\n        \"status\": \"pending\",\n        \"gate\": \"Day 60 TRACTION signal required\"\n      },\n      \"seasonal\": {\n        \"windows\": [],\n        \"status\": \"pending\"\n      }\n    },\n    \"portfolio_metrics\": {\n      \"total_deployed\": 0,\n      \"anchors\": 0,\n      \"fillers\": 0,\n      \"killed\": 0,\n      \"total_revenue\": 0,\n      \"monthly_revenue\": 0\n    },\n    \"asset_tracking\": [],\n    \"output_files\": []\n  }\n}\n```\n\n### Step 6: Present to User\n\nPresent the Portfolio Deployment Package with:\n- Asset portfolio sorted by score and deployment phase\n- Build time estimate for SEED phase\n- Revenue projection summary\n- First 3 assets to build with specs\n\nTier 2 \u2014 Notify & Proceed for package generation.\nThe user builds and deploys at their own pace.\n\n## Autonomy\nTier 1 \u2014 Full Auto for research and scoring.\nTier 2 \u2014 Notify & Proceed for presenting the deployment package.\nUser executes the physical build and listing at their pace.\n\n## Output\nComplete Portfolio Deployment Package in assets folder. Checklist presented inline.\n\n## Next Step\nUser builds SEED assets \u2192 runs `/passive-check day30` at Day 30 \u2192 system routes from there.";
//# sourceMappingURL=passive-deploy.d.ts.map