arkaos 2.53.0 → 2.55.0

package/VERSION

@@ -1 +1 @@
-2.53.0
+2.55.0

package/departments/content/skills/youtube-strategy/SKILL.md

@@ -1,7 +1,9 @@
 ---
 name: content/youtube-strategy
 description: >
-  YouTube strategy: title/thumbnail packaging, script structure, SEO, upload cadence.
+  YouTube strategy — channel positioning, title × thumbnail architecture,
+  hook + script structure, SEO + metadata, publishing cadence, cross-platform
+  distribution.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 
@@ -19,14 +21,141 @@ treat them as your default source. External research supplements, it
 does not replace the vault.
 <!-- arka:kb-first-prefix end -->
 
-# Youtube Strategy — `/content youtube <topic>`
+# YouTube Strategy — `/content youtube <topic>`
 
-> **Agent:** Rafael (Content Strategist) | **Framework:** MrBeast Method + YouTube Algorithm
+> **Lead:** Rafael (Content Strategist) | **Cross-dept:** Isabel (Visual Designer) + Teresa (Copy) + Luna (Marketing) | **Frameworks:** MrBeast Title × Thumbnail Method + Algorithm-Aware Retention Design
 
-## What It Does
+## What ships
 
-YouTube strategy: title/thumbnail packaging, script structure, SEO, upload cadence.
+A production YouTube strategy in 7 deliverables:
 
-## Output
+1. **Channel positioning** with competing-channel analysis
+2. **10 title × thumbnail pairs** with CTR patterns named
+3. **Hook architecture** + retention curve plan per video
+4. **Script structure** with retention drops mapped
+5. **SEO metadata + playlist hierarchy**
+6. **Publishing cadence** with view + subscriber targets
+7. **Cross-platform derivative spec** (Shorts, threads, newsletter)
 
