arkaos 2.50.0 → 2.52.0

package/VERSION

@@ -1 +1 @@
-2.50.0
+2.52.0

package/departments/landing/skills/webinar-funnel/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: landing/webinar-funnel
 description: >
-  Webinar funnel: registration page, reminder sequence, live pitch, replay sequence.
+  Webinar funnel design — registration page, reminder sequence, live pitch
+  script structure, replay/cart sequence, conversion targets.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 
@@ -21,12 +22,164 @@ does not replace the vault.
 
 # Webinar Funnel — `/landing webinar <topic>`
 
-> **Agent:** Ines (Conversion Strategist) | **Framework:** Webinar Funnel + Russell Brunson
+> **Lead:** Ines (Conversion Strategist) | **Copy:** Teresa (Sales Copywriter) | **Framework:** Russell Brunson Perfect Webinar + False Belief Patterns
 
-## What It Does
+## What ships
 
-Webinar funnel: registration page, reminder sequence, live pitch, replay sequence.
+A production webinar funnel in 6 deliverables:
 
-## Output
+1. **Registration page** with hook + promise + agenda + host + social proof + CTA
+2. **Reminder email sequence** (5 emails, registration → live)
+3. **Live pitch script** with timing markers, false-belief teardown, offer stack
+4. **Replay + cart sequence** (5-7 emails post-webinar)
+5. **Conversion targets** with funnel math (registration → show-up → buy)
+6. **Tracking spec** with pixel events and attribution windows
 
