@elevasis/ui 2.79.0 → 2.81.0

package/dist/{knowledge-search-index-6GQK55IQ.js → knowledge-search-index-UPKXCXQP.js}

@@ -52,7 +52,7 @@ Log bounce count, leads cleaned, root cause, and resolution in the batch tracker
   {
     id: "knowledge.cold-email-research-2026",
     title: "Copy Research (March 2026)",
-    summary: "Cold email research findings from 2025-2026 benchmark reports, A/B test data, and industry studies \xE2\u20AC\u201D reply rates, subject lines, CTAs, sequence structure, social proof, and vertical-specific angles.",
+    summary: "Cold email research findings from 2025-2026 benchmark reports, A/B test data, and industry studies \u2014 reply rates, subject lines, CTAs, sequence structure, social proof, and vertical-specific angles.",
     bodyText: `Research findings that inform our copy strategy and campaign decisions. Sourced from Instantly's 2026 Benchmark Report (3M+ emails), industry studies, and platform data.
 
 Last researched: 2026-03-18
@@ -96,13 +96,13 @@ Sequence Length
     id: "knowledge.discovery-call-playbook",
     title: "Stage 03: Discovery",
     summary: "Discovery form submission, qualification routing, and data storage -- the pipeline endpoint",
-    bodyText: "Overview\n\nThe discovery form is filled during the call by the salesperson. On submission, the workflow stores structured data, updates the CRM, and routes based on qualification.\n\nThis is the current pipeline endpoint \xE2\u20AC\u201D qualified leads receive a HITL task for manual follow-up; no automated stages exist beyond this point.\n\nWorkflow Steps\n\n1. route-by-action \xE2\u20AC\u201D Route to submission or no-show flow\n2. compute-cost \xE2\u20AC\u201D Calculate totalAnnualCost from bottlenecks\n3. store-discovery \xE2\u20AC\u201D Save discoverydata JSONB to acqdeals\n4. find-deal \xE2\u20AC\u201D Find Attio Deal (acqdeals \xE2\u2020\u2019 URL context \xE2\u2020\u2019 Attio API)\n5. update-attio-stage \xE2\u20AC\u201D Update Deal.stage based on qualification\n6. create-summary-note \xE2\u20AC\u201D Add markdown Note to Deal\n7. create-hitl-task \xE2\u20AC\u201D Create HITL approval item for qualified leads\n\nQualification Routing\n\n- Qualified: Deal moves to qualified stage; HITL task created for admin follow-up\n- Not Qualified: Deal moves to closedlost stage; no further automation\n- No-Show: Deal moves to noshow stage; timeout checker handles re-engagement\n\nDiscovery Form Structure\n\nThe form captures: company size, current tools, 3 biggest bottlenecks, estimated time wasted per week, budget comfort range, urgency, decision-making authority."
+    bodyText: "Overview\n\nThe discovery form is filled during the call by the salesperson. On submission, the workflow stores structured data, updates the CRM, and routes based on qualification.\n\nThis is the current pipeline endpoint \u2014 qualified leads receive a HITL task for manual follow-up; no automated stages exist beyond this point.\n\nWorkflow Steps\n\n1. route-by-action \u2014 Route to submission or no-show flow\n2. compute-cost \u2014 Calculate totalAnnualCost from bottlenecks\n3. store-discovery \u2014 Save discoverydata JSONB to acqdeals\n4. find-deal \u2014 Find Attio Deal (acqdeals \u2192 URL context \u2192 Attio API)\n5. update-attio-stage \u2014 Update Deal.stage based on qualification\n6. create-summary-note \u2014 Add markdown Note to Deal\n7. create-hitl-task \u2014 Create HITL approval item for qualified leads\n\nQualification Routing\n\n- Qualified: Deal moves to qualified stage; HITL task created for admin follow-up\n- Not Qualified: Deal moves to closedlost stage; no further automation\n- No-Show: Deal moves to noshow stage; timeout checker handles re-engagement\n\nDiscovery Form Structure\n\nThe form captures: company size, current tools, 3 biggest bottlenecks, estimated time wasted per week, budget comfort range, urgency, decision-making authority."
   },
   {
     id: "knowledge.inbound-booking-playbook",
     title: "Stage 02: Booking",
     summary: "Cal.com booking handling -- create, reschedule, and cancel discovery call bookings",
-    bodyText: 'Overview\n\nWhen a prospect books a discovery call via Cal.com, the booking handler manages CRM updates, notifications, and reminder scheduling across all booking lifecycle events.\n\nBooking Handler Workflow\n\nTriggers: Cal.com webhooks (BOOKINGCREATED, BOOKINGRESCHEDULED, BOOKINGCANCELLED)\n\nEvent Flows\n\nBOOKINGCREATED:\n1. create-contact \xE2\u20AC\u201D Create or update Attio Person record, resolve Deal via metadata or email, update Deal stage to booked, create Discovery Call Prep note, cancel brochure follow-ups\n2. notify-created \xE2\u20AC\u201D Send platform notification to admin\n3. schedule-reminders \xE2\u20AC\u201D Create absolute schedule with pre-computed -24h and -1h reminder times\n\nBOOKINGRESCHEDULED:\n1. update-schedule \xE2\u20AC\u201D Cancel existing reminders, schedule new ones at updated times\n2. finish-reschedule \xE2\u20AC\u201D Update Deal stage, notify admin\n\nBOOKINGCANCELLED:\n1. cancel-schedule \xE2\u20AC\u201D Cancel all scheduled reminders\n2. finish-cancel \xE2\u20AC\u201D Update Deal stage to cancelled, notify admin\n\nReminder Schedule\n\nTwo automated reminders per booking:\n- -24h reminder: "Looking forward to our call tomorrow"\n- -1h reminder: "See you in 1 hour" with discovery form link\n\nReminders are scheduled as absolute times (not relative), so rescheduling correctly cancels and re-schedules them.'
+    bodyText: 'Overview\n\nWhen a prospect books a discovery call via Cal.com, the booking handler manages CRM updates, notifications, and reminder scheduling across all booking lifecycle events.\n\nBooking Handler Workflow\n\nTriggers: Cal.com webhooks (BOOKINGCREATED, BOOKINGRESCHEDULED, BOOKINGCANCELLED)\n\nEvent Flows\n\nBOOKINGCREATED:\n1. create-contact \u2014 Create or update Attio Person record, resolve Deal via metadata or email, update Deal stage to booked, create Discovery Call Prep note, cancel brochure follow-ups\n2. notify-created \u2014 Send platform notification to admin\n3. schedule-reminders \u2014 Create absolute schedule with pre-computed -24h and -1h reminder times\n\nBOOKINGRESCHEDULED:\n1. update-schedule \u2014 Cancel existing reminders, schedule new ones at updated times\n2. finish-reschedule \u2014 Update Deal stage, notify admin\n\nBOOKINGCANCELLED:\n1. cancel-schedule \u2014 Cancel all scheduled reminders\n2. finish-cancel \u2014 Update Deal stage to cancelled, notify admin\n\nReminder Schedule\n\nTwo automated reminders per booking:\n- -24h reminder: "Looking forward to our call tomorrow"\n- -1h reminder: "See you in 1 hour" with discovery form link\n\nReminders are scheduled as absolute times (not relative), so rescheduling correctly cancels and re-schedules them.'
   },
   {
     id: "knowledge.inbound-reply-handling-playbook",
@@ -118,10 +118,10 @@ Four-way classification with confidence-based HITL routing. Auto-replies detecte
 
 | Category | Examples | Action |
 | --- | --- | --- |
-| Interested | "Yes I'm interested", "Tell me more" | CRM \xE2\u2020\u2019 HITL task with LLM-drafted follow-up |
+| Interested | "Yes I'm interested", "Tell me more" | CRM \u2192 HITL task with LLM-drafted follow-up |
 | Not Interested | "Unsubscribe", "Not interested" | Stop outreach sequence |
-| Bounced | mailer-daemon@, "Undeliverable" | Stop outreach \xE2\u2020\u2019 Mark Lead DB INVALID \xE2\u2020\u2019 Skip CRM |
-| Auto-Reply | Out-of-office, ticketing acknowledgments | No action \xE2\u20AC\u201D campaign continues |
+| Bounced | mailer-daemon@, "Undeliverable" | Stop outreach \u2192 Mark Lead DB INVALID \u2192 Skip CRM |
+| Auto-Reply | Out-of-office, ticketing acknowledgments | No action \u2014 campaign continues |
 
 Auto-Reply Detection (Pre-LLM)
 
@@ -133,7 +133,7 @@ Caught deterministically via regex:
 Routing Notes
 
 - NOTINTERESTED and BOUNCED: sequence stopped via Instantly update-interest-status
-- INTERESTED: does NOT stop sequence \xE2\u20AC\u201D proceeds to CRM creation and HITL queue
+- INTERESTED: does NOT stop sequence \u2014 proceeds to CRM creation and HITL queue
 - AUTO-REPLY: no CRM, no sequence stop, no reply
 
 HITL Strategy
@@ -144,7 +144,7 @@ For INTERESTED replies, an LLM drafts a follow-up response. Admin reviews and ap
     id: "knowledge.lead-gen-pipeline-playbook",
     title: "Lead-Gen Playbook",
     summary: "Empirical benchmarks, threshold guidance, provider economics, and codified learnings from 3 completed batches of the lead-gen pipeline.",
-    bodyText: "Performance Benchmarks\n\nPer-stage success rates across the 3 completed Orange County batches (vet-1, auto-1, home-1).\n\nStage 1: Scrape (Raw to Filtered)\n\n| Metric | vet-1 | auto-1 | home-1 | Benchmark |\n| --- | --- | --- | --- | --- |\n| Raw results | 480 | 800 | 1000 | -- |\n| Companies created | 393 | 566 | 701 | -- |\n| Active in DB | 322 | 428 | 640 | -- |\n\nStage 3: Company Qualification Rate\n\n| Metric | vet-1 | auto-1 | home-1 | Benchmark |\n| --- | --- | --- | --- | --- |\n| Qualified | 213 (76%) | 284 (79%) | 326 (60%) | 60-80% |\n| Disqualified | 66 (24%) | 74 (21%) | 222 (40%) | 20-40% |\n\nStage 5: Email Verification\n\nVALID rate: 33-41% of discovered emails across batches. Target bounce rate \\<2%.\n\nModel Selection\n\nAll lead-gen LLM steps run on claude-sonnet-5 (Anthropic) \u2014 qualification, extraction, and personalization alike. There is no separate cheap tier for high-volume steps.\n\nProvider Economics\n\nTomba domain search provides the best cost-per-verified-contact for local SMBs. Dual-verify (Tomba + Mails.so) catches most false positives.\n\nPipeline Stages\n\n1. Scrape (Google Maps via Apify)\n2. LLM Extract (website crawl \xE2\u2020\u2019 structured data)\n3. Company Qualification (LLM ICP scoring)\n4. Email Discovery (Tomba domain search)\n5. Email Verification (Mails.so)\n6. Opening Line Generation (ist-personalization-workflow)\n7. Campaign Upload (ist-upload-contacts-workflow)"
+    bodyText: "Performance Benchmarks\n\nPer-stage success rates across the 3 completed Orange County batches (vet-1, auto-1, home-1).\n\nStage 1: Scrape (Raw to Filtered)\n\n| Metric | vet-1 | auto-1 | home-1 | Benchmark |\n| --- | --- | --- | --- | --- |\n| Raw results | 480 | 800 | 1000 | -- |\n| Companies created | 393 | 566 | 701 | -- |\n| Active in DB | 322 | 428 | 640 | -- |\n\nStage 3: Company Qualification Rate\n\n| Metric | vet-1 | auto-1 | home-1 | Benchmark |\n| --- | --- | --- | --- | --- |\n| Qualified | 213 (76%) | 284 (79%) | 326 (60%) | 60-80% |\n| Disqualified | 66 (24%) | 74 (21%) | 222 (40%) | 20-40% |\n\nStage 5: Email Verification\n\nVALID rate: 33-41% of discovered emails across batches. Target bounce rate \\<2%.\n\nModel Selection\n\nAll lead-gen LLM steps run on claude-sonnet-5 (Anthropic) \u2014 qualification, extraction, and personalization alike. There is no separate cheap tier for high-volume steps.\n\nProvider Economics\n\nTomba domain search provides the best cost-per-verified-contact for local SMBs. Dual-verify (Tomba + Mails.so) catches most false positives.\n\nPipeline Stages\n\n1. Scrape (Google Maps via Apify)\n2. LLM Extract (website crawl \u2192 structured data)\n3. Company Qualification (LLM ICP scoring)\n4. Email Discovery (Tomba domain search)\n5. Email Verification (Mails.so)\n6. Opening Line Generation (ist-personalization-workflow)\n7. Campaign Upload (ist-upload-contacts-workflow)"
   },
   {
     id: "knowledge.lead-gen-strategy",
@@ -210,14 +210,14 @@ pnpm exec elevasis exec Elevasis/lgn-01a-google-maps-scrape-workflow --input '{"
 
 After the execution starts, record the execution ID and source counts in the batch tracker.
 
-Local Website Crawl
+Stage 02a: Website Crawl
 
-Run the local website crawler against the batch:
+Run the Apify website crawl workflow against the batch:
 
 bash
-pnpm -C scripts/web-scraper run crawl -- {batch-id}
+pnpm exec elevasis exec Elevasis/lgn-02a-apify-website-crawl-workflow --input '{"batchId":"{batch-id}"}' --async
 
-The crawl should capture relevant sub-pages for LLM extraction. If vertical-specific keywords are not available in the active code path, use the default crawl coverage and note any manual crawl gaps in the tracker before extraction.
+The crawl captures relevant sub-pages for LLM extraction and writes them to enrichmentdata.websiteCrawl. Note any crawl gaps in the tracker before extraction.
 
 Stage 02: Website Extract
 
@@ -298,7 +298,7 @@ Launch Checklist
     id: "knowledge.outreach-campaign-playbook",
     title: "Campaign Playbook",
     summary: "Codified rules, benchmarks, and standard operating procedures for Instantly cold email campaigns -- testing methodology, personalization tiers, sequence structure, optimization loop, and batch readiness queries.",
-    bodyText: 'Benchmarks\n\nB2B cold email benchmarks (2025-2026). Use these as evaluation thresholds when running ist-analytics-workflow.\n\n| Metric | Bad | Needs Work | Good | Excellent |\n| --- | --- | --- | --- | --- |\n| Open Rate | \\<20% | 20-30% | 30-45% | 45%+ |\n| Reply Rate | \\<1% | 1-3% | 3-8% | 8%+ |\n| Positive Reply Rate | \\<0.5% | 0.5-1% | 1-3% | 3%+ |\n| Bounce Rate | \\>5% | 2-5% | 1-2% | \\<1% |\n\nCampaign Sizing Rules\n\n- 100-200 contacts per campaign segment -- small enough for meaningful personalization, large enough for statistical learning\n- 1-2 contacts per company -- reply rates drop from 8% to 4% when blasting 10+ people at the same company\n- 30-50 emails/day max per sending account\n- 50-100 emails/day total during testing (weeks 1-4), scaling to 500+/day once a winning formula is found\n\nTesting Priority\n\n1. Subject lines -- highest leverage, easiest to isolate\n2. Opening line / hook -- determines if they keep reading\n3. CTA type -- meeting request vs. soft question vs. value offer\n4. Body copy angle -- pain-point framing vs. benefit lead vs. social proof\n5. Send timing -- Tuesday-Thursday outperform Monday/Friday for B2B\n\nSequence Structure\n\n3 emails total (1 opener + 2 follow-ups). 87-95% of replies come within the first 3 emails.\n\n| Step | Timing | Strategy |\n| --- | --- | --- |\n| Email 1 | Day 0 | Cold read opener + EMRG social proof + interest-based CTA |\n| Email 2 | Day 3 | Short bump in same thread |\n| Email 3 | Day 5 | Breakup email. Soft close, loss aversion |\n\nAgent Optimization Loop\n\nPhase 1 (Launch): Verify batch readiness \xE2\u2020\u2019 Personalize \xE2\u2020\u2019 Create campaign \xE2\u2020\u2019 Create tracking list \xE2\u2020\u2019 Upload \xE2\u2020\u2019 Activate\n\nPhase 2 (Analyze Day 7-14): Run ist-campaign-review-workflow \xE2\u2020\u2019 Run ist-analytics-workflow \xE2\u2020\u2019 Interpret results\n\nPhase 3 (Optimize): Fix based on Phase 2 analysis (subject lines, personalization, bounce cleanup)\n\nPhase 4 (Scale): Document winning combination \xE2\u2020\u2019 Replicate to new segments \xE2\u2020\u2019 Maintain hygiene\n\nOffer Framing\n\n"We find one bottleneck, build an AI solution to fix it, and you only pay if it actually saves you time or makes you money."\n\n- Never use "free" in subject lines -- triggers spam filters\n- Frame as conditional, not charitable\n- Low-commitment CTAs get 2x more replies than direct meeting requests'
+    bodyText: 'Benchmarks\n\nB2B cold email benchmarks (2025-2026). Use these as evaluation thresholds when running ist-analytics-workflow.\n\n| Metric | Bad | Needs Work | Good | Excellent |\n| --- | --- | --- | --- | --- |\n| Open Rate | \\<20% | 20-30% | 30-45% | 45%+ |\n| Reply Rate | \\<1% | 1-3% | 3-8% | 8%+ |\n| Positive Reply Rate | \\<0.5% | 0.5-1% | 1-3% | 3%+ |\n| Bounce Rate | \\>5% | 2-5% | 1-2% | \\<1% |\n\nCampaign Sizing Rules\n\n- 100-200 contacts per campaign segment -- small enough for meaningful personalization, large enough for statistical learning\n- 1-2 contacts per company -- reply rates drop from 8% to 4% when blasting 10+ people at the same company\n- 30-50 emails/day max per sending account\n- 50-100 emails/day total during testing (weeks 1-4), scaling to 500+/day once a winning formula is found\n\nTesting Priority\n\n1. Subject lines -- highest leverage, easiest to isolate\n2. Opening line / hook -- determines if they keep reading\n3. CTA type -- meeting request vs. soft question vs. value offer\n4. Body copy angle -- pain-point framing vs. benefit lead vs. social proof\n5. Send timing -- Tuesday-Thursday outperform Monday/Friday for B2B\n\nSequence Structure\n\n3 emails total (1 opener + 2 follow-ups). 87-95% of replies come within the first 3 emails.\n\n| Step | Timing | Strategy |\n| --- | --- | --- |\n| Email 1 | Day 0 | Cold read opener + EMRG social proof + interest-based CTA |\n| Email 2 | Day 3 | Short bump in same thread |\n| Email 3 | Day 5 | Breakup email. Soft close, loss aversion |\n\nAgent Optimization Loop\n\nPhase 1 (Launch): Verify batch readiness \u2192 Personalize \u2192 Create campaign \u2192 Create tracking list \u2192 Upload \u2192 Activate\n\nPhase 2 (Analyze Day 7-14): Run ist-campaign-review-workflow \u2192 Run ist-analytics-workflow \u2192 Interpret results\n\nPhase 3 (Optimize): Fix based on Phase 2 analysis (subject lines, personalization, bounce cleanup)\n\nPhase 4 (Scale): Document winning combination \u2192 Replicate to new segments \u2192 Maintain hygiene\n\nOffer Framing\n\n"We find one bottleneck, build an AI solution to fix it, and you only pay if it actually saves you time or makes you money."\n\n- Never use "free" in subject lines -- triggers spam filters\n- Frame as conditional, not charitable\n- Low-commitment CTAs get 2x more replies than direct meeting requests'
   },
   {
     id: "knowledge.outreach-copy-strategy",
@@ -322,7 +322,7 @@ Tone
 
 3-Email Sequence Framework
 
-Email 1 \xE2\u20AC\u201D Hook + Offer (Day 0, 80 words)
+Email 1 \u2014 Hook + Offer (Day 0, 80 words)
 
 Hi {{firstName | there}},
 
@@ -330,23 +330,23 @@ Hi {{firstName | there}},
 
 {{categorypain}}
 
-I built 4 automations for a company that worked with Google and Sony Music. The first one alone saved them over $1,500 a month. I do the same thing for businesses like yours \xE2\u20AC\u201D you only pay if it actually works.
+I built 4 automations for a company that worked with Google and Sony Music. The first one alone saved them over $1,500 a month. I do the same thing for businesses like yours \u2014 you only pay if it actually works.
 
 Worth a quick look?
 
 {{sendingAccountFirstName}}
 
-Email 2 \xE2\u20AC\u201D Bump (Day 3, 40 words)
+Email 2 \u2014 Bump (Day 3, 40 words)
 
 Hi {{firstName | there}},
 
-Wanted to circle back on this \xE2\u20AC\u201D I've been helping a few companies like {{companyName}} free up their team by automating the repetitive stuff that eats up the day.
+Wanted to circle back on this \u2014 I've been helping a few companies like {{companyName}} free up their team by automating the repetitive stuff that eats up the day.
 
-Happy to take a 10-minute look \xE2\u20AC\u201D no pitch, just observations.
+Happy to take a 10-minute look \u2014 no pitch, just observations.
 
 {{sendingAccountFirstName}}
 
-Email 3 \xE2\u20AC\u201D Breakup (Day 5, 25 words)
+Email 3 \u2014 Breakup (Day 5, 25 words)
 
 Totally understand if this isn't the right time. If you ever want a second pair of eyes on what could be automated at {{companyName}}, the offer stands.
 
@@ -404,18 +404,18 @@ Opening Line Style: Cold Read
 The opening line must earn attention through recognition, not create tension through a pitch setup. Take one real fact from enrichment data and make an observation that shows you actually looked at their business.
 
 Good examples:
-- "4,400 reviews since 2018 \xE2\u20AC\u201D that kind of growth in Orange County is honestly wild."
-- "60 years family-owned with a proprietary Clean Green method \xE2\u20AC\u201D that's rare in pest control."
+- "4,400 reviews since 2018 \u2014 that kind of growth in Orange County is honestly wild."
+- "60 years family-owned with a proprietary Clean Green method \u2014 that's rare in pest control."
 
 Anti-patterns:
-- "You do termite inspections \xE2\u20AC\u201D how many follow-up calls get missed?" (Implication \xE2\u20AC\u201D signals selling)
+- "You do termite inspections \u2014 how many follow-up calls get missed?" (Implication \u2014 signals selling)
 - "Great company you've built!" (Generic flattery)`
   },
   {
     id: "knowledge.pipeline-management-playbook",
     title: "Pipeline Management",
     summary: "Automated pipeline maintenance workflows for the inbound pipeline, covering timeout monitoring, stale deal handling, unsubscribe cleanup, and full contact reset.",
-    bodyText: "Overview\n\nPipeline management keeps the inbound pipeline clean without manual intervention.\n\n- Timeout monitoring \xE2\u20AC\u201D Detecting deals that have gone stale in a stage\n- Unsubscribe cleanup \xE2\u20AC\u201D Closing deals and cancelling automation when a contact opts out\n- Full cleanup \xE2\u20AC\u201D Complete removal of all pipeline data for a contact\n\nNo timeout action transitions a deal automatically. All stage changes from the timeout system require admin approval via a HITL Command Queue item.\n\nTimeout System\n\nTimeout Checker (inb-pipeline-timeout-checker-workflow)\n\nScans all active pipeline stages. For each stale deal, creates a HITL approval item in the Command Queue. Never modifies deal records directly.\n\nTimeout rules by stage:\n\n| Stage | Condition | Timeout |\n| --- | --- | --- |\n| interested | No activity | 30 days |\n| booked | Meeting time has passed | 3 hours after meeting |\n| discovery | No form submission | 24 hours after call |\n\nAction Workflows\n\n4 action workflows triggered by admin approval:\n- Nurture: Move to nurture sequence\n- Close-Lost: Mark deal closed, stop all automation\n- No-Show: Re-send booking link with personal note\n- Follow-Up: Send soft re-engagement email\n\nUnsubscribe Cleanup\n\nWhen a contact opts out:\n1. Find all active automation for the contact\n2. Cancel scheduled reminders\n3. Update Deal stage to unsubscribed\n4. Mark contact as unsubscribed in Attio"
+    bodyText: "Overview\n\nPipeline management keeps the inbound pipeline clean without manual intervention.\n\n- Timeout monitoring \u2014 Detecting deals that have gone stale in a stage\n- Unsubscribe cleanup \u2014 Closing deals and cancelling automation when a contact opts out\n- Full cleanup \u2014 Complete removal of all pipeline data for a contact\n\nNo timeout action transitions a deal automatically. All stage changes from the timeout system require admin approval via a HITL Command Queue item.\n\nTimeout System\n\nTimeout Checker (inb-pipeline-timeout-checker-workflow)\n\nScans all active pipeline stages. For each stale deal, creates a HITL approval item in the Command Queue. Never modifies deal records directly.\n\nTimeout rules by stage:\n\n| Stage | Condition | Timeout |\n| --- | --- | --- |\n| interested | No activity | 30 days |\n| booked | Meeting time has passed | 3 hours after meeting |\n| discovery | No form submission | 24 hours after call |\n\nAction Workflows\n\n4 action workflows triggered by admin approval:\n- Nurture: Move to nurture sequence\n- Close-Lost: Mark deal closed, stop all automation\n- No-Show: Re-send booking link with personal note\n- Follow-Up: Send soft re-engagement email\n\nUnsubscribe Cleanup\n\nWhen a contact opts out:\n1. Find all active automation for the contact\n2. Cancel scheduled reminders\n3. Update Deal stage to unsubscribed\n4. Mark contact as unsubscribed in Attio"
   },
   {
     id: "knowledge.seo-lead-gen-playbook",
@@ -432,7 +432,7 @@ Anti-patterns:
   {
     id: "knowledge.upwork-proposal-playbook",
     title: "Proposal Playbook",
-    summary: "Data-backed strategies for writing winning Upwork proposals \xE2\u20AC\u201D structure, pricing, timing, client qualification, and benchmarks.",
+    summary: "Data-backed strategies for writing winning Upwork proposals \u2014 structure, pricing, timing, client qualification, and benchmarks.",
     bodyText: `The Numbers That Matter
 
 | Metric | Benchmark |
@@ -447,29 +447,29 @@ Keep proposals 150-200 words, mobile-scannable.
 
 The Five-Part Formula
 
-1. Hook (1-2 sentences) \xE2\u20AC\u201D Lead with what you do and why it's relevant. Never use "caught my attention" \xE2\u20AC\u201D overused clich\xC3\xA9.
-2. Proof (1-2 sentences) \xE2\u20AC\u201D One concrete metric from past work.
-3. Plan (2-3 lines) \xE2\u20AC\u201D Maximum 3 steps.
-4. Discovery Questions (exactly 2) \xE2\u20AC\u201D Smart, role-specific questions. End with a binary CTA.
-5. Sample (optional) \xE2\u20AC\u201D Loom video (2-3 min).
+1. Hook (1-2 sentences) \u2014 Lead with what you do and why it's relevant. Never use "caught my attention" \u2014 overused clich\xE9.
+2. Proof (1-2 sentences) \u2014 One concrete metric from past work.
+3. Plan (2-3 lines) \u2014 Maximum 3 steps.
+4. Discovery Questions (exactly 2) \u2014 Smart, role-specific questions. End with a binary CTA.
+5. Sample (optional) \u2014 Loom video (2-3 min).
 
 Opening Lines
 
 The first line decides 80% of reply outcomes. Always use the client's name or company name.
 
-Good openers: "Hi \xE2\u20AC\u201D I build {whattheyneed} for a living and run my own business on them daily."
+Good openers: "Hi \u2014 I build {whattheyneed} for a living and run my own business on them daily."
 
 Never open with: "The part that caught my attention..." / "What stood out..."
 
 Elevasis-Specific Positioning
 
-Dogfooding (Strongest Differentiator): We run our own 7-stage client acquisition pipeline on the platform: Scrape \xE2\u2020\u2019 Extract \xE2\u2020\u2019 Qualify \xE2\u2020\u2019 Email Discovery \xE2\u2020\u2019 Verify \xE2\u2020\u2019 Personalize \xE2\u2020\u2019 Outreach.
+Dogfooding (Strongest Differentiator): We run our own 7-stage client acquisition pipeline on the platform: Scrape \u2192 Extract \u2192 Qualify \u2192 Email Discovery \u2192 Verify \u2192 Personalize \u2192 Outreach.
 
 The 4 Principles (Use in Discovery Questions):
-1. Integrated \xE2\u20AC\u201D Works with existing tools
-2. Improving \xE2\u20AC\u201D Learns from every human decision
-3. Observable \xE2\u20AC\u201D Real-time visibility
-4. Governed \xE2\u20AC\u201D Humans approve what matters`
+1. Integrated \u2014 Works with existing tools
+2. Improving \u2014 Learns from every human decision
+3. Observable \u2014 Real-time visibility
+4. Governed \u2014 Humans approve what matters`
   },
   {
     id: "knowledge.upwork-query-strategy",
@@ -528,7 +528,7 @@ Style Rules
   {
     id: "knowledge.vertical-messaging-playbook",
     title: "Vertical Messaging Playbook",
-    summary: "Research-backed messaging strategy per vertical \xE2\u20AC\u201D verified claims, owner voice, language guides, pain point framing, and copy guidelines for outreach messaging.",
+    summary: "Research-backed messaging strategy per vertical \u2014 verified claims, owner voice, language guides, pain point framing, and copy guidelines for outreach messaging.",
     bodyText: `Purpose
 
 Reference doc for writing and evaluating vertical-specific outreach copy. Captures verified research, owner voice and language, and per-vertical messaging strategy.
@@ -564,7 +564,7 @@ Lead with Scenarios, Not Statistics
 
 | Weak (stat-first) | Strong (scenario-first) |
 | --- | --- |
-| "78% of homeowners hire the first contractor who responds." | "When you're on a job, you can't answer the phone \xE2\u20AC\u201D but the homeowner already called two other plumbers." |
+| "78% of homeowners hire the first contractor who responds." | "When you're on a job, you can't answer the phone \u2014 but the homeowner already called two other plumbers." |
 
 Claim Strength Tiers:
 - Tier 1 (Verified): Named source, specific methodology. Use confidently.
@@ -813,7 +813,7 @@ A common session combining read and write commands:
 
 Testimonials
 
-Xero Automation \xE2\u20AC\u201D The Invoice Chase That Disappeared
+Xero Automation \u2014 The Invoice Chase That Disappeared
 
 Client: Word of Mouth Agency
 
@@ -823,7 +823,7 @@ Result: 10+ hours/week saved. Zero manual follow-up emails.
 
 Permission: Case study approved with company name.
 
-Influencer Discovery \xE2\u20AC\u201D From Spreadsheet Hell to Strategic Decisions
+Influencer Discovery \u2014 From Spreadsheet Hell to Strategic Decisions
 
 Client: Word of Mouth Agency (Perth, Australia)
 
@@ -833,15 +833,15 @@ Result: 10+ hours/week saved. Research scope: 50 to 200+ influencers. Team focus
 
 Permission: Case study approved with company name.
 
-EMRG Media \xE2\u20AC\u201D 4 Automations for NYC's Premier Events Firm
+EMRG Media \u2014 4 Automations for NYC's Premier Events Firm
 
 Client: EMRG Media (NYC, est. 2001). Clients include Google, YouTube, Sony Music, Fiverr, Equinox.
 
 What We Built:
-1. Case Study Generator \xE2\u20AC\u201D 7-10 hours \xE2\u2020\u2019 2 hours. Publication rate: 1/quarter \xE2\u2020\u2019 2/month.
-2. EMRG Follow-Up Generator \xE2\u20AC\u201D Automated post-event follow-ups with signature management.
-3. Event Sponsor Tracker \xE2\u20AC\u201D Automated sponsor pipeline tracking and communications.
-4. Lead Scraper \xE2\u20AC\u201D Automated discovery of event planning prospects.
+1. Case Study Generator \u2014 7-10 hours \u2192 2 hours. Publication rate: 1/quarter \u2192 2/month.
+2. EMRG Follow-Up Generator \u2014 Automated post-event follow-ups with signature management.
+3. Event Sponsor Tracker \u2014 Automated sponsor pipeline tracking and communications.
+4. Lead Scraper \u2014 Automated discovery of event planning prospects.
 
 Fame Stats:
 - 3,500+ attendees at The Event Planner Expo
@@ -853,62 +853,62 @@ Permission: Case study approved with company name.`
   {
     id: "knowledge.content-playbook",
     title: "Content Playbook",
-    summary: "Content creation guide \xE2\u20AC\u201D pillars, platform rules, format specs, repurposing chain, and metrics benchmarks for multi-platform distribution",
-    bodyText: 'Content Pillars\n\nEvery content piece maps to one of five pillars.\n\n| Pillar              | What It Is                                         | Target Frequency |\n| ------------------- | -------------------------------------------------- | ---------------- |\n| dogfooding      | How we run Elevasis using our own platform         | 1-2x/week        |\n| education       | 4 Pattern Framework and AI orchestration concepts  | 1x/week          |\n| demo            | "Watch AI Work" \xE2\u20AC\u201D showing the platform in action | 1x/2 weeks       |\n| pain-point      | SMB pain points backed by data                     | 1x/week          |\n| founder-journey | Solo founder building with AI                      | 1x/week          |\n\nThe 90-10 Rule\n\n90% educational value, 10% promotional. Keeping promotional content to \\<15% ensures your audience stays receptive when you do make an offer.\n\nContent Creation Workflow\n\n1. Capture the Idea \xE2\u20AC\u201D Insert into contentitems with status: idea\n2. Draft the Source Content \xE2\u20AC\u201D Write core idea in contentitems.body. LinkedIn first.\n3. Adapt for Platforms \xE2\u20AC\u201D Repurpose from LinkedIn to YouTube, Instagram, X\n4. Schedule and Publish \xE2\u20AC\u201D Use platform-native scheduling\n5. Track Performance \xE2\u20AC\u201D Monitor in contentitems via Command Center\n\nPlatform Priority\n\n1. LinkedIn \xE2\u20AC\u201D #1 priority, 3x/week\n2. YouTube \xE2\u20AC\u201D #2 priority, 1x/week + Shorts\n3. Instagram \xE2\u20AC\u201D #3 priority, 2-3x/week, repurpose from LinkedIn/YouTube\n4. X \xE2\u20AC\u201D #4 priority, 2-3x/week, threads from LinkedIn'
+    summary: "Content creation guide \u2014 pillars, platform rules, format specs, repurposing chain, and metrics benchmarks for multi-platform distribution",
+    bodyText: 'Content Pillars\n\nEvery content piece maps to one of five pillars.\n\n| Pillar              | What It Is                                         | Target Frequency |\n| ------------------- | -------------------------------------------------- | ---------------- |\n| dogfooding      | How we run Elevasis using our own platform         | 1-2x/week        |\n| education       | 4 Pattern Framework and AI orchestration concepts  | 1x/week          |\n| demo            | "Watch AI Work" \u2014 showing the platform in action | 1x/2 weeks       |\n| pain-point      | SMB pain points backed by data                     | 1x/week          |\n| founder-journey | Solo founder building with AI                      | 1x/week          |\n\nThe 90-10 Rule\n\n90% educational value, 10% promotional. Keeping promotional content to \\<15% ensures your audience stays receptive when you do make an offer.\n\nContent Creation Workflow\n\n1. Capture the Idea \u2014 Insert into contentitems with status: idea\n2. Draft the Source Content \u2014 Write core idea in contentitems.body. LinkedIn first.\n3. Adapt for Platforms \u2014 Repurpose from LinkedIn to YouTube, Instagram, X\n4. Schedule and Publish \u2014 Use platform-native scheduling\n5. Track Performance \u2014 Monitor in contentitems via Command Center\n\nPlatform Priority\n\n1. LinkedIn \u2014 #1 priority, 3x/week\n2. YouTube \u2014 #2 priority, 1x/week + Shorts\n3. Instagram \u2014 #3 priority, 2-3x/week, repurpose from LinkedIn/YouTube\n4. X \u2014 #4 priority, 2-3x/week, threads from LinkedIn'
   },
   {
     id: "knowledge.instagram-strategy",
     title: "Instagram Strategy",
-    summary: "Comprehensive Instagram posting strategy for B2B SaaS founder content \xE2\u20AC\u201D algorithm deep dive, Reels, carousels, Stories, SEO, hashtags, captions, profile optimization, growth tactics, and analytics benchmarks (2025-2026)",
-    bodyText: 'Overview\n\nInstagram is the #3 priority platform. Carousels repurpose easily from LinkedIn, and Reels come directly from YouTube Shorts.\n\nCadence: 3-5x/week feed posts + daily Stories\n\nB2B Reality Check: Instagram is a complementary channel for B2B SaaS, not a primary lead gen tool. Decision-makers are on Instagram (76% of B2B companies use it), but they are in consumer mode.\n\nAlgorithm Deep Dive (2025-2026)\n\nReels Algorithm (Most Important for Reach)\n\nReels are designed for discovery: 55% of Reels views come from non-followers.\n\nThree priority signals:\n| Signal | Weight | How to Optimize |\n| --- | --- | --- |\n| Watch time | #1 | Hook in first 1.7s; optimize for completion |\n| Sends per reach | Highest for new audiences | "Send this to someone" content |\n| Likes per reach | Highest for followers | Valuable content followers engage with |\n\nContent Strategy\n\n- Repurpose from LinkedIn: Carousel slides \xE2\u2020\u2019 Instagram carousel\n- Repurpose from YouTube: Long-form \xE2\u2020\u2019 Reels (cut 30-60s clips)\n- Stories: Daily touchpoints, polls, Q&A, behind-the-scenes\n\nCarousel Optimization\n\n- Slide 1: Hook (bold claim or question)\n- Slides 2-9: Value delivery (one point per slide)\n- Slide 10: CTA (follow, DM, link in bio)'
+    summary: "Comprehensive Instagram posting strategy for B2B SaaS founder content \u2014 algorithm deep dive, Reels, carousels, Stories, SEO, hashtags, captions, profile optimization, growth tactics, and analytics benchmarks (2025-2026)",
+    bodyText: 'Overview\n\nInstagram is the #3 priority platform. Carousels repurpose easily from LinkedIn, and Reels come directly from YouTube Shorts.\n\nCadence: 3-5x/week feed posts + daily Stories\n\nB2B Reality Check: Instagram is a complementary channel for B2B SaaS, not a primary lead gen tool. Decision-makers are on Instagram (76% of B2B companies use it), but they are in consumer mode.\n\nAlgorithm Deep Dive (2025-2026)\n\nReels Algorithm (Most Important for Reach)\n\nReels are designed for discovery: 55% of Reels views come from non-followers.\n\nThree priority signals:\n| Signal | Weight | How to Optimize |\n| --- | --- | --- |\n| Watch time | #1 | Hook in first 1.7s; optimize for completion |\n| Sends per reach | Highest for new audiences | "Send this to someone" content |\n| Likes per reach | Highest for followers | Valuable content followers engage with |\n\nContent Strategy\n\n- Repurpose from LinkedIn: Carousel slides \u2192 Instagram carousel\n- Repurpose from YouTube: Long-form \u2192 Reels (cut 30-60s clips)\n- Stories: Daily touchpoints, polls, Q&A, behind-the-scenes\n\nCarousel Optimization\n\n- Slide 1: Hook (bold claim or question)\n- Slides 2-9: Value delivery (one point per slide)\n- Slide 10: CTA (follow, DM, link in bio)'
   },
   {
     id: "knowledge.linkedin-strategy",
     title: "LinkedIn Strategy",
-    summary: "LinkedIn posting strategy \xE2\u20AC\u201D algorithm deep dive, format rankings, hook techniques, carousel optimization, newsletter strategy, engagement tactics, profile optimization, and growth playbook for B2B SaaS (2025-2026)",
-    bodyText: 'Overview\n\nLinkedIn is the #1 priority platform. The algorithm heavily favors personal profiles over company pages. In 2025-2026, LinkedIn shifted from viral reach to depth and authority \xE2\u20AC\u201D topical consistency is now the single biggest strategic lever.\n\nCadence: 3-5x/week (Wed/Thu/Fri strongest, Monday weakest)\n\nAlgorithm Deep Dive\n\nRanking Signals (by weight)\n\n| Signal | Weight | Notes |\n| --- | --- | --- |\n| Comments | Highest | 15x more valuable than likes |\n| Saves and sends | Very high | Added to analytics in late 2025 |\n| Dwell time | High | 15+ seconds = meaningful |\n| "See more" clicks | High | Whether people expand the full post |\n| Reactions/likes | Lowest | Significantly de-emphasized |\n\nTopical Authority\n\nThe algorithm rewards consistent publishing within a defined area of expertise. Pick a lane (AI automation) and stay in it.\n\nPost Formats\n\n1. Carousels \xE2\u20AC\u201D Highest avg engagement; 10-slide with text + data\n2. Text posts \xE2\u20AC\u201D Quick takes, contrarian observations, founder stories\n3. Documents/PDFs \xE2\u20AC\u201D In-depth guides, playbooks, frameworks\n4. Videos \xE2\u20AC\u201D Native upload outperforms external links by 5x\n\nHook Techniques\n\n- Lead with the most surprising/counterintuitive insight\n- Use "I" not "we" \xE2\u20AC\u201D personal profile posts outperform company pages\n- 3 lines max before "...see more" break\n- Questions outperform statements for comments engagement'
+    summary: "LinkedIn posting strategy \u2014 algorithm deep dive, format rankings, hook techniques, carousel optimization, newsletter strategy, engagement tactics, profile optimization, and growth playbook for B2B SaaS (2025-2026)",
+    bodyText: 'Overview\n\nLinkedIn is the #1 priority platform. The algorithm heavily favors personal profiles over company pages. In 2025-2026, LinkedIn shifted from viral reach to depth and authority \u2014 topical consistency is now the single biggest strategic lever.\n\nCadence: 3-5x/week (Wed/Thu/Fri strongest, Monday weakest)\n\nAlgorithm Deep Dive\n\nRanking Signals (by weight)\n\n| Signal | Weight | Notes |\n| --- | --- | --- |\n| Comments | Highest | 15x more valuable than likes |\n| Saves and sends | Very high | Added to analytics in late 2025 |\n| Dwell time | High | 15+ seconds = meaningful |\n| "See more" clicks | High | Whether people expand the full post |\n| Reactions/likes | Lowest | Significantly de-emphasized |\n\nTopical Authority\n\nThe algorithm rewards consistent publishing within a defined area of expertise. Pick a lane (AI automation) and stay in it.\n\nPost Formats\n\n1. Carousels \u2014 Highest avg engagement; 10-slide with text + data\n2. Text posts \u2014 Quick takes, contrarian observations, founder stories\n3. Documents/PDFs \u2014 In-depth guides, playbooks, frameworks\n4. Videos \u2014 Native upload outperforms external links by 5x\n\nHook Techniques\n\n- Lead with the most surprising/counterintuitive insight\n- Use "I" not "we" \u2014 personal profile posts outperform company pages\n- 3 lines max before "...see more" break\n- Questions outperform statements for comments engagement'
   },
   {
     id: "knowledge.marketing-overview",
     title: "Marketing Overview",
     summary: "Marketing documentation for Elevasis - strategy, website infrastructure, and content systems",
-    bodyText: "Welcome to the Elevasis marketing documentation. This section covers marketing strategy, website implementation, and content systems.\n\nDocumentation\n\nStrategy\n\n- Overview \xE2\u20AC\u201D Channel strategy, inbound content system, and proof-led demand generation\n\nWebsite\n\nThe marketing website's technical infrastructure, setup, and SEO docs now live under Architecture \xE2\u2020\u2019 Website."
+    bodyText: "Welcome to the Elevasis marketing documentation. This section covers marketing strategy, website implementation, and content systems.\n\nDocumentation\n\nStrategy\n\n- Overview \u2014 Channel strategy, inbound content system, and proof-led demand generation\n\nWebsite\n\nThe marketing website's technical infrastructure, setup, and SEO docs now live under Architecture \u2192 Website."
   },
   {
     id: "knowledge.reddit-account-strategy",
     title: "Reddit Account",
-    summary: "AlexElevasis Reddit account strategy \xE2\u20AC\u201D warm-up playbook, karma thresholds, posting rules, and lead generation approach for the social monitoring pipeline.",
-    bodyText: 'Account Details\n\n| Field | Value |\n| --- | --- |\n| Username | AlexElevasis |\n| Created | 2026-03-26 |\n| Purpose | Lead generation via Reddit monitoring pipeline |\n| Persona | Alexander, founder of an AI automation company |\n\nThe username serves double duty: every helpful comment puts "Elevasis" in front of the reader.\n\nWarm-Up Playbook\n\nDays 1-3 \xE2\u20AC\u201D Cold Start:\n- Browse, upvote, follow target subs\n- 1 comment per day max\n- No links, no self-promotion, no CTAs\n\nDays 4-14 \xE2\u20AC\u201D Gradual Ramp:\n- Increase to 2-3 comments/day\n- Genuine, helpful answers \xE2\u20AC\u201D no copy-paste across threads\n- Still no links or CTAs\n\nAfter 30 Days + 100 Karma \xE2\u20AC\u201D Activation:\n- Most automod filters cleared\n- Start using monitoring pipeline drafts\n- 300+ karma unlocks more restrictive subs (r/Entrepreneur, r/startups)\n\nKarma Thresholds\n\n| Karma | Access Level |\n| --- | --- |\n| 100 | Bypasses most automod filters |\n| 300+ | Access to restrictive subs |\n| 1,000+ | Considered established community member |\n\nPosting Rules\n\n- Genuine value first \xE2\u20AC\u201D no pitching without established reputation\n- 30-day account age required before using pipeline drafts\n- Open questions in responses (not CTAs) per pipeline draft conventions'
+    summary: "AlexElevasis Reddit account strategy \u2014 warm-up playbook, karma thresholds, posting rules, and lead generation approach for the social monitoring pipeline.",
+    bodyText: 'Account Details\n\n| Field | Value |\n| --- | --- |\n| Username | AlexElevasis |\n| Created | 2026-03-26 |\n| Purpose | Lead generation via Reddit monitoring pipeline |\n| Persona | Alexander, founder of an AI automation company |\n\nThe username serves double duty: every helpful comment puts "Elevasis" in front of the reader.\n\nWarm-Up Playbook\n\nDays 1-3 \u2014 Cold Start:\n- Browse, upvote, follow target subs\n- 1 comment per day max\n- No links, no self-promotion, no CTAs\n\nDays 4-14 \u2014 Gradual Ramp:\n- Increase to 2-3 comments/day\n- Genuine, helpful answers \u2014 no copy-paste across threads\n- Still no links or CTAs\n\nAfter 30 Days + 100 Karma \u2014 Activation:\n- Most automod filters cleared\n- Start using monitoring pipeline drafts\n- 300+ karma unlocks more restrictive subs (r/Entrepreneur, r/startups)\n\nKarma Thresholds\n\n| Karma | Access Level |\n| --- | --- |\n| 100 | Bypasses most automod filters |\n| 300+ | Access to restrictive subs |\n| 1,000+ | Considered established community member |\n\nPosting Rules\n\n- Genuine value first \u2014 no pitching without established reputation\n- 30-day account age required before using pipeline drafts\n- Open questions in responses (not CTAs) per pipeline draft conventions'
   },
   {
     id: "knowledge.reddit-monitoring-playbook",
     title: "Social Monitoring",
-    summary: "Automated Reddit monitoring pipeline \xE2\u20AC\u201D 4-step workflow (search, LLM score, LLM draft, store) with tiered subreddit scraping via Apify, claude-sonnet-5 scoring and response drafting, and lead-gen optimized responses via the AlexElevasis account.",
-    bodyText: "Overview\n\nSocial monitoring surfaces Reddit posts where business owners discuss operational challenges, manual processes, and automation needs.\n\nCron Trigger (3x/day: 16:00, 22:00, 04:00 UTC)\n    \xE2\u2020\u2019 mnt-reddit-monitor-workflow (4-step pipeline)\n        \xE2\u2020\u2019 Step 1: Search \xE2\u20AC\u201D 4 sequential Apify actors (one per tier)\n        \xE2\u2020\u2019 Step 2: Score \xE2\u20AC\u201D claude-sonnet-5 (concurrency 5)\n        \xE2\u2020\u2019 Step 3: Draft \xE2\u20AC\u201D claude-sonnet-5 (high-score only)\n        \xE2\u2020\u2019 Step 4: Report \xE2\u20AC\u201D Store to acqsocialposts, log breakdown\n    \xE2\u2020\u2019 Command Center: /acquisition/monitoring\n\nStatus: Paused until further notice (2026-03-31). Pipeline technically validated but ROI is low without deep vertical expertise.\n\nVelocity Batches\n\nSubreddits grouped by posting velocity, each with its own maxPostsPerSource.\n\n| Batch | Subs | Posts/Source | Example Subreddits |\n| --- | --- | --- | --- |\n| Medium Velocity | 2 | 5 | Accounting, Plumbing |\n| Buyer Low-Volume | 10 | 3 | CRM, EntrepreneurRideAlong, sweatystartup |\n| Trade Niche | 10 | 2 | electricians, Dentists, InsuranceAgent |\n| Decision Niche | 3 | 2 | logistics, FreightBrokers, healthIT |\n\nScoring\n\nPosts scored 0-100 by claude-sonnet-5 for business automation opportunity relevance. Posts scoring \\>= 60 get response drafts via claude-sonnet-5.\n\nAlexElevasis Account\n\nAll responses posted via the AlexElevasis Reddit account. See Reddit Account strategy doc for warmup playbook and karma thresholds."
+    summary: "Automated Reddit monitoring pipeline \u2014 4-step workflow (search, LLM score, LLM draft, store) with tiered subreddit scraping via Apify, claude-sonnet-5 scoring and response drafting, and lead-gen optimized responses via the AlexElevasis account.",
+    bodyText: "Overview\n\nSocial monitoring surfaces Reddit posts where business owners discuss operational challenges, manual processes, and automation needs.\n\nCron Trigger (3x/day: 16:00, 22:00, 04:00 UTC)\n    \u2192 mnt-reddit-monitor-workflow (4-step pipeline)\n        \u2192 Step 1: Search \u2014 4 sequential Apify actors (one per tier)\n        \u2192 Step 2: Score \u2014 claude-sonnet-5 (concurrency 5)\n        \u2192 Step 3: Draft \u2014 claude-sonnet-5 (high-score only)\n        \u2192 Step 4: Report \u2014 Store to acqsocialposts, log breakdown\n    \u2192 Command Center: /acquisition/monitoring\n\nStatus: Paused until further notice (2026-03-31). Pipeline technically validated but ROI is low without deep vertical expertise.\n\nVelocity Batches\n\nSubreddits grouped by posting velocity, each with its own maxPostsPerSource.\n\n| Batch | Subs | Posts/Source | Example Subreddits |\n| --- | --- | --- | --- |\n| Medium Velocity | 2 | 5 | Accounting, Plumbing |\n| Buyer Low-Volume | 10 | 3 | CRM, EntrepreneurRideAlong, sweatystartup |\n| Trade Niche | 10 | 2 | electricians, Dentists, InsuranceAgent |\n| Decision Niche | 3 | 2 | logistics, FreightBrokers, healthIT |\n\nScoring\n\nPosts scored 0-100 by claude-sonnet-5 for business automation opportunity relevance. Posts scoring \\>= 60 get response drafts via claude-sonnet-5.\n\nAlexElevasis Account\n\nAll responses posted via the AlexElevasis Reddit account. See Reddit Account strategy doc for warmup playbook and karma thresholds."
   },
   {
     id: "knowledge.seo-content-guide",
     title: "SEO Content Writing Guide",
-    summary: "Tactical guide for writing SEO and AEO-optimized content \xE2\u20AC\u201D page structure, keyword strategy, AI engine citation optimization, E-E-A-T signals, and CTA patterns.",
-    bodyText: 'Overview\n\nThis guide covers how to write SEO content that ranks in traditional search AND gets cited by AI answer engines \xE2\u20AC\u201D ChatGPT, Perplexity, Google AI Overviews, and Gemini.\n\nThe distribution channel is split: 69% of Google searches result in zero clicks, while AI platforms generated 1.13 billion referral visits in June 2025 alone.\n\nPage Structure\n\nSection Architecture\n\nEvery section must be self-contained. AI engines extract individual passages, not full pages.\n\n- Lead with a 30-50 word standalone answer in the first sentence of each section\n- Paragraphs: 2-4 sentences max\n- 78% of AI Overview answers use list format -- use bullets and numbered lists extensively\n- Heading hierarchy: one H1 (page title), H2 for major sections, H3 for subsections\n- Frame headings as questions when possible\n\nSection Length\n\n- Pillar pages: 2,000-3,000 words total\n- Cluster pages: 1,000-2,000 words total\n- Each major section: 150-300 words\n\nConciseness Rules\n\n1. Two-paragraph intro max\n2. No stat duplication between intro and problem section\n3. Section character budget: Intro 450-600 chars, Problem 250-400 chars, Solution 300-550 chars\n\nE-E-A-T Signals\n\n- Brand name "Elevasis" must appear explicitly minimum 3x per page\n- Vertical names used as proper noun concepts\n- Organization + Service + SoftwareApplication schema markup reinforces entity recognition'
+    summary: "Tactical guide for writing SEO and AEO-optimized content \u2014 page structure, keyword strategy, AI engine citation optimization, E-E-A-T signals, and CTA patterns.",
+    bodyText: 'Overview\n\nThis guide covers how to write SEO content that ranks in traditional search AND gets cited by AI answer engines \u2014 ChatGPT, Perplexity, Google AI Overviews, and Gemini.\n\nThe distribution channel is split: 69% of Google searches result in zero clicks, while AI platforms generated 1.13 billion referral visits in June 2025 alone.\n\nPage Structure\n\nSection Architecture\n\nEvery section must be self-contained. AI engines extract individual passages, not full pages.\n\n- Lead with a 30-50 word standalone answer in the first sentence of each section\n- Paragraphs: 2-4 sentences max\n- 78% of AI Overview answers use list format -- use bullets and numbered lists extensively\n- Heading hierarchy: one H1 (page title), H2 for major sections, H3 for subsections\n- Frame headings as questions when possible\n\nSection Length\n\n- Pillar pages: 2,000-3,000 words total\n- Cluster pages: 1,000-2,000 words total\n- Each major section: 150-300 words\n\nConciseness Rules\n\n1. Two-paragraph intro max\n2. No stat duplication between intro and problem section\n3. Section character budget: Intro 450-600 chars, Problem 250-400 chars, Solution 300-550 chars\n\nE-E-A-T Signals\n\n- Brand name "Elevasis" must appear explicitly minimum 3x per page\n- Vertical names used as proper noun concepts\n- Organization + Service + SoftwareApplication schema markup reinforces entity recognition'
   },
   {
     id: "knowledge.seo-distribution-playbook",
     title: "Distribution & Citation Building",
-    summary: "Post-publish distribution playbook \xE2\u20AC\u201D AI crawler discovery, directory citations, Google Business Profile, community seeding, monitoring cadence, and AEO optimization tactics.",
+    summary: "Post-publish distribution playbook \u2014 AI crawler discovery, directory citations, Google Business Profile, community seeding, monitoring cadence, and AEO optimization tactics.",
     bodyText: 'Overview\n\nEverything that happens after pages are published and sitemap/IndexNow pings are sent. Evergreen reference for maximizing visibility across traditional search, AI answer engines, and buyer-intent directories.\n\nAI Crawler Discovery\n\nllms.txt\n\nA plain-text Markdown file at the domain root that gives LLMs a structured map of key content. Location: apps/website/public/llms.txt.\n\nUpdate whenever pillar or cluster pages are published.\n\nSitemap Segmentation\n\n| Segment ID | Contents | Priority |\n| --- | --- | --- |\n| 0 | Static pages | Default |\n| 1 | Pillar pages (9) | 0.9 |\n| 2 | Cluster pages (52) | 0.8 |\n\nEntity Density Rules\n\nPages with 15+ recognized entities show 4.8x higher selection probability for AI citations.\n- Brand name "Elevasis" must appear explicitly (minimum 3x per page)\n- Stat density target: one statistic every 150-200 words\n\nDirectory Citations\n\nTier 1 (Buyer Intent): G2, Capterra, Product Hunt, AppSumo (direct buyer intent, high domain authority)\n\nTier 2 (Authority): Crunchbase, AngelList, LinkedIn company page, industry association directories\n\nGoogle Business Profile\n\nClaim and verify GBP listing. Category: "Software Company". Keep NAP (Name, Address, Phone) consistent across all citations.'
   },
   {
     id: "knowledge.seo-playbook",
     title: "SEO Playbook",
-    summary: "Operational playbook for the SEO/AEO system \xE2\u20AC\u201D vertical launch workflow, content quality gates, AEO formatting rules, stale content management, metrics interpretation, and rollout phases.",
+    summary: "Operational playbook for the SEO/AEO system \u2014 vertical launch workflow, content quality gates, AEO formatting rules, stale content management, metrics interpretation, and rollout phases.",
     bodyText: "Vertical Launch Workflow\n\nEnd-to-end process for launching a new vertical (e.g., hvac-contractors):\n\nStep 1: Research vertical data\n\nFind real, citable industry statistics: pain points, automation ROI, market context. Sources: trade associations, industry surveys, government data (BLS, Census).\n\nStep 2: Generate pages\n\nbash\nPillar page\npnpm tsx scripts/seo/generate-pages.ts --vertical hvac-contractors --type pillar --dry-run\npnpm tsx scripts/seo/generate-pages.ts --vertical hvac-contractors --type pillar\n\nCluster pages\npnpm tsx scripts/seo/generate-pages.ts --vertical hvac-contractors --type cluster\n\nStep 3: Backfill chart data\n\nCharts require post-generation patching. Write chart patch files using Step 1 research, then apply via content.ts patch.\n\nStep 4: AEO optimization\n\nEvery section must be self-contained. AI engines extract individual passages, not full pages.\n- Lead with a 30-50 word standalone answer in the first sentence of each section\n- 78% of AI Overview answers use list format\n- Frame headings as questions when possible\n\nStep 5: Post-publish distribution\n\nUpdate llms.txt, ping IndexNow, submit sitemap segments to Search Console.\n\nData Sourcing Rules\n\n- Tier 1 (Verified): Named source, specific methodology. Use confidently.\n- Tier 2 (Plausible): Widely cited, directionally correct. Soften the specific number.\n- Tier 3 (Unverified): No credible source. Do not use specific numbers."
   },
   {
     id: "knowledge.x-strategy",
     title: "X (Twitter) Strategy",
-    summary: "X/Twitter posting strategy \xE2\u20AC\u201D algorithm signals, thread tactics, engagement weights, Premium ROI, video specs, growth playbook, and B2B SaaS niche tactics",
-    bodyText: "Overview\n\nX is the #4 priority platform. Most content is repurposed from LinkedIn text posts as threads.\n\nCadence: 3-5 posts/day (mix of original posts + replies + quote tweets), 2-3 threads/week\n\nPrerequisite: Get X Premium ($8/mo) \xE2\u20AC\u201D verified accounts get 10x more impressions. Non-Premium accounts posting links receive near-zero engagement as of 2026.\n\nAlgorithm Deep Dive\n\nEngagement Weight Scoring\n\n| Signal | Weight | vs. Like |\n| --- | --- | --- |\n| Reply engaged by author | +75 | 150x |\n| Reply | +13.5 | 27x |\n| Profile click + engagement | +12.0 | 24x |\n| Bookmark | +10.0 | 20x |\n| Retweet | +1.0 | 2x |\n| Like | +0.5 | 1x |\n\nCritical takeaway: Replying to your own replies is worth 150x a like.\n\nPenalties\n\n- External links: 30-50% reach reduction\n- Multiple hashtags: 40% penalty\n\nThread Strategy\n\n- First tweet = hook (bold claim or surprising stat)\n- 5-10 tweets per thread\n- Last tweet = CTA (follow for more, link to extended content)\n- Reply to your own threads within the first hour to boost algorithmic velocity"
+    summary: "X/Twitter posting strategy \u2014 algorithm signals, thread tactics, engagement weights, Premium ROI, video specs, growth playbook, and B2B SaaS niche tactics",
+    bodyText: "Overview\n\nX is the #4 priority platform. Most content is repurposed from LinkedIn text posts as threads.\n\nCadence: 3-5 posts/day (mix of original posts + replies + quote tweets), 2-3 threads/week\n\nPrerequisite: Get X Premium ($8/mo) \u2014 verified accounts get 10x more impressions. Non-Premium accounts posting links receive near-zero engagement as of 2026.\n\nAlgorithm Deep Dive\n\nEngagement Weight Scoring\n\n| Signal | Weight | vs. Like |\n| --- | --- | --- |\n| Reply engaged by author | +75 | 150x |\n| Reply | +13.5 | 27x |\n| Profile click + engagement | +12.0 | 24x |\n| Bookmark | +10.0 | 20x |\n| Retweet | +1.0 | 2x |\n| Like | +0.5 | 1x |\n\nCritical takeaway: Replying to your own replies is worth 150x a like.\n\nPenalties\n\n- External links: 30-50% reach reduction\n- Multiple hashtags: 40% penalty\n\nThread Strategy\n\n- First tweet = hook (bold claim or surprising stat)\n- 5-10 tweets per thread\n- Last tweet = CTA (follow for more, link to extended content)\n- Reply to your own threads within the first hour to boost algorithmic velocity"
   },
   {
     id: "knowledge.youtube-obs-recording-setup",
@@ -1164,23 +1164,23 @@ Pre-Recording Checklist
   {
     id: "knowledge.youtube-channel-strategy",
     title: "Channel Strategy",
-    summary: 'Unified YouTube channel strategy \xE2\u20AC\u201D channel setup, content pipeline, differentiation positioning, launch queue, and production workflow for "Alexander Le | Elevasis" channel',
+    summary: 'Unified YouTube channel strategy \u2014 channel setup, content pipeline, differentiation positioning, launch queue, and production workflow for "Alexander Le | Elevasis" channel',
     bodyText: `Objective
 
-Build the "Alexander Le | Elevasis" YouTube channel as an evergreen discovery engine for Elevasis. YouTube is the #1 content priority \xE2\u20AC\u201D evergreen discovery, SEO compounding, and 53% of B2B buyers watch video before requesting demos.
+Build the "Alexander Le | Elevasis" YouTube channel as an evergreen discovery engine for Elevasis. YouTube is the #1 content priority \u2014 evergreen discovery, SEO compounding, and 53% of B2B buyers watch video before requesting demos.
 
 Channel Identity
 
-- Name: "Alexander Le | Elevasis" \xE2\u20AC\u201D personal-brand hybrid with clear business association
+- Name: "Alexander Le | Elevasis" \u2014 personal-brand hybrid with clear business association
 - Handle: @AlexanderElevasis
 - Why personal-brand hybrid: People subscribe to people. Algorithm favors creator-branded channels over faceless brands.
 
-Content Format: Face Bubble Intro \xE2\u2020\u2019 Screen Recording
+Content Format: Face Bubble Intro \u2192 Screen Recording
 
 Primary format: Quick face-cam intro (circle overlay, 15-30s) to build trust, then full-screen recording.
 
 Why this works:
-- 40%+ of YouTube's top 1,000 channels never show a presenter \xE2\u20AC\u201D faceless works
+- 40%+ of YouTube's top 1,000 channels never show a presenter \u2014 faceless works
 - Screen recording tutorials rank extremely well on YouTube + Google
 - Face in thumbnails gets 921K more views on average
 
@@ -1189,7 +1189,7 @@ Differentiation
 Compete on substance, not production quality:
 - Real execution data, real costs, real results (not simulations)
 - "Document the build" format: record while building, editing, deploying
-- Show Command Center in action \xE2\u20AC\u201D no equivalent content exists
+- Show Command Center in action \u2014 no equivalent content exists
 
 Launch Queue
 
@@ -1202,15 +1202,15 @@ Launch Queue
     id: "knowledge.youtube-growth-playbook",
     title: "YouTube Growth Playbook",
     summary: "Practical YouTube optimization guide for Elevasis screen-recorded demos, founder-led walkthroughs, Shorts, SEO, and launch review loops",
-    bodyText: 'Overview\n\nThis playbook maps YouTube growth tactics to the current Elevasis content format: screen recordings, Command Center walkthroughs, founder commentary, proof assets, and short clips cut from real demos.\n\nThe goal is to make real AI orchestration visible enough that buyers and technical peers understand what Elevasis does.\n\nCore Format\n\n| Format | Use For | Notes |\n| --- | --- | --- |\n| Face intro \xE2\u2020\u2019 screen recording | Flagship demos, founder-led walkthroughs | 15-30 second intro, then full-screen product work |\n| Screen recording only | Tutorials, Shorts source material | Fastest to produce |\n| Data walkthrough | Campaign metrics, cost tracking, workflow results | Use only real data |\n| Concept explainer | AI agents, orchestration, human oversight | Keep tied to concrete business workflows |\n\nCTR Optimization\n\nThumbnails should show the result or system, not abstract concepts:\n1. Command Center, workflow graph, campaign analytics, or visible output\n2. Optional face overlay when it improves trust\n3. Three to five words of context. High contrast, readable at mobile size.\n\nTitle rules:\n- Front-load the topic\n- Use real numbers only when current and verifiable\n- Prefer "Watch", "Real", "Live", "Actual", "Walkthrough" over hype language\n- Make the title and thumbnail say different things\n\nRetention\n\nOpen with the payoff:\n1. Show the final dashboard, result, or workflow output\n2. Explain what the viewer is about to see\n3. Switch into the walkthrough quickly\n\nFirst-24-Hour Workflow\n\nAlgorithm watches first 30-60 minutes closely. A video getting 10 replies in 15 minutes dramatically outperforms one getting 10 replies over 24 hours.'
+    bodyText: 'Overview\n\nThis playbook maps YouTube growth tactics to the current Elevasis content format: screen recordings, Command Center walkthroughs, founder commentary, proof assets, and short clips cut from real demos.\n\nThe goal is to make real AI orchestration visible enough that buyers and technical peers understand what Elevasis does.\n\nCore Format\n\n| Format | Use For | Notes |\n| --- | --- | --- |\n| Face intro \u2192 screen recording | Flagship demos, founder-led walkthroughs | 15-30 second intro, then full-screen product work |\n| Screen recording only | Tutorials, Shorts source material | Fastest to produce |\n| Data walkthrough | Campaign metrics, cost tracking, workflow results | Use only real data |\n| Concept explainer | AI agents, orchestration, human oversight | Keep tied to concrete business workflows |\n\nCTR Optimization\n\nThumbnails should show the result or system, not abstract concepts:\n1. Command Center, workflow graph, campaign analytics, or visible output\n2. Optional face overlay when it improves trust\n3. Three to five words of context. High contrast, readable at mobile size.\n\nTitle rules:\n- Front-load the topic\n- Use real numbers only when current and verifiable\n- Prefer "Watch", "Real", "Live", "Actual", "Walkthrough" over hype language\n- Make the title and thumbnail say different things\n\nRetention\n\nOpen with the payoff:\n1. Show the final dashboard, result, or workflow output\n2. Explain what the viewer is about to see\n3. Switch into the walkthrough quickly\n\nFirst-24-Hour Workflow\n\nAlgorithm watches first 30-60 minutes closely. A video getting 10 replies in 15 minutes dramatically outperforms one getting 10 replies over 24 hours.'
   },
   {
     id: "knowledge.youtube-mental-prep",
-    title: "Mental Preparation \xE2\u20AC\u201D Creator Anxiety Playbook",
-    summary: "Research-backed strategies for overcoming publishing anxiety, the spotlight effect, graduated exposure, and building comfort on camera \xE2\u20AC\u201D practical guide for a technical founder starting YouTube",
+    title: "Mental Preparation \u2014 Creator Anxiety Playbook",
+    summary: "Research-backed strategies for overcoming publishing anxiety, the spotlight effect, graduated exposure, and building comfort on camera \u2014 practical guide for a technical founder starting YouTube",
     bodyText: `Why This Exists
 
-Recording yourself and putting your ideas out publicly is genuinely uncomfortable. This doc captures the research and practical strategies so you can reference them when the anxiety spikes \xE2\u20AC\u201D not as motivation, but as evidence that the discomfort is normal, finite, and navigable.
+Recording yourself and putting your ideas out publicly is genuinely uncomfortable. This doc captures the research and practical strategies so you can reference them when the anxiety spikes \u2014 not as motivation, but as evidence that the discomfort is normal, finite, and navigable.
 
 The Core Insight
 
@@ -1220,15 +1220,15 @@ What You're Actually Afraid Of
 
 The Spotlight Effect (Gilovich et al., 2000)
 
-People overestimate how much others notice and judge them by roughly 2x. Early videos get almost zero views \xE2\u20AC\u201D you're practicing in an empty room.
+People overestimate how much others notice and judge them by roughly 2x. Early videos get almost zero views \u2014 you're practicing in an empty room.
 
 The Five Common Fears (in order of prevalence)
 
-1. Judgment from people you know \xE2\u20AC\u201D not strangers. The #1 blocker.
-2. Perfectionism as procrastination \xE2\u20AC\u201D "I'll start when I have better equipment." This is avoidance.
-3. Impostor syndrome \xE2\u20AC\u201D "Who am I to teach this?"
-4. Permanence anxiety \xE2\u20AC\u201D "This will be on the internet forever"
-5. Voice/face aversion \xE2\u20AC\u201D Most people dislike their recorded voice (bone conduction gap)
+1. Judgment from people you know \u2014 not strangers. The #1 blocker.
+2. Perfectionism as procrastination \u2014 "I'll start when I have better equipment." This is avoidance.
+3. Impostor syndrome \u2014 "Who am I to teach this?"
+4. Permanence anxiety \u2014 "This will be on the internet forever"
+5. Voice/face aversion \u2014 Most people dislike their recorded voice (bone conduction gap)
 
 The Real Fear: Cringe
 
@@ -1236,16 +1236,16 @@ People tolerate a video that flops quietly. What they can't tolerate is creating
 
 Graduated Exposure Protocol
 
-1. Screen recording only (no face, no voice) \xE2\u20AC\u201D 2 videos
-2. Screen recording + voiceover (no face) \xE2\u20AC\u201D 5 videos
-3. Face bubble intro (15-30s) + screen recording \xE2\u20AC\u201D ongoing
+1. Screen recording only (no face, no voice) \u2014 2 videos
+2. Screen recording + voiceover (no face) \u2014 5 videos
+3. Face bubble intro (15-30s) + screen recording \u2014 ongoing
 
 Each stage desensitizes one fear at a time. Never skip ahead. The goal is consistency, not perfection.`
   },
   {
     id: "knowledge.youtube-tactics",
     title: "YouTube Strategy",
-    summary: "YouTube posting strategy \xE2\u20AC\u201D upload optimization, Shorts tactics, algorithm signals, SEO, first-48-hour playbook, faceless content tips, and small channel growth for B2B SaaS",
+    summary: "YouTube posting strategy \u2014 upload optimization, Shorts tactics, algorithm signals, SEO, first-48-hour playbook, faceless content tips, and small channel growth for B2B SaaS",
     bodyText: `Overview
 
 YouTube is the #2 priority platform and the only one with true evergreen discovery. Videos keep gaining views months/years after posting.
@@ -1262,11 +1262,11 @@ Title
 Thumbnail
 - 1280x720px, 16:9, max 2MB
 - 4 words max of bold, high-contrast text
-- Use YouTube's Test & Compare \xE2\u20AC\u201D upload 3 thumbnails, YouTube A/B tests and reports CTR
+- Use YouTube's Test & Compare \u2014 upload 3 thumbnails, YouTube A/B tests and reports CTR
 
 Description
 - First 125 chars = what shows in search results
-- Add timestamps/chapters \xE2\u20AC\u201D improve retention + create extra search ranking hooks
+- Add timestamps/chapters \u2014 improve retention + create extra search ranking hooks
 
 Shorts Strategy
 
@@ -1279,7 +1279,7 @@ First-48-Hour Playbook
 1. Publish during peak hours (12pm-3pm ET Tuesday-Thursday)
 2. Post about the video on LinkedIn immediately after upload
 3. Reply to every comment within the first 24 hours
-4. Share in relevant communities (not spam \xE2\u20AC\u201D genuine value)`
+4. Share in relevant communities (not spam \u2014 genuine value)`
   },
   {
     id: "knowledge.finance-operations-playbook",
@@ -1301,7 +1301,7 @@ The 4 Principles
 
 Principle: AI must work with your existing tools, not replace them.
 
-AI that doesn't connect to your CRM, your email, your calendar, your existing workflows is a toy. Real AI automation works WITH what you already have \xE2\u20AC\u201D not instead of it.
+AI that doesn't connect to your CRM, your email, your calendar, your existing workflows is a toy. Real AI automation works WITH what you already have \u2014 not instead of it.
 
 - Your 50 Zapier workflows keep running
 - Your CRM stays your CRM
@@ -1313,7 +1313,7 @@ The anti-pattern: "Use our AI instead of everything else." Creates vendor lock-i
 
 Principle: AI must learn from every decision and improve continuously.
 
-Static automation is just fancy if-then logic. Real AI captures every approval, rejection, and edit \xE2\u20AC\u201D then uses that data to get smarter.
+Static automation is just fancy if-then logic. Real AI captures every approval, rejection, and edit \u2014 then uses that data to get smarter.
 
 The anti-pattern: "Set it and forget it." Systems that don't learn stay dumb forever.
 
@@ -1321,7 +1321,7 @@ The anti-pattern: "Set it and forget it." Systems that don't learn stay dumb for
 
 Principle: You must be able to see what AI systems are doing in real-time.
 
-Black-box automation is unacceptable for business operations. You need to see every action, every decision, every cost \xE2\u20AC\u201D as it happens.
+Black-box automation is unacceptable for business operations. You need to see every action, every decision, every cost \u2014 as it happens.
 
 - Real-time activity feeds showing what's executing
 - Cost tracking per workflow, per execution
@@ -1334,7 +1334,7 @@ The anti-pattern: "It just works, trust us." Systems without observability creat
 
 Principle: Humans must approve important actions before execution.
 
-AI should handle the grunt work. But critical decisions \xE2\u20AC\u201D sending emails to prospects, updating customer records, publishing content \xE2\u20AC\u201D require human approval.
+AI should handle the grunt work. But critical decisions \u2014 sending emails to prospects, updating customer records, publishing content \u2014 require human approval.
 
 - AI researches 50 prospects and drafts personalized emails
 - Before anything sends, it lands in your approval queue
@@ -1347,7 +1347,7 @@ The anti-pattern: "Fully autonomous AI." Systems without governance create risk
     id: "knowledge.communications-map",
     title: "Communications Map",
     summary: "All lead-facing messages across the active client acquisition pipeline (stages 01-03). Stages 04-08 communications are archived.",
-    bodyText: 'Overview\n\nEvery message sent to a lead across the active acquisition pipeline \xE2\u20AC\u201D outreach, follow-ups, reminders, and event-triggered emails. 10 total active messages (3 outreach + 1 reply + 2 subsequent reply + 2 discovery reminders + 1 timeout follow-up + 1 timeout re-engagement).\n\nStages 04-08 communications (proposal follow-ups, payment reminders, nurture sequences) are archived.\n\nActive Pipeline Phases\n\n1. Outreach (Instantly)  2. Reply Handling     3. Discovery Reminders\n 3 emails                 1 email + 2 HITL      2 reminders\n Day 0/3/7                On reply              -24h/-1h\n\nPhase 1: Outreach (Instantly)\n\n| # | Day | Subject | Angle | Purpose |\n| --- | --- | --- | --- | --- |\n| 1 | 0 | idea for {{companyName}} | Earn attention | Personal, specific |\n| 2 | 3 | where do business hours actually go? | New angle | Peer-level, intriguing |\n| 3 | 7 | the offer (whenever useful) | Permission to close | Warm, zero pressure |\n\nPhase 2: Reply Handling (Resend)\n\nSent only to INTERESTED replies. LLM drafts; admin approves via HITL before sending.\n\nPhase 3: Discovery Reminders (Resend)\n\nTwo automated reminders per booking:\n- -24h: "Looking forward to our call tomorrow"\n- -1h: "See you in 1 hour" with discovery form link\n\nAll scheduled/event emails signed "Alex". Plain text.'
+    bodyText: 'Overview\n\nEvery message sent to a lead across the active acquisition pipeline \u2014 outreach, follow-ups, reminders, and event-triggered emails. 10 total active messages (3 outreach + 1 reply + 2 subsequent reply + 2 discovery reminders + 1 timeout follow-up + 1 timeout re-engagement).\n\nStages 04-08 communications (proposal follow-ups, payment reminders, nurture sequences) are archived.\n\nActive Pipeline Phases\n\n1. Outreach (Instantly)  2. Reply Handling     3. Discovery Reminders\n 3 emails                 1 email + 2 HITL      2 reminders\n Day 0/3/7                On reply              -24h/-1h\n\nPhase 1: Outreach (Instantly)\n\n| # | Day | Subject | Angle | Purpose |\n| --- | --- | --- | --- | --- |\n| 1 | 0 | idea for {{companyName}} | Earn attention | Personal, specific |\n| 2 | 3 | where do business hours actually go? | New angle | Peer-level, intriguing |\n| 3 | 7 | the offer (whenever useful) | Permission to close | Warm, zero pressure |\n\nPhase 2: Reply Handling (Resend)\n\nSent only to INTERESTED replies. LLM drafts; admin approves via HITL before sending.\n\nPhase 3: Discovery Reminders (Resend)\n\nTwo automated reminders per booking:\n- -24h: "Looking forward to our call tomorrow"\n- -1h: "See you in 1 hour" with discovery form link\n\nAll scheduled/event emails signed "Alex". Plain text.'
   },
   {
     id: "knowledge.org-model-actions",
@@ -1526,13 +1526,13 @@ Related References
     id: "knowledge.understanding-elevasis",
     title: "Understanding Elevasis Overview",
     summary: "Company overview, product positioning, and platform systems context for Elevasis AI orchestration platform",
-    bodyText: "Lean documentation explaining what Elevasis is and what the platform can do. This section provides the foundational context for business conversations and technical evaluation.\n\nElevasis is a done-for-you AI automation service backed by a production-grade platform. The company targets service-based SMBs (2-50 employees, $200K-$5M revenue) who are too busy serving clients to grow their own business.\n\nKey Facts\n\n- Stage: Pre-revenue, platform 100% complete, client acquisition active\n- Offer: Done-for-you AI automation -- we build and maintain the workflows, no coding required\n- ICP: Service-based SMBs (2-50 employees, $200K-$5M revenue, USA)\n- Pricing: $500-$2k/mo (Foundation) \xE2\u2020\u2019 $2k-$5k/mo (Scaled) \xE2\u2020\u2019 $5k-$15k+/mo (AI-Powered)\n- Market: Early Adopters stage, $23.77B TAM growing to $87.7B by 2032\n- Competitive position: No dominant done-for-you SMB AI provider exists; blue ocean\n\nWhen to Use Each Document\n\n| Situation | Document |\n| --- | --- |\n| First conversation with any audience | What is Elevasis |\n| Technical evaluation or demo prep | Platform Systems Overview |\n\nDocumentation\n\n- What is Elevasis \xE2\u20AC\u201D AI orchestration platform overview, company stage, value proposition, and pricing tiers\n- Platform Systems Overview \xE2\u20AC\u201D Authoritative overview of what is built, what each system does, and how the pieces fit together"
+    bodyText: "Lean documentation explaining what Elevasis is and what the platform can do. This section provides the foundational context for business conversations and technical evaluation.\n\nElevasis is a done-for-you AI automation service backed by a production-grade platform. The company targets service-based SMBs (2-50 employees, $200K-$5M revenue) who are too busy serving clients to grow their own business.\n\nKey Facts\n\n- Stage: Pre-revenue, platform 100% complete, client acquisition active\n- Offer: Done-for-you AI automation -- we build and maintain the workflows, no coding required\n- ICP: Service-based SMBs (2-50 employees, $200K-$5M revenue, USA)\n- Pricing: $500-$2k/mo (Foundation) \u2192 $2k-$5k/mo (Scaled) \u2192 $5k-$15k+/mo (AI-Powered)\n- Market: Early Adopters stage, $23.77B TAM growing to $87.7B by 2032\n- Competitive position: No dominant done-for-you SMB AI provider exists; blue ocean\n\nWhen to Use Each Document\n\n| Situation | Document |\n| --- | --- |\n| First conversation with any audience | What is Elevasis |\n| Technical evaluation or demo prep | Platform Systems Overview |\n\nDocumentation\n\n- What is Elevasis \u2014 AI orchestration platform overview, company stage, value proposition, and pricing tiers\n- Platform Systems Overview \u2014 Authoritative overview of what is built, what each system does, and how the pieces fit together"
   },
   {
     id: "knowledge.what-is-elevasis",
     title: "What is Elevasis",
     summary: "Company overview, positioning, value proposition, and pricing for the AI orchestration platform",
-    bodyText: 'Executive Summary\n\nCompany: Bootstrapped AI orchestration platform for done-for-you business automation\n\nFounder: Solo (Alex, 34), bootstrapped\n\nMarket: Service-based SMBs that need practical AI automation without building internal AI teams\n\nGTM: Content-led marketing, proof assets, consultative sales, and land-and-expand pricing\n\nCompany Overview\n\nCurrent Status\n\nThe platform core is production-ready enough to support client-facing demonstrations and implementation work. Current business focus is client acquisition, proof-building, and turning the platform into a repeatable service delivery system.\n\nFounder Profile\n\nAlex, 34 \xE2\u20AC\u201D Solo founder with software engineering background (BSCS degree). Previous: Ecommerce platforms, Streaming technology. No formal AI background \xE2\u20AC\u201D practitioner, not academic.\n\nWhat We Are\n\nOperating layer for AI automation. We help SMBs operate with closed-loop feedback, decision capture, and continuous learning \xE2\u20AC\u201D at SMB pricing with done-for-you implementation (NOT self-service).\n\nTarget Market\n\nICP: Service-based SMBs (2-50 employees, USA, $200K-$5M revenue)\n\nCore Pain: Capacity crisis, pipeline problems, operational chaos, growth blockers \xE2\u20AC\u201D too busy serving clients to grow their own business.\n\nPricing (Land-and-Expand)\n\n- Tier 1 \xE2\u20AC\u201D Foundation (1-2 workflows): $500-2k/mo\n- Tier 2 \xE2\u20AC\u201D Scaled Operations (3-5 workflows): $2k-5k/mo\n- Tier 3 \xE2\u20AC\u201D AI-Powered Systems (6+ workflows): $5k-15k+/mo\n\nAdditional workflows cost less due to shared infrastructure.\n\nValue Proposition\n\n"We find one bottleneck in your business, build an AI solution to fix it, and you only pay if it actually saves you time or makes you money."'
+    bodyText: 'Executive Summary\n\nCompany: Bootstrapped AI orchestration platform for done-for-you business automation\n\nFounder: Solo (Alex, 34), bootstrapped\n\nMarket: Service-based SMBs that need practical AI automation without building internal AI teams\n\nGTM: Content-led marketing, proof assets, consultative sales, and land-and-expand pricing\n\nCompany Overview\n\nCurrent Status\n\nThe platform core is production-ready enough to support client-facing demonstrations and implementation work. Current business focus is client acquisition, proof-building, and turning the platform into a repeatable service delivery system.\n\nFounder Profile\n\nAlex, 34 \u2014 Solo founder with software engineering background (BSCS degree). Previous: Ecommerce platforms, Streaming technology. No formal AI background \u2014 practitioner, not academic.\n\nWhat We Are\n\nOperating layer for AI automation. We help SMBs operate with closed-loop feedback, decision capture, and continuous learning \u2014 at SMB pricing with done-for-you implementation (NOT self-service).\n\nTarget Market\n\nICP: Service-based SMBs (2-50 employees, USA, $200K-$5M revenue)\n\nCore Pain: Capacity crisis, pipeline problems, operational chaos, growth blockers \u2014 too busy serving clients to grow their own business.\n\nPricing (Land-and-Expand)\n\n- Tier 1 \u2014 Foundation (1-2 workflows): $500-2k/mo\n- Tier 2 \u2014 Scaled Operations (3-5 workflows): $2k-5k/mo\n- Tier 3 \u2014 AI-Powered Systems (6+ workflows): $5k-15k+/mo\n\nAdditional workflows cost less due to shared infrastructure.\n\nValue Proposition\n\n"We find one bottleneck in your business, build an AI solution to fix it, and you only pay if it actually saves you time or makes you money."'
   }
 ];