-YouTube strategy with 10 video ideas, title/thumb variants, and growth targets
+## The CTR-Retention Math (why packaging matters)
+
+The YouTube algorithm rewards two metrics in tight loop:
+
+- **CTR (click-through rate)** — % of impressions that click. Median is 4-6%; top performers 10-15%.
+- **AVD (average view duration)** — minutes watched per view. Algorithm normalizes by video length but rewards higher absolute AVD.
+
+CTR depends on **title × thumbnail × topic** working together. AVD depends on **hook + retention curve + payoff**. If CTR is high but AVD is low, the algorithm interprets the video as clickbait and demotes it. If CTR is low but AVD is high, the video starves of impressions.
+
+Target floor: CTR ≥ 6%, AVD ≥ 40% of length, retention curve no sharp drops in first 30 seconds.
+
+## Title × Thumbnail Patterns (CTR levers)
+
+Each title × thumbnail pair uses one of these named patterns. Mixing patterns randomly produces noise; picking a primary pattern per channel produces compounding.
+
+| Pattern | Title shape | Thumbnail shape | Use case |
+|---|---|---|---|
+| **Curiosity Gap** | "What happens when [unexpected]" | One element + question mark + face surprised | Investigation, experiment videos |
+| **Transformation** | "From X to Y in Z time" | Before / After split | Tutorial, journey, case study |
+| **Specific Claim** | "I [verb] [specific number] [specific subject]" | Numbers visible + product / outcome | Stunt, achievement, deep-dive |
+| **Loss Aversion** | "Don't [common mistake]" | Red X + warning icon + face concerned | Warning, education |
+| **Authority + Specific** | "How [expert title] [does specific thing]" | Person + tool / artifact + clean type | Expert content, behind-the-scenes |
+| **Comparison** | "X vs Y: Which actually [outcome]" | Split with both items + clear winner cue | Review, head-to-head |
+| **Contrarian** | "Why everyone is wrong about X" | Strikethrough on common belief + face defiant | Opinion, takedown, education |
+
+Thumbnail design rules (visual hierarchy):
+- **One focal point** — eye lands on a single element first
+- **Face if relevant** — human face drives 30-40% CTR lift on most topics
+- **Contrast** — high-saturation focal vs muted background
+- **Type ≤ 4 words** — readable on mobile at 320px width
+- **No clickbait that breaks promise** — title and thumbnail must accurately preview the payoff
+
+## Hook Architecture (first 30 seconds)
+
+The first 30 seconds determines whether the viewer stays. The hook structure that consistently retains:
+
+```
+0-3s   PATTERN INTERRUPT — visual + audio shock or unexpected statement
+3-10s  PROMISE — name the transformation / outcome the viewer gets
+10-20s STAKES — why this matters, what they'll lose by leaving
+20-30s PREVIEW — quick montage of the 3 best moments coming up
+```
+
+Pattern interrupts that work: starting mid-action, a contradictory statement, an unexpected location, an unexpected visual element. Pattern interrupts that don't work: long intro animations, founder face talking to camera with no visual.
+
+## Script Structure (full video)
+
+Default structure for a 10-12 minute video (the optimal range for monetisation + retention):
+
+```
+0:00 - 0:30   Hook (see Hook Architecture)
+0:30 - 2:00   Setup — name the problem, stakes, why now
+2:00 - 4:00   Reframe — show the prevailing wrong answer + your alternative frame
+4:00 - 8:00   Content blocks (2-3 blocks) — each with a mini-hook, a payoff, a transition
+8:00 - 10:00  Payoff — the promised transformation / answer delivered concretely
+10:00 - 11:00 Recap + CTA — quick recap + subscribe / next video / link in description
+11:00 - 12:00 Outro + end screen — pattern-interrupt sting + related video CTA
+```
+
+Retention drops happen at predictable moments: 1:00 (initial commitment), 4:00 (mid-video boredom), 8:00 (sense of completion). Insert a mini-hook 10 seconds before each predicted drop to retain viewers through it.
+
+## SEO Metadata Stack
+
+For each video, fill the metadata stack:
+
+```yaml
+title:
+  primary_keyword: "<2-3 word keyword>"
+  full_title: "<title with keyword + pattern + emotional anchor>"
+  variants_for_testing: 3-5 alternates
+
+description:
+  first_140_chars: "<keyword-loaded summary that appears in search>"
+  full_description:
+    - paragraph 1: hook + value prop (250 chars)
+    - paragraph 2: timestamps with keyword variants
+    - paragraph 3: links + CTAs
+    - paragraph 4: hashtags (3-5 max, mixed broad + niche)
+  pinned_comment: "<first comment author posts with related links>"
+
+tags:
+  primary: ["<broad topic>", "<specific topic>"]
+  long_tail: ["<specific phrase>", "<question phrase>"]
+  branded: ["<channel name>", "<series name>"]
+
+end_screen:
+  best_for_viewer: <related video by same channel>
+  subscribe_cta: <button position>
+
+playlists:
+  series_playlist: <series name if applicable>
+  topic_playlist: <topic cluster>
+```
+
+## Publishing Cadence Math
+
+Sustainability beats burst. The cadence math:
+
+- **Long-form video** anchor — 1 per week typical floor for growth channels, 1 per 2 weeks for high-production
+- **Shorts derivatives** — 3-5 per long-form video, posted on rolling schedule
+- **Community posts** — 2-3 per week to keep algorithm engagement signal
+- **Live / Premiere** — optional monthly cadence for community deepening
+
+First 90 days targets:
+- Week 1-4: 4 long-forms, 16-20 shorts. Target: identify which pattern resonates.
+- Week 5-8: Double down on winning pattern. Target: first video to 10k views.
+- Week 9-12: Optimise + scale. Target: first 1000 subs OR 100k cumulative views, whichever ships first.
+
+## Cross-Platform Derivatives (per long-form video)
+
+Each long-form video should produce:
+- **3-5 YouTube Shorts** (vertical, 30-60s, hook-led clips)
+- **1 Twitter/X thread** (10-15 tweets summarising the video with embedded clips)
+- **1 LinkedIn post** (professional framing for B2B audiences)
+- **1 newsletter section** (long-form summary with personal context)
+- **1 Podcast adaptation** (audio extraction if relevant)
+
+Derivative production should be templated — derivatives are not new content, they are repackaging.
+
+## Output → Obsidian: `WizardingCode/Content/YouTube/<topic>-<date>/`
+
+Delivers: channel positioning + 10 title × thumbnail pairs + hook architecture + script structure for 3-5 videos + SEO metadata stack per video + 90-day cadence + cross-platform derivative spec + 1-page executive summary.

package/departments/content/workflows/system.yaml