-Webinar funnel map with all pages, emails, and conversion targets
+## The Perfect Webinar Frame (Brunson)
+
+A converting webinar follows a strict structure. Deviating from any element measurably drops conversion.
+
+```
+TIMING               BLOCK            PURPOSE
+─────────────────────────────────────────────────────────────────────
+0:00 - 0:05          Open             Hook, agenda, attendance proof
+0:05 - 0:15          Origin Story     Builder credibility, stakes
+0:15 - 0:45          Content (3 secrets) Teardown of 3 false beliefs
+0:45 - 0:55          Transition       "Here's what to do next"
+0:55 - 1:25          Offer Stack      Itemized value, anchored price
+1:25 - 1:35          Urgency + FAQ    Scarcity reason, top objections
+1:35 - 1:50          Close + Q&A      Repeated CTA, live Q&A
+```
+
+The 90-minute structure is the floor. Live webinars can run 120-180; auto-webinars compress to 60-75.
+
+## False Belief Patterns (the content middle)
+
+The middle of the webinar exists to teardown 3 false beliefs the audience holds — about the **vehicle** (what method), the **internal** (their own capability), and the **external** (their environment / circumstances). Each teardown follows the same shape:
+
+```
+1. State the false belief plainly ("Most people think X")
+2. Tell the origin of that belief (where it came from, why it's plausible)
+3. Tell the story of when YOU believed it (vulnerability anchor)
+4. Reveal the cost of that belief (specific consequence)
+5. Introduce the new belief (what actually works)
+6. Prove the new belief with evidence + story
+```
+
+Pick the 3 most load-bearing false beliefs your offer needs to dismantle. Pick more than 3 and the webinar bloats. Pick fewer and conversion drops.
+
+## Registration Page Anatomy
+
+Above the fold:
+- **Headline** — the hook (curiosity-led specific outcome)
+- **Sub-headline** — the timeframe + named mechanism
+- **Date / time / format** — specific, with timezone
+- **CTA button** — register, not "submit"
+
+Below the fold:
+- **Agenda** — 3-4 bullets teasing the 3 content blocks
+- **Host bio** — one paragraph + photo + 3 credibility markers
+- **Social proof** — 2-3 testimonials or registrant count
+- **Reminder consent** — "We'll send a reminder by email/SMS"
+- **FAQ block** — duration, replay availability, recording disclosure
+
+Conversion target: **30-45%** registration rate from warm traffic, **8-15%** from cold ads.
+
+## Reminder Sequence Template (5 emails)
+
+| # | When | Subject style | Purpose |
+|---|---|---|---|
+| 1 | Immediately | Confirmation + calendar link | Confirm registration, add to calendar |
+| 2 | 24h before | Value-prime story | Story-led pre-sell of the secrets to be revealed |
+| 3 | 1h before | "Starting soon" + login link | Drive show-up |
+| 4 | 10 min before | "We're live in 10" | Last show-up push |
+| 5 | At start | "We're live now" | Catch the last-minute attendees |
+
+Conversion target: **35-55%** show-up rate from registration. Auto-webinar shows higher (60-70%) because re-watching is built in.
+
+## Live Pitch Script Structure (core deliverable)
+
+The script template has fixed sections. Filling each section is the work; structure is not optional.
+
+```markdown
+# Webinar — [TOPIC]
+
+## 0:00 — Open (5 min)
+Hook line: [ONE SENTENCE WITH SPECIFIC NUMBER + TIMEFRAME]
+Agenda: [3 BULLETS — THE 3 SECRETS]
+Attendance proof: [WHO'S HERE / WHERE FROM]
+
+## 0:05 — Origin Story (10 min)
+- The moment everything changed
+- What was at stake (concrete)
+- The cost of NOT solving it
+- The breakthrough insight
+
+## 0:15 — Secret #1 [VEHICLE FALSE BELIEF] (10 min)
+- False belief: [plain sentence]
+- Origin of the belief: [story]
+- When YOU believed it: [vulnerability anchor]
+- Cost of the belief: [specific consequence]
+- New belief: [plain sentence]
+- Proof: [story + evidence]
+
+## 0:25 — Secret #2 [INTERNAL FALSE BELIEF] (10 min)
+(same structure)
+
+## 0:35 — Secret #3 [EXTERNAL FALSE BELIEF] (10 min)
+(same structure)
+
+## 0:45 — Transition (10 min)
+"You're now wondering: how do I actually DO this?"
+- Three options: (1) figure it out alone (slow), (2) hire someone (expensive), (3) follow a proven system (the offer)
+- Introduce the offer name
+
+## 0:55 — Offer Stack (30 min)
+- Component 1: [name + dream outcome + value $X]
+- Component 2: [name + dream outcome + value $X]
+- Component 3: [name + dream outcome + value $X]
+- Bonus 1: [name + scarcity reason]
+- Bonus 2: [name + scarcity reason]
+- Total value: $X
+- Today's price: $Y (anchored vs total)
+
+## 1:25 — Urgency + FAQ (10 min)
+Urgency reason: [scarcity / deadline / cohort cap / price increase]
+Top objections answered: [3-5 with prepared scripts]
+
+## 1:35 — Close + Live Q&A (15 min)
+Repeat CTA + URL
+Live Q&A with prepared questions
+Final close at 1:50
+```
+
+## Replay + Cart Sequence (post-webinar)
+
+| # | When | Subject style | Purpose |
+|---|---|---|---|
+| 1 | 1h after | "Did you miss it?" + replay | Catch no-shows |
+| 2 | 24h | "Quick recap" + replay + CTA | Re-engage, soft pitch |
+| 3 | 48h | Case study | Social proof, momentum |
+| 4 | 72h | FAQ + objection-handling | De-risk |
+| 5 | Cart-close - 24h | "Closing tomorrow" + scarcity | Urgency |
+| 6 | Cart-close - 6h | "Closing in 6h" | Final push |
+| 7 | Cart-close - 1h | "Closing in 1h" | Last-call |
+
+Conversion target: **3-8%** of registrants buy (cold list), **8-20%** (warm list). Replay attribution is 30-50% of total revenue — don't skip it.
+
+## Tracking Spec
+
+Pixel events required:
+- `Registration` — fires on registration form submit
+- `WebinarOpen` — fires on live broadcast page load (50%+ attendance signal)
+- `WebinarComplete` — fires at 75% watched
+- `PitchOpen` — fires when offer URL loads from webinar
+- `Purchase` — fires on order confirmation
+- `ReplayOpen` — fires on replay page load
+- `ReplayPurchase` — fires on order from replay-attributed link
+
+Attribution window: 14 days, last-click weighted toward the live broadcast event.
+
+## Output → Obsidian: `WizardingCode/Webinars/<topic>-<date>/`
+
+Delivers: hook variants + registration page + 5-email reminder sequence + full pitch script + 5-7 email replay/cart sequence + conversion targets + tracking spec.

package/departments/landing/workflows/funnel.yaml

