export declare const DEPLOY = "# /deploy \u2014 Campaign Deployment Engine\n\n## What This Does\n\nBuilds all marketing and sales assets from the validated Building Blocks, Copy Directives, Product Blueprint, and platform constraints.\n\n## Trigger Context\nAfter Product Architecture Engine and Platform Engine complete. Both must feed in.\nName Lock Registry must exist \u2014 no assets get built with unlocked names.\n\n## Execution Protocol\n\n**DELEGATE TO SUBAGENT: `campaign-builder`**\n\n### Step 0: Verify Prerequisites\nRead `pipeline-state.json`. Verify all three conditions:\n- `name_lock.status == \"locked\"`\n- `platform_engine.status == \"complete\"`\n- `product_architecture.status == \"complete\"`\n\nIf any are not met:\n```\nSTAGE_BLOCKED \u2014 Prerequisites not met.\n\nMissing stages:\n - [stage]: status is \"[current]\", needs \"complete\"\n\nRun these first:\n 1. /name-lock (if name not locked)\n 2. /platform (if platform not selected)\n 3. /product (if product architecture not complete)\n```\n\n### Step 1: Pre-Deploy Quality Gate (AUTO-EXECUTE \u2014 Tier 1)\n\n**Before generating any campaign assets**, run the research and unit economics test modules to verify all upstream inputs are clean:\n\n```bash\npython qa-tests/qa_runner.py [market-slug] --module research_report --module unit_economics --json-out assets/[market-name]/campaigns/qa-pre-deploy.json\n```\n\nThis catches: missing research sections, insufficient citations, cross-report contradictions (awareness/sophistication mismatch between buyer research and building blocks), broken unit economics math (margins <= 0, CAC >= LTV), and placeholder text in research files.\n\n**If exit code is 0:** proceed to asset production.\n\n**If exit code is 1:** fix the flagged issues in the research/unit-economics files before proceeding. These are foundational inputs \u2014 deploying from broken research produces broken copy. Fix directly (Tier 1), re-run tests, then proceed.\n\n### Asset Production Sequence\n\n1. **Sales Letter / Landing Page** (SOP 5: Copy Structure Formula)\n - Headline (from SOP 7 formulas, matched to awareness level)\n - Lead (hook based on direct/indirect selection from sophistication level)\n - Body: Selling points structured to overcome objections in sequence\n - Module breakdowns pulled from Product Blueprint (specific, not vague)\n - Mechanism explanation from Product Blueprint\n - Offer stack with value quantification\n - Guarantee (directly inverts buyer's biggest risk)\n - CTAs with urgency\n - FAQ addressing remaining objections from persona research\n\n2. **Email Sequence** (5-7 emails)\n - Welcome/delivery email\n - Story-driven emails using transformation narrative\n - Objection-handling emails (one per top objection)\n - Proof/testimonial email\n - Urgency/deadline email\n - Each email references specific modules or deliverables from Product Blueprint\n\n3. **Ad Copy** (3-5 variations)\n - Direct response ads for high-awareness markets\n - Content-style ads for low-awareness markets\n - Each variation tests a different Building Block as the lead hook\n - Platform-native formatting (respect platform constraints)\n\n4. **Content Assets** (if platform requires content-first approach)\n - Lead magnets derived from Module 1 of Product Blueprint\n - Social proof compilations\n - Value-demonstration content pieces\n\n5. **SEO Foundation** (applied to all landing page assets)\n - Meta title variant (<60 chars) combining primary keyword + compelling angle\n - Meta description (<160 chars) with value prop + CTA\n - Canonical URL tag (``) with clean URL slug: `/[primary-keyword]-[mechanism-name]/`\n - Open Graph tags (og:title, og:description, og:image, og:url, og:type)\n - Twitter Card tags (twitter:card, twitter:title, twitter:description, twitter:image)\n - JSON-LD generation \u2014 3 schema blocks embedded in ``:\n - Organization schema from Name Lock Registry\n - Product schema with offer details\n - FAQ schema extracted from FAQ section\n - Review schema for testimonials section (if testimonials are present)\n - EEAT signals: author name + credentials, \"Last updated\" date, specific client stats\n - Citation magnets: at least 2 per landing page (named framework + specific stat)\n - Apply first-200-words rule: first 200 words of landing page must contain primary value proposition + specific stat from market intel + brand name\n - H2/H3 hierarchy that works for both conversion AND featured snippet optimization\n - FAQ section structured with question-as-header format (enables FAQ schema extraction)\n\n### Production Rules\n- Every claim in copy must appear in Copy Directives (authorized promises only)\n- Every specific product description must come from Product Blueprint\n- Language must match the Language Bank from buyer research\n- Format must respect platform constraints\n- **Landing page saved as `.html`** (complete HTML5 with meta tags, JSON-LD schemas, and semantic structure) \u2014 not `.md`\n- Email sequences and ad copy saved as `.md` files\n- All assets saved as individual files in `assets/[market-name]/campaigns/`\n\n1. Invoke campaign-builder subagent with all inputs.\n - Include Name Lock Registry (`assets/[market-name]/building-blocks/name-lock-registry.md`)\n2. Receive all campaign assets.\n3. Save to `assets/[market-name]/campaigns/` with clear filenames.\n4. Update pipeline-state.json with asset inventory.\n5. Present asset list to user for review before deployment.\n\n### Post-Deploy Structural Check (AUTO-EXECUTE \u2014 Tier 1)\n\nAfter the campaign-builder subagent writes all assets, run landing page and campaign asset tests immediately \u2014 before triggering `/qa`:\n\n```bash\npython qa-tests/qa_runner.py [market-slug] --module landing_page --module campaign_assets --json-out assets/[market-name]/campaigns/qa-post-deploy.json\n```\n\nThis catches: HTML validity issues, missing CTAs, no viewport meta tag, exposed API keys, placeholder text, email subject lines over 60 chars, missing ad variation components, brand name inconsistency \u2014 all structural issues that should be fixed before persona alignment even looks at the copy.\n\n**If exit code is 0:** proceed to `/qa`.\n\n**If exit code is 1:** fix the flagged structural issues directly in the campaign files (Tier 1). Re-run tests. Repeat up to 3 iterations. Then proceed to `/qa` \u2014 persona alignment will catch content-level issues separately.\n\n## Output\nComplete campaign asset package, structurally validated. All files in assets folder.\n\n## Next Step\nAuto-trigger `/qa` (Persona Alignment Gate \u2014 stress-tests all assets against buyer persona before deployment)"; //# sourceMappingURL=deploy.d.ts.map