@@ -0,0 +1,136 @@
+id: content-system
+name: Content Operating System
+description: Build a complete Content OS — strategy + production system + distribution + repurposing + analytics — that compounds output over time
+department: content
+tier: enterprise
+command: "/content system"
+requires_branch: false
+requires_spec: false
+quality_gate_required: true
+
+phases:
+  - id: brief
+    name: Content OS Brief
+    description: Define audience, content goals, current capacity, platforms, runway, success metric
+    agents:
+      - agent_id: content-director-rafael
+        role: Frame audience, goals, current production cadence, target platforms, success metric
+    gate:
+      type: user_approval
+      description: User confirms audience, goals, platforms, success metric
+
+  - id: pillar-design
+    name: Content Pillar Design
+    description: Define 3-5 content pillars that align audience interest × business value × differentiation
+    agents:
+      - agent_id: content-director-rafael
+        role: 3-5 pillar topics with audience-interest score + business-value score per pillar
+      - agent_id: marketing-director-luna
+        role: Search demand + competitive density per pillar
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves the pillar set
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/Content/OS/Pillars/"
+        description: Content pillar definition with audience/business/differentiation scoring
+
+  - id: format-stack
+    name: Format Stack
+    description: Define the format stack per pillar (long-form anchor + short-form derivatives + repurposing chain)
+    agents:
+      - agent_id: content-director-rafael
+        role: Format stack design (anchor format + 4-6 derivative formats per anchor)
+      - agent_id: short-form-specialist
+        role: Short-form derivative specifications (Reels / Shorts / Tweets / Carousels)
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves the format stack
+
+  - id: production-cadence
+    name: Production Cadence
+    description: Set realistic cadence — anchor pieces per month, derivatives per anchor, total weekly output
+    agents:
+      - agent_id: content-director-rafael
+        role: Cadence math — anchor cycle time, derivative multiplier, weekly total, sustainability check
+    gate:
+      type: user_approval
+      description: User approves the cadence
+
+  - id: distribution-channels
+    name: Distribution Channels
+    description: Map content type × platform — where each anchor and each derivative lives, with platform-native adaptations
+    agents:
+      - agent_id: content-director-rafael
+        role: Channel map with platform-native adaptations per format
+      - agent_id: marketing-director-luna
+        role: Distribution amplification — paid, partnerships, syndication options
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves distribution map
+
+  - id: analytics-stack
+    name: Analytics Stack
+    description: Define the metrics that matter — per-pillar performance, per-format performance, per-channel performance, North Star metric
+    agents:
+      - agent_id: content-director-rafael
+        role: Analytics dashboard spec with per-level metrics (pillar / format / channel)
+      - agent_id: tech-director-francisca
+        role: Tracking implementation feasibility
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves analytics stack
+
+  - id: ops-systems
+    name: Ops & Systems
+    description: Templates, briefs, asset library, review workflow, publishing workflow, archive
+    agents:
+      - agent_id: content-director-rafael
+        role: Operational templates and workflow specs (brief, review, publish, archive)
+    gate:
+      type: auto
+
+  - id: self-critique
+    name: Self-Critique
+    description: Stress-test the system — is cadence sustainable? Are pillars differentiated? Does analytics tie to North Star?
+    agents:
+      - agent_id: content-director-rafael
+        role: Coherence check across pillars / format stack / cadence / analytics / North Star
+    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: Pillar prose, format brief quality, no clichés
+        parallel: true
+      - agent_id: tech-director-francisca
+        role: Cadence feasibility, tracking integrity, workflow operability
+        parallel: true
+    gate:
+      type: quality_gate
+      required_verdict: APPROVED
+
+  - id: delivery
+    name: Content OS Package Delivery
+    description: Compile the full Content OS — pillars + format stack + cadence + distribution + analytics + ops templates
+    agents:
+      - agent_id: content-director-rafael
+        role: Full Content OS package + 1-page executive summary
+    gate:
+      type: auto
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/Content/OS/"
+        description: Complete Content OS — pillars + format stack + cadence + distribution + analytics + ops templates + exec summary

package/departments/content/workflows/youtube.yaml