@@ -0,0 +1,135 @@
+id: landing-funnel
+name: Funnel Architecture
+description: Sales funnel architecture matched to audience awareness and price point — squeeze, tripwire, SLO, webinar, VSL, application
+department: landing
+tier: enterprise
+command: "/landing funnel"
+requires_branch: false
+requires_spec: false
+quality_gate_required: true
+
+phases:
+  - id: brief
+    name: Funnel Brief
+    description: Define product, price point, audience awareness level, conversion target
+    agents:
+      - agent_id: conversion-strategist-ines
+        role: Frame product, current traffic source, price point, current conversion baseline
+    gate:
+      type: user_approval
+      description: User confirms product, price point, awareness level, conversion target
+
+  - id: awareness-diagnosis
+    name: Awareness Diagnosis
+    description: Diagnose audience awareness level (Schwartz 5 stages) — drives funnel type selection
+    agents:
+      - agent_id: conversion-strategist-ines
+        role: Apply Schwartz Awareness Ladder, score audience position
+    gate:
+      type: user_approval
+      description: User approves awareness diagnosis before funnel-type selection
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/Funnels/Awareness/"
+        description: Awareness diagnosis with evidence per stage
+
+  - id: funnel-selection
+    name: Funnel Type Selection
+    description: Pick funnel type from Value Ladder matching awareness × price (squeeze / tripwire / SLO / webinar / VSL / application)
+    agents:
+      - agent_id: conversion-strategist-ines
+        role: Apply Value Ladder + awareness-price-funnel matrix; select primary funnel
+      - agent_id: saas-strategist-tiago
+        role: Pricing strategy fit check
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves funnel-type selection with rationale
+
+  - id: offer-design
+    name: Offer Design
+    description: Grand Slam Offer construction (Hormozi value equation) for the funnel
+    agents:
+      - agent_id: conversion-strategist-ines
+        role: Build offer with dream outcome × perceived likelihood / (time delay × effort)
+    gate:
+      type: user_approval
+      description: User approves offer structure before page architecture
+
+  - id: page-architecture
+    name: Page Architecture
+    description: Map every page in the funnel — squeeze / sales / order / thank-you / upsell / downsell, plus copy framework per page
+    agents:
+      - agent_id: conversion-strategist-ines
+        role: Define page list with role, copy framework, conversion target per page
+      - agent_id: sales-copywriter-teresa
+        role: Headline + sub-headline + lead drafts per page
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves the page list and primary CTA per page
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/Funnels/Architecture/"
+        description: Page list with copy framework and conversion target per page
+
+  - id: email-sequences
+    name: Email Sequences
+    description: Email sequences supporting the funnel — indoctrination, cart, nurture, abandonment, post-purchase
+    agents:
+      - agent_id: sales-copywriter-teresa
+        role: Email sequence design per supporting role
+    gate:
+      type: auto
+
+  - id: metrics-targets
+    name: Metrics & Targets
+    description: Set conversion targets per page + funnel-level metrics (CAC, AOV, LTV, ROAS)
+    agents:
+      - agent_id: conversion-strategist-ines
+        role: Compute conversion baseline + targets, funnel economics
+    gate:
+      type: user_approval
+      description: User approves the funnel metrics targets
+
+  - id: self-critique
+    name: Self-Critique
+    description: Stress-test the funnel — does awareness match offer match price match traffic source?
+    agents:
+      - agent_id: conversion-strategist-ines
+        role: Coherence check across all funnel elements
+    gate:
+      type: auto
+
+  - id: quality-gate
+    name: Quality Gate
+    model_override: opus
+    description: Mandatory quality review
+    agents:
+      - agent_id: cqo-marta
+        role: Orchestrate quality review
+      - agent_id: copy-director-eduardo
+        role: Sales copy quality, awareness-match prose, no clichés
+        parallel: true
+      - agent_id: tech-director-francisca
+        role: Page count + metrics target feasibility + tracking integrity
+        parallel: true
+    gate:
+      type: quality_gate
+      required_verdict: APPROVED
+
+  - id: delivery
+    name: Funnel Package Delivery
+    description: Compile the funnel package — pages + copy + emails + metrics targets
+    agents:
+      - agent_id: conversion-strategist-ines
+        role: Full funnel package compilation
+    gate:
+      type: auto
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/Funnels/"
+        description: Complete funnel package — awareness diagnosis + offer + page architecture + email sequences + metrics targets

package/departments/landing/workflows/webinar.yaml