@@ -0,0 +1,144 @@
+id: content-youtube
+name: YouTube Strategy
+description: Full YouTube strategy — channel positioning, title × thumbnail × hook architecture, script structure, SEO optimization, distribution
+department: content
+tier: enterprise
+command: "/content youtube"
+requires_branch: false
+requires_spec: false
+quality_gate_required: true
+
+phases:
+  - id: brief
+    name: YouTube Brief
+    description: Define topic, target audience, current channel state, monetisation goal, weekly capacity
+    agents:
+      - agent_id: content-director-rafael
+        role: Frame topic, audience, current subscribers + AVG view duration, monetisation goal
+    gate:
+      type: user_approval
+      description: User confirms YouTube brief
+
+  - id: channel-positioning
+    name: Channel Positioning
+    description: Position the channel in the YouTube taxonomy — niche, target persona, channel promise, competing channels
+    agents:
+      - agent_id: content-director-rafael
+        role: Channel positioning statement + competing channels analysis
+      - agent_id: brand-strategist-mateus
+        role: Differentiation angle, channel identity
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves channel positioning
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/Content/YouTube/Positioning/"
+        description: Channel positioning + competing channels + differentiation angle
+
+  - id: title-thumbnail-architecture
+    name: Title × Thumbnail Architecture
+    description: Design 10 title × thumbnail pairs using CTR-tested patterns — curiosity gap + transformation + specificity + visual hierarchy
+    agents:
+      - agent_id: content-director-rafael
+        role: 10 title × thumbnail pairs with CTR pattern named per pair
+      - agent_id: visual-designer-isabel
+        role: Thumbnail visual hierarchy specs (face / contrast / focal-point / text-overlay rules)
+        parallel: true
+    gate:
+      type: user_approval
+      description: User selects 3-5 title × thumbnail pairs for first videos
+
+  - id: hook-script-structure
+    name: Hook × Script Structure
+    description: First 30s hook architecture + retention curve plan for the full script
+    agents:
+      - agent_id: content-director-rafael
+        role: Hook framework (negative → positive → curiosity gap → preview) + retention curve plan
+      - agent_id: sales-copywriter-teresa
+        role: Hook copy variants (3 per video) + script outline with retention drops mapped
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves hook + script structure
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/Content/YouTube/Scripts/"
+        description: Hook architecture + script structure with retention curve plan
+
+  - id: seo-metadata
+    name: SEO & Metadata
+    description: Title keywords, description optimization, tags, end-screen design, playlist architecture
+    agents:
+      - agent_id: content-director-rafael
+        role: SEO metadata specs per video; playlist hierarchy
+      - agent_id: marketing-director-luna
+        role: Keyword research + search volume targeting
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves SEO + playlist architecture
+
+  - id: publishing-cadence
+    name: Publishing Cadence
+    description: Set sustainable publishing cadence with first-week / first-month / first-quarter targets
+    agents:
+      - agent_id: content-director-rafael
+        role: Cadence math + first-week / first-month / first-quarter view + subscriber targets
+    gate:
+      type: user_approval
+      description: User approves cadence and targets
+
+  - id: distribution-amplification
+    name: Distribution & Amplification
+    description: Cross-platform distribution — Shorts derivatives, Twitter/LinkedIn threads, email newsletter, podcast
+    agents:
+      - agent_id: content-director-rafael
+        role: Cross-platform derivative spec per long-form video
+      - agent_id: short-form-specialist
+        role: Shorts adaptation spec (3-5 Shorts per long-form)
+        parallel: true
+    gate:
+      type: auto
+
+  - id: self-critique
+    name: Self-Critique
+    description: Stress-test the strategy — is the cadence sustainable? Does positioning differentiate from competing channels? Does the CTR pattern math hold?
+    agents:
+      - agent_id: content-director-rafael
+        role: Coherence + sustainability + differentiation check
+    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: Title copy, hook copy, script structure, no clickbait that breaks promise
+        parallel: true
+      - agent_id: tech-director-francisca
+        role: Thumbnail visual hierarchy, retention curve feasibility, SEO metadata correctness
+        parallel: true
+    gate:
+      type: quality_gate
+      required_verdict: APPROVED
+
+  - id: delivery
+    name: YouTube Strategy Package Delivery
+    description: Compile the full YouTube strategy package
+    agents:
+      - agent_id: content-director-rafael
+        role: Full YouTube strategy package + 1-page executive summary
+    gate:
+      type: auto
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/Content/YouTube/"
+        description: Complete YouTube strategy — positioning + title × thumbnail pairs + hook architecture + script structure + SEO metadata + publishing cadence + distribution + exec summary

package/departments/strategy/skills/growth-strategy/SKILL.md

@@ -1,7 +1,9 @@
 ---
 name: strat/growth-strategy
 description: >
-  Growth strategy: market penetration, development, product development, diversification.
+  Growth strategy using Ansoff Matrix + adjacency framework + Greiner growth
+  phases. Picks the next growth vector with risk-adjusted feasibility and a
+  12-month execution roadmap.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 
@@ -21,12 +23,139 @@ does not replace the vault.
 
 # Growth Strategy — `/strat growth <business>`
 
-> **Agent:** Tomas (Chief Strategist) | **Framework:** Ansoff Matrix + Adjacencies
+> **Lead:** Tomas (Chief Strategist) | **Cross-dept:** Helena (CFO) + Rita (Market Analyst) | **Frameworks:** Ansoff Matrix + Chris Zook Adjacencies + Greiner Growth Phases
 
-## What It Does
+## What ships
 
-Growth strategy: market penetration, development, product development, diversification.
+A production growth strategy in 6 deliverables:
 
-## Output
+1. **Greiner phase diagnosis** — current phase + impending crisis prediction
+2. **Ansoff Matrix mapping** — concrete options per quadrant with market sizing
+3. **Adjacency analysis** — ranked adjacencies by distance × capability × attractiveness
+4. **Growth vector selection** — primary + assist with explicit trade-off rationale
+5. **Risk profile** — pre-mortem with top 5 risks + early warning signals + mitigations
+6. **12-month execution roadmap** — quarter-by-quarter milestones with named owners
 