@@ -0,0 +1,134 @@
+id: landing-webinar
+name: Webinar Funnel
+description: Webinar funnel — registration page, reminder sequence, live pitch script, replay sequence, indoctrination + cart sequences
+department: landing
+tier: enterprise
+command: "/landing webinar"
+requires_branch: false
+requires_spec: false
+quality_gate_required: true
+
+phases:
+  - id: brief
+    name: Webinar Brief
+    description: Define topic, target avatar, live vs evergreen, sale price, dates
+    agents:
+      - agent_id: conversion-strategist-ines
+        role: Frame topic, audience, format (live / auto / hybrid), sale price, broadcast dates
+    gate:
+      type: user_approval
+      description: User confirms topic, format, sale price, and dates
+
+  - id: hook-design
+    name: Hook & Promise
+    description: Design the webinar hook (one-time deal, secret framework, mistake list) and the core promise
+    agents:
+      - agent_id: conversion-strategist-ines
+        role: Hook variants (3-5), core promise statement, false-belief frames (3)
+    gate:
+      type: user_approval
+      description: User approves hook and core promise
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/Webinars/Hooks/"
+        description: Hook variants + core promise + false-belief frames
+
+  - id: registration-page
+    name: Registration Page
+    description: Registration page design — hook, promise, agenda, host bio, social proof, CTA
+    agents:
+      - agent_id: conversion-strategist-ines
+        role: Page wireframe with conversion target
+      - agent_id: sales-copywriter-teresa
+        role: Headline + sub-headline + agenda copy + host bio + CTA copy
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves the registration page before email sequence build
+
+  - id: reminder-sequence
+    name: Reminder Sequence
+    description: Email sequence before the webinar — confirmation, value-prime, day-before, hour-before, last-call
+    agents:
+      - agent_id: sales-copywriter-teresa
+        role: 5-email reminder sequence with show-up rate target
+    gate:
+      type: auto
+
+  - id: live-script
+    name: Live Pitch Script
+    description: Webinar script — open, content (3-5 modules), pitch transition, offer, FAQ, close
+    agents:
+      - agent_id: conversion-strategist-ines
+        role: Script structure with timing, false-belief teardown, offer stack, urgency, FAQ
+      - agent_id: sales-copywriter-teresa
+        role: Script copy with stories, transitions, CTAs
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves script structure before replay sequence
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/Webinars/Scripts/"
+        description: Live pitch script with timing markers
+
+  - id: replay-sequence
+    name: Replay & Cart Sequence
+    description: Post-webinar email sequence — replay availability, encore, cart-open, cart-close, last-chance
+    agents:
+      - agent_id: sales-copywriter-teresa
+        role: 5-7 email post-webinar sequence with cart-close target
+    gate:
+      type: auto
+
+  - id: metrics-targets
+    name: Conversion Targets
+    description: Set registration → show-up → buy targets, plus replay attribution
+    agents:
+      - agent_id: conversion-strategist-ines
+        role: Funnel math — registration rate, show-up rate, buy rate, CAC, LTV
+    gate:
+      type: user_approval
+      description: User approves the conversion targets
+
+  - id: self-critique
+    name: Self-Critique
+    description: Stress-test the webinar — does hook match promise match script match offer?
+    agents:
+      - agent_id: conversion-strategist-ines
+        role: Coherence check across all webinar elements
+    gate:
+      type: auto
+
+  - id: quality-gate
+    name: Quality Gate
+    model_override: opus
+    description: Mandatory quality review
+    agents:
+      - agent_id: cqo-marta
+        role: Orchestrate quality review
+      - agent_id: copy-director-eduardo
+        role: Script + email copy quality, no clichés, no over-promise
+        parallel: true
+      - agent_id: tech-director-francisca
+        role: Funnel mechanics integrity, tracking, evergreen-vs-live config correctness
+        parallel: true
+    gate:
+      type: quality_gate
+      required_verdict: APPROVED
+
+  - id: delivery
+    name: Webinar Package Delivery
+    description: Compile the full webinar package
+    agents:
+      - agent_id: conversion-strategist-ines
+        role: Full webinar package compilation
+    gate:
+      type: auto
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/Webinars/"
+        description: Complete webinar package — hook + registration page + reminder sequence + script + replay sequence + conversion targets

package/departments/saas/skills/gtm-strategy/SKILL.md

@@ -1,7 +1,9 @@
 ---
 name: saas/gtm-strategy
 description: >
-  Go-to-market strategy for SaaS: motion selection, ICP, channel mix, launch plan.
+  Cross-departmental go-to-market strategy: ICP, positioning, motion selection,
+  channel mix, 90-day execution plan. Orchestrates SaaS + Strategy + Marketing
+  + Sales + Landing.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 
@@ -19,14 +21,138 @@ treat them as your default source. External research supplements, it
 does not replace the vault.
 <!-- arka:kb-first-prefix end -->
 
-# Gtm Strategy — `/saas gtm <product>`
+# GTM Strategy — `/saas gtm <product>`
 
-> **Agent:** Tiago (SaaS Strategist) | **Framework:** MOVE Framework (Sangram Vajre) + 6 GTM Motions
+> **Lead:** Tiago (SaaS Strategist) | **Cross-dept:** Tomas (Strategy) + Mateus (Brand) + Luna (Marketing) + Miguel (Sales) + Ines (Landing) | **Framework:** MOVE (Sangram Vajre) + Onlyness + AARRR
 
-## What It Does
+## What ships
 
-Go-to-market strategy for SaaS: motion selection, ICP, channel mix, launch plan.
+A production GTM package in 6 deliverables, each with a named owner and a measurable target:
 
-## Output
+1. **ICP profile** — firmographics + persona + pain triggers + buying signal
+2. **Positioning statement** — Onlyness frame + competitive contrast table
+3. **Motion selection** — primary + assist motion with feasibility math
+4. **Channel mix** — budget allocation across channels with AARRR baseline
+5. **90-day execution plan** — week-by-week with owners + checkpoints
+6. **Executive summary** — 1-page printable to align stakeholders
 
-GTM strategy doc with motion, ICP, channels, and 90-day execution plan
+## ICP Template (firmographic + persona + pain + signal)
+
+Every ICP profile must carry these four blocks. Vagueness in any block invalidates the rest of the GTM stack.
+
+### Firmographics (the company shape)
+- Company size (employees, ARR range)
+- Industry vertical (with NAICS / SIC code if relevant)
+- Geo (countries, regulatory regions)
+- Tech stack signal (what they already pay for that signals readiness)
+- Funding stage (bootstrapped / seed / Series A+ / public)
+
+### Persona (the human inside the company)
+- Title and seniority
+- Primary KPI they own
+- Tools they use daily
+- Information diet (newsletters, podcasts, communities)
+- Decision authority (sole / committee / approval)
+
+### Pain Triggers (the moment they realise they need this)
+- The specific event that surfaces the pain (new hire, missed quarter, audit, regulation change)
+- The cost of not solving it (revenue at risk, hours wasted, compliance exposure)
+- The status quo workaround (Excel, agencies, internal builds)
+
+### Buying Signal (how you find them in the wild)
+- Observable behavior in the open web (job postings with specific keywords, tool reviews, talks at specific conferences)
+- Account-level data signal (vendor footprint, hiring pattern, public infrastructure)
+- Conversational signal (specific Slack/Discord communities, specific subreddits)
+
+## Onlyness Statement (positioning frame)
+
+The Onlyness frame forces a single defensible sentence:
+
+> **We are the only [category] that [unique mechanism] for [ICP] who want [outcome].**
+
+Worked example:
+> "We are the only AI agent orchestration system that ships behavioral compliance telemetry baked into the runtime for technical founders who want measurable governance instead of vibes-based discipline."
+
+The statement must pass three tests:
+1. **Substitution test** — replace your name with a competitor's. Does the sentence still hold? If yes, the positioning isn't defensible.
+2. **Customer-articulation test** — would a current customer say this sentence back unprompted in roughly these words?
+3. **Mechanism test** — is "unique mechanism" a verifiable specific (a feature, a method, a metric) or marketing prose (an adjective, a vibe)?
+
+## 6 GTM Motions (pick primary + assist)
+
+Each motion has a default ICP shape and a default channel mix. Mixing motions without understanding the constraints below produces zero-momentum GTM.
+
+| Motion | Default ICP | Default Channels | Velocity | Typical CAC payback |
+|---|---|---|---|---|
+| **Product-Led (PLG)** | High-volume, low-ticket, self-serve adoption pattern | SEO + integrations + viral loops + product itself | Fast (weeks to first value) | 6-12 months |
+| **Sales-Led (SLG)** | Enterprise, committee buying, regulated industries | Outbound + content + events + partner channel | Slow (months to close) | 12-18 months |
+| **Community-Led** | High-affinity practitioners, identity-driven adoption | Owned community + open source + advocate program | Medium (compounds quarterly) | Variable (community creates own loop) |
+| **Partner-Led** | Vertical specialists, complex installs, system integrator channel | Channel partnerships + reseller program + co-marketing | Slow start, faster scale | 9-18 months |
+| **Inbound** | Information-seeking buyers researching solutions | SEO + content marketing + comparison content + reviews | Medium (3-6 month ramp) | 6-12 months |
+| **Outbound** | Identified buyer set, account-based targeting | Cold email + cold call + LinkedIn + ABM | Fast pipeline, slow trust | 12-24 months |
+
+The MOVE framework (Sangram Vajre): **M**arkets (who you're selling into), **O**perations (your repeatable engine), **V**elocity (deal cycle + expansion math), **E**xpansion (NRR > 110% target).
+
+## Channel-Motion Matrix
+
+```
+                  Content/SEO   Paid   Community   Partner   Event   Outbound
+Product-Led          ✓✓✓         ✓✓     ✓✓✓          ✓        ✓       —
+Sales-Led            ✓✓          ✓✓     ✓            ✓✓✓      ✓✓✓     ✓✓✓
+Community-Led        ✓✓✓         —      ✓✓✓✓         ✓✓       ✓✓      —
+Partner-Led          ✓           ✓      ✓            ✓✓✓✓     ✓✓✓     ✓✓
+Inbound              ✓✓✓✓        ✓✓✓    ✓✓           ✓        ✓✓      —
+Outbound             ✓✓          ✓      ✓            ✓✓       ✓✓      ✓✓✓✓
+```
+
+Pick exactly ONE primary channel that gets 50%+ of budget. Add at most TWO assist channels. More channels = no channel.
+
+## 90-Day Execution Plan Template
+
+Plan structure (every plan must follow this shape):
+
+```
+Week 1-2: Foundation
+  - [Owner] ICP doc validated with 5 customer conversations
+  - [Owner] Positioning statement live on homepage
+  - [Owner] Tracking baseline measured (current AARRR rates)
+
+Week 3-4: Channel Activation (primary)
+  - [Owner] First 4 [channel-native content units] published
+  - [Owner] Conversion tracking live, first signals captured
+  - [Owner] Sales playbook v1 written for inbound responses
+
+Week 5-8: Iteration
+  - [Owner] Top-funnel CAC measured, channel ROI computed
+  - [Owner] Pricing test A/B started
+  - [Owner] First 10 customer interviews completed and tagged
+  - [Owner] Assist channels activated based on primary signal
+
+Week 9-12: Scale Decision
+  - [Owner] Channel-mix review — double down or pivot
+  - [Owner] First retention cohort analysis (D7, D30)
+  - [Owner] Next-90-day plan written based on real data
+```
+
+Every line must have: owner name, measurable output, due date.
+
+## Executive Summary (1-page, mandatory output)
+
+The full GTM package is dense. The 1-page exec summary captures:
+
+```
+Product:             [name]
+ICP:                 [one sentence: who, where, what pain]
+Positioning:         [Onlyness sentence]
+Primary Motion:      [name + why this one]
+Primary Channel:     [name + 90-day budget]
+North Star Metric:   [the one number that, if it moves, the strategy works]
+Day-90 Target:       [specific number tied to North Star Metric]
+Top Risk:            [what would invalidate this strategy + mitigation]
+```
+
+If the executive summary doesn't fit on one printable page, the strategy is overcomplicated.
+
+## Output → Obsidian: `WizardingCode/GTM/<product>-<date>/`
+
+Delivers: ICP profile + positioning statement + motion selection + channel mix + 90-day plan + executive summary. Plus the cross-departmental review trail (Strategy + Brand + Marketing + Sales + Landing signatures from each phase gate).

package/departments/saas/workflows/gtm-strategy.yaml

@@ -0,0 +1,144 @@
+id: saas-gtm-strategy
+name: GTM Strategy (Cross-Departmental)
+description: Full go-to-market strategy from ICP to 90-day execution plan, orchestrating SaaS + Strategy + Marketing + Sales + Landing
+department: saas
+tier: enterprise
+command: "/saas gtm"
+requires_branch: false
+requires_spec: false
+quality_gate_required: true
+
+phases:
+  - id: brief
+    name: GTM Brief
+    description: Define product, current stage, available budget/runway, and success metric
+    agents:
+      - agent_id: saas-strategist-tiago
+        role: Frame product context, current ARR/MRR, runway, win condition for the launch
+    gate:
+      type: user_approval
+      description: User confirms product context, budget, and success metric
+
+  - id: icp-discovery
+    name: ICP Discovery
+    description: Define Ideal Customer Profile from existing user data and competitor analysis
+    agents:
+      - agent_id: strategy-director-tomas
+        role: ICP framework — firmographics, technographics, pain triggers, buying committee
+        parallel: true
+      - agent_id: saas-strategist-tiago
+        role: Current-user pattern extraction, look-alike modeling, willingness-to-pay signals
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves the ICP (firmographics + persona + pain triggers + buying signal)
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/GTM/ICP/"
+        description: ICP profile with persona card, pain triggers, buying signals
+
+  - id: positioning
+    name: Positioning Statement
+    description: Position the product in the ICP's mental category using Ries/Trout template + Onlyness frame
+    agents:
+      - agent_id: brand-strategist-mateus
+        role: Onlyness statement (only X that Y for Z), category creation vs category capture analysis
+      - agent_id: strategy-director-tomas
+        role: Competitive contrast — 3-5 direct competitors with relative positioning
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves positioning (one-sentence + competitive contrast)
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/GTM/Positioning/"
+        description: Positioning statement + competitive contrast table
+
+  - id: motion-selection
+    name: GTM Motion Selection
+    description: Pick the primary motion (PLG / SLG / community / partner / inbound / outbound) and the assist motion
+    agents:
+      - agent_id: saas-strategist-tiago
+        role: Apply Sangram Vajre's MOVE framework — Markets, Operations, Velocity, Expansion
+      - agent_id: sales-director-miguel
+        role: Sales motion feasibility — pipeline math, CAC payback, win-rate baseline
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves primary motion + assist motion + 90-day target velocity
+
+  - id: channel-mix
+    name: Channel Mix
+    description: Map motion to channels — content / paid / community / partnerships / events / outbound — with budget allocation
+    agents:
+      - agent_id: marketing-director-luna
+        role: Channel mix design with AARRR baseline, growth loop selection
+      - agent_id: conversion-strategist-ines
+        role: Landing surface design per channel (one URL per channel intent)
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves channel allocation and budget split
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/GTM/Channels/"
+        description: Channel mix with budget allocation and AARRR baseline
+
+  - id: ninety-day-plan
+    name: 90-Day Execution Plan
+    description: Concrete week-by-week deliverables, owners, success metrics — first 90 days
+    agents:
+      - agent_id: saas-strategist-tiago
+        role: Week-by-week deliverable plan with named owners and weekly checkpoints
+      - agent_id: marketing-director-luna
+        role: Marketing-side deliverables (content cadence, paid ramp, community)
+        parallel: true
+      - agent_id: sales-director-miguel
+        role: Sales-side deliverables (outbound cadence, demo book rate target)
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves the 90-day plan before Quality Gate
+
+  - id: self-critique
+    name: Self-Critique
+    description: Stress-test the plan — is the motion-channel-budget triple internally consistent? Are weekly checkpoints measurable?
+    agents:
+      - agent_id: strategy-director-tomas
+        role: Strategic coherence check — motion ↔ ICP ↔ positioning ↔ channels alignment
+    gate:
+      type: auto
+
+  - id: quality-gate
+    name: Quality Gate
+    model_override: opus
+    description: Mandatory quality review
+    agents:
+      - agent_id: cqo-marta
+        role: Orchestrate quality review
+      - agent_id: copy-director-eduardo
+        role: ICP language, positioning prose, plan readability — no clichés
+        parallel: true
+      - agent_id: tech-director-francisca
+        role: Plan executability — every action has an owner, a date, a metric
+        parallel: true
+    gate:
+      type: quality_gate
+      required_verdict: APPROVED
+
+  - id: delivery
+    name: GTM Package Delivery
+    description: Compile the full GTM package and produce the 1-page executive summary
+    agents:
+      - agent_id: saas-strategist-tiago
+        role: Full GTM package compilation + 1-page executive summary
+    gate:
+      type: auto
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/GTM/"
+        description: Complete GTM package — ICP + positioning + motion + channel mix + 90-day plan + executive summary

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "arkaos",
-  "version": "2.50.0",
+  "version": "2.52.0",
   "description": "The Operating System for AI Agent Teams",
   "type": "module",
   "bin": {

package/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "arkaos-core"
-version = "2.50.0"
+version = "2.52.0"
 description = "Core engine for ArkaOS — The Operating System for AI Agent Teams"
 readme = "README.md"
 license = {text = "MIT"}