-Growth roadmap with Ansoff quadrant, risk assessment, and resource requirements
+## Greiner Growth Phases (where are you in the curve?)
+
+Larry Greiner's model says companies grow through 6 evolutionary phases, each ending in a predictable crisis. Knowing the phase predicts the crisis.
+
+| # | Phase | Driver | Predictable Crisis | Resolution |
+|---|---|---|---|---|
+| 1 | **Creativity** | Founder vision + product-market fit | Leadership Crisis (founder can't manage operations) | Hire professional management |
+| 2 | **Direction** | Top-down management + functional structure | Autonomy Crisis (middle managers blocked by HQ) | Delegate authority downward |
+| 3 | **Delegation** | Decentralised operating units | Control Crisis (HQ loses visibility into BUs) | Build coordination systems |
+| 4 | **Coordination** | Formal systems, planning, ROI gates | Red Tape Crisis (bureaucracy strangles decisions) | Collaboration via teams |
+| 5 | **Collaboration** | Cross-functional teams, matrix structure | Growth Crisis (internal saturation, need new sources) | External alliances / M&A |
+| 6 | **Alliances** | Partnerships, joint ventures, ecosystems | Identity Crisis (who are we?) | Reinvention / spin-out |
+
+Diagnose by symptoms, not org-chart vibes. Each phase has specific decision-making patterns and pain points.
+
+## The Ansoff Matrix (4 growth quadrants)
+
+The 2×2 matrix on Products (existing / new) × Markets (existing / new). Each quadrant has a different risk profile.
+
+```
+                    EXISTING PRODUCTS         NEW PRODUCTS
+EXISTING MARKETS    Market Penetration        Product Development
+                    (lowest risk)             (medium-high risk)
+                    - Cross-sell              - Adjacent product
+                    - Up-sell                 - Same customer expansion
+                    - Win share from competitor
+
+NEW MARKETS         Market Development        Diversification
+                    (medium risk)             (highest risk)
+                    - New geo                 - New product + new market
+                    - New segment             - True new business
+                    - New channel             - Acquisition often required
+```
+
+Default risk-adjusted sequencing: start with **Market Penetration** until the law of diminishing returns hits (typically 70-80% market share in a defined segment). Then choose between Market Development and Product Development based on capability fit. Diversification only when first three quadrants are exhausted or a structural opportunity is undeniable.
+
+## Chris Zook Adjacency Framework
+
+For each candidate growth move, score on three dimensions:
+
+1. **Distance from core** (1-10): How far is this from your repeatable model? 1 = same customer + same product + tweaks. 10 = different customer + different product + different capability.
+2. **Capability fit** (1-10): Does it use your existing strengths? 10 = leverages your core competence. 1 = requires building all-new capability.
+3. **Market attractiveness** (1-10): Size × growth × profitability of the target market.
+
+Zook's empirical finding: **adjacency success rate drops 50% with every step away from core**. So the math:
+
+```
+expected_success_rate = 0.27 × (0.5 ^ distance_from_core_steps) × capability_fit_factor × market_factor
+```
+
+Adjacencies more than 2 steps from core have <10% historical success rate. Pick the closest viable adjacency, not the most attractive one.
+
+## Growth Vector Decision Tree
+
+```
+Is current retention healthy (D30 > category norm)?
+  NO  → Fix retention. No growth vector survives broken retention.
+  YES → Continue.
+
+Have you saturated current market segment (>70% share or stalled)?
+  NO  → Market Penetration is the default. Cross-sell, up-sell, win share.
+  YES → Continue.
+
+Do you have unique capability that transfers?
+  YES → Product Development (new product to existing customers) OR
+        Market Development (existing product to new segment / geo).
+        Choose by capability fit score.
+  NO  → Acquisition or partnership required. Diversification.
+```
+
+## Risk Profile Template
+
+Every growth vector ships with a pre-mortem. Format:
+
+```yaml
+top_5_risks:
+  - name: <specific risk>
+    probability: low | medium | high
+    impact: low | medium | high | terminal
+    early_warning_signal: <observable signal in first 90 days>
+    mitigation: <named action if signal fires>
+    owner: <named human>
+```
+
+Risks must be specific. "Market might shift" is vibes; "if our top 3 partners renegotiate pricing in Q2 our gross margin drops below the cost floor" is a risk.
+
+## 12-Month Roadmap Template
+
+```
+Q1: Foundation
+  Milestone: [specific outcome, not activity]
+  Owner: [named human]
+  Success metric: [measurable number]
+
+Q2: First Proof
+  Milestone: [first measurable signal that vector is working]
+  Owner: [named]
+  Decision gate: [continue / pivot criteria]
+
+Q3: Scale or Pivot
+  Decision: [scale signal observed? Y/N]
+  If scale: doubling milestone
+  If pivot: alternate vector selected
+
+Q4: Compound
+  Milestone: [vector now self-sustaining or absorbed into ops]
+  Owner: [named]
+  Year-end metric: [measurable target tied to original brief]
+```
+
+Every quarter has a decision gate, not just a milestone. Roadmaps without decision gates become wish lists.
+
+## Common Failure Modes
+
+1. **Skipping retention check** — chasing growth on broken retention amplifies churn
+2. **Ansoff diagonal-jumping** — jumping straight to Diversification without proving Market Penetration is exhausted
+3. **Capability vanity** — picking the most attractive adjacency instead of the highest-fit one
+4. **Greiner phase denial** — refusing to acknowledge the next crisis (e.g., founder won't delegate, stays in Direction phase past breakeven)
+5. **Roadmap without decision gates** — quarterly milestones without "continue / pivot" criteria become marketing for the existing strategy
+
+## Output → Obsidian: `WizardingCode/Strategy/Growth/<business>-<date>/`
+
+Delivers: Greiner phase diagnosis + Ansoff Matrix mapping + adjacency analysis + vector selection rationale + risk profile (5 risks with mitigations) + 12-month roadmap with decision gates + 1-page executive summary.

package/departments/strategy/workflows/blue-ocean.yaml

@@ -0,0 +1,136 @@
+id: strat-blue-ocean
+name: Blue Ocean Strategy
+description: Blue Ocean Strategy canvas with ERRC grid (Eliminate / Reduce / Raise / Create) — define uncontested market space
+department: strategy
+tier: enterprise
+command: "/strat blue-ocean"
+requires_branch: false
+requires_spec: false
+quality_gate_required: true
+
+phases:
+  - id: brief
+    name: Market Brief
+    description: Define the current market, the industry's competitive factors, and the customer base under analysis
+    agents:
+      - agent_id: strategy-director-tomas
+        role: Frame current market, named competitors, customer segments
+    gate:
+      type: user_approval
+      description: User confirms market scope, competitor set, customer segments
+
+  - id: red-ocean-canvas
+    name: Red Ocean Strategy Canvas
+    description: Map the current industry on the Strategy Canvas — 6-10 competitive factors with relative levels
+    agents:
+      - agent_id: strategy-director-tomas
+        role: Identify 6-10 competitive factors the industry competes on; score each competitor 1-10
+    gate:
+      type: user_approval
+      description: User approves the red ocean canvas before ERRC analysis
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/Strategy/BlueOcean/Canvas/"
+        description: Red Ocean Strategy Canvas with competitor scores per factor
+
+  - id: errc-grid
+    name: ERRC Grid
+    description: Apply the ERRC framework — Eliminate / Reduce / Raise / Create — to redesign the value curve
+    agents:
+      - agent_id: strategy-director-tomas
+        role: ERRC analysis on each competitive factor with rationale
+      - agent_id: market-analyst-rita
+        role: Non-customer analysis — what would the 3 tiers of non-customers value?
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves the ERRC grid
+
+  - id: non-customer-analysis
+    name: Non-Customer Analysis
+    description: Map the 3 tiers of non-customers (Soon-to-be, Refusing, Unexplored) and what would convert each tier
+    agents:
+      - agent_id: market-analyst-rita
+        role: Define 3 non-customer tiers with their reasons for not buying and conversion triggers
+    gate:
+      type: user_approval
+      description: User approves non-customer analysis
+
+  - id: blue-ocean-canvas
+    name: Blue Ocean Strategy Canvas
+    description: Draw the new value curve — the blue ocean position based on ERRC + non-customer insights
+    agents:
+      - agent_id: strategy-director-tomas
+        role: Blue Ocean Strategy Canvas with new value curve; quantify divergence from red ocean
+    gate:
+      type: user_approval
+      description: User approves the blue ocean canvas before viability test
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/Strategy/BlueOcean/Canvas/"
+        description: Blue Ocean Strategy Canvas with new value curve and divergence analysis
+
+  - id: viability-test
+    name: Commercial Viability Test
+    description: Apply the BOS Sequence — Utility, Price, Cost, Adoption — to test whether the blue ocean is commercially viable
+    agents:
+      - agent_id: strategy-director-tomas
+        role: BOS Sequence test (Buyer Utility Map, Strategic Pricing, Target Cost, Adoption Hurdles)
+      - agent_id: cfo-helena
+        role: Cost feasibility check — does the target cost math work given the price corridor?
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves commercial viability before execution plan
+
+  - id: execution-plan
+    name: Execution Plan
+    description: 90-day execution — first product/service move, channels, organisational changes
+    agents:
+      - agent_id: strategy-director-tomas
+        role: 90-day execution plan with first move, channel implications, organisational changes
+    gate:
+      type: user_approval
+      description: User approves the 90-day execution plan
+
+  - id: self-critique
+    name: Self-Critique
+    description: Stress-test the blue ocean — is the divergence real? Are non-customer triggers credible? Does the cost math close?
+    agents:
+      - agent_id: strategy-director-tomas
+        role: Coherence + viability + execution feasibility cross-check
+    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: Canvas labels, non-customer prose, no clichés
+        parallel: true
+      - agent_id: tech-director-francisca
+        role: Visual canvas integrity, ERRC grid completeness, viability test math
+        parallel: true
+    gate:
+      type: quality_gate
+      required_verdict: APPROVED
+
+  - id: delivery
+    name: Blue Ocean Package Delivery
+    description: Compile the full blue ocean package
+    agents:
+      - agent_id: strategy-director-tomas
+        role: Full blue ocean package + 1-page executive summary
+    gate:
+      type: auto
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/Strategy/BlueOcean/"
+        description: Complete blue ocean package — red ocean canvas + ERRC grid + non-customer analysis + blue ocean canvas + viability test + execution plan

package/departments/strategy/workflows/growth.yaml

@@ -0,0 +1,139 @@
+id: strat-growth
+name: Growth Strategy
+description: Growth strategy using Ansoff Matrix + adjacencies + Greiner growth phases — pick the next growth vector with risk-adjusted feasibility
+department: strategy
+tier: enterprise
+command: "/strat growth"
+requires_branch: false
+requires_spec: false
+quality_gate_required: true
+
+phases:
+  - id: brief
+    name: Growth Brief
+    description: Define current business state, current revenue mix, current growth rate, runway, success metric
+    agents:
+      - agent_id: strategy-director-tomas
+        role: Frame current business — products, markets, revenue mix, growth rate, runway
+    gate:
+      type: user_approval
+      description: User confirms business context and growth target
+
+  - id: greiner-diagnosis
+    name: Greiner Growth Phase Diagnosis
+    description: Identify which Greiner growth phase the business is in (Creativity / Direction / Delegation / Coordination / Collaboration / Alliances) and the predictable crisis
+    agents:
+      - agent_id: strategy-director-tomas
+        role: Greiner phase diagnosis with evidence; name the impending crisis
+    gate:
+      type: user_approval
+      description: User approves Greiner diagnosis
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/Strategy/Growth/Diagnosis/"
+        description: Greiner growth phase diagnosis with crisis prediction
+
+  - id: ansoff-matrix
+    name: Ansoff Matrix Analysis
+    description: Map growth options across the 4 Ansoff quadrants (Market Penetration / Market Development / Product Development / Diversification)
+    agents:
+      - agent_id: strategy-director-tomas
+        role: Ansoff Matrix mapping with concrete options per quadrant
+      - agent_id: market-analyst-rita
+        role: Market sizing per quadrant option
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves Ansoff Matrix mapping before adjacency analysis
+
+  - id: adjacency-analysis
+    name: Adjacency Analysis
+    description: Apply Chris Zook's adjacency framework — score each adjacency by distance from core, capability fit, market attractiveness
+    agents:
+      - agent_id: strategy-director-tomas
+        role: Adjacency scoring (distance from core × capability fit × market attractiveness)
+      - agent_id: cfo-helena
+        role: Investment requirement and payback per adjacency
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves adjacency scoring
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/Strategy/Growth/Adjacencies/"
+        description: Ranked adjacency analysis with investment + payback
+
+  - id: vector-selection
+    name: Growth Vector Selection
+    description: Pick the primary growth vector + assist vector based on Greiner phase, Ansoff quadrant, adjacency ranking
+    agents:
+      - agent_id: strategy-director-tomas
+        role: Vector selection with explicit trade-off rationale
+    gate:
+      type: user_approval
+      description: User approves primary + assist growth vector
+
+  - id: risk-feasibility
+    name: Risk & Feasibility
+    description: Stress-test the chosen vector — what kills it? What signals indicate it's working / failing?
+    agents:
+      - agent_id: strategy-director-tomas
+        role: Pre-mortem analysis — top 5 risks + early warning signals + mitigation per risk
+      - agent_id: cfo-helena
+        role: Runway impact per vector, breakeven scenario, downside math
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves risk profile
+
+  - id: execution-roadmap
+    name: 12-Month Execution Roadmap
+    description: Quarter-by-quarter milestones, owner per milestone, success metric per quarter
+    agents:
+      - agent_id: strategy-director-tomas
+        role: 12-month roadmap with quarterly milestones and named owners
+    gate:
+      type: user_approval
+      description: User approves the 12-month roadmap
+
+  - id: self-critique
+    name: Self-Critique
+    description: Stress-test coherence — does Greiner phase support the chosen vector? Does Ansoff position match adjacency ranking?
+    agents:
+      - agent_id: strategy-director-tomas
+        role: Coherence check across Greiner / Ansoff / adjacency / vector / roadmap
+    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: Diagnosis prose, vector rationale, no clichés
+        parallel: true
+      - agent_id: tech-director-francisca
+        role: Roadmap executability, milestone measurability, owner specificity
+        parallel: true
+    gate:
+      type: quality_gate
+      required_verdict: APPROVED
+
+  - id: delivery
+    name: Growth Strategy Package Delivery
+    description: Compile the full growth strategy package
+    agents:
+      - agent_id: strategy-director-tomas
+        role: Full growth package + 1-page executive summary
+    gate:
+      type: auto
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/Strategy/Growth/"
+        description: Complete growth package — Greiner diagnosis + Ansoff Matrix + adjacency analysis + vector selection + risk profile + 12-month roadmap

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "arkaos",
-  "version": "2.53.0",
+  "version": "2.55.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.53.0"
+version = "2.55.0"
 description = "Core engine for ArkaOS — The Operating System for AI Agent Teams"
 readme = "README.md"
 license = {text = "MIT"}