arkaos 2.52.0 → 2.54.0

package/VERSION

@@ -1 +1 @@
-2.52.0
+2.54.0

package/departments/marketing/skills/growth-loop/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: mkt/growth-loop
 description: >
-  Design sustainable growth loops (viral, paid, product) that compound over time.
-  Replaces linear funnels with self-reinforcing cycles.
+  Design sustainable growth loops (viral, paid, content, product, community) that compound over time.
+  Replaces linear funnels with self-reinforcing cycles. Spec + math + instrumentation + 30-day experiment plan.
 allowed-tools: [Read, Write, Edit, Agent, WebFetch, WebSearch]
 ---
 
@@ -22,43 +22,160 @@ does not replace the vault.
 
 # Growth Loop Design — `/mkt growth-loop`
 
-> **Agent:** Luna (Marketing Director) | **Framework:** Growth Loops (Andrew Chen / Reforge)
+> **Lead:** Luna (Marketing Director) | **Cross-dept:** Pedro (Paid Specialist) + Tomas (Strategy) + Helena (CFO) | **Framework:** Growth Loops (Andrew Chen / Reforge)
 
 ## Why Loops > Funnels
 
-Funnels are linear: input stops → output stops.
-Loops are circular: output feeds next cycle's input.
+Funnels are linear: input stops → output stops. Every new customer requires fresh top-of-funnel work. CAC stays flat or rises.
 
-## 3 Loop Types
+Loops are circular: **output feeds the next cycle's input**. The system gets stronger with use. CAC trends toward zero on the marginal customer.
+
+A growing business is the sum of working loops, not the sum of funnels.
+
+## Loop Type Decision Matrix
+
+Pick the primary loop based on product DNA, retention shape, and unit economics. Mixing loop types without committing to a primary produces zero compounding.
+
+| Loop type | Default product DNA | Min retention | Min unit econ | Compounding rate | Typical payback |
+|---|---|---|---|---|---|
+| **Viral** | UGC, communication, multiplayer | D30 ≥ 25% | Free or freemium | K-factor (target > 0.5) | Weeks |
+| **Paid** | Clear LTV signal, AOV ≥ CAC × 3 | D30 ≥ 30% | LTV/CAC ≥ 3 | Reinvest ratio | 6-12 months |
+| **Content** | Searchable problem space, repeat searcher | Brand recall | Long-tail compound | Page-month growth | 3-12 months |
+| **Product** | Multi-user by design (invite, share, embed) | D30 ≥ 40% | Free trial / freemium | Natural rate of growth | Months |
+| **Community** | Identity-driven adoption, practitioner audience | D90 ≥ 50% | LTV scales with engagement | Member-second-order growth | Quarters |
+
+If you don't pass any minimum, **fix retention first**. Loops on broken retention amplify churn.
+
+## The 5 Loop Types Fully Spec'd
 
 ### 1. Viral Loop (User-Generated)
+
 ```
-User creates content → Content indexed/shared → New user discovers → Signs up → REPEAT
+User creates content → Content indexed/shared → New user discovers → Signs up → Creates content → REPEAT
 ```
-Example: Pinterest, YouTube, Notion templates
-Key metric: Viral coefficient (K-factor > 1 = exponential)
+
+Worked example: Pinterest, YouTube, Notion templates, Figma community files.
+
+Key metric: **K-factor** = invites sent × conversion rate. K > 1 = exponential. K = 0.5 means each new user brings 0.5 more (sub-viral but compounds with paid).
+
+Failure modes: K declines as audience saturates → loop dies. Invite incentives without product value → users opt out. Content production without index → SEO doesn't pick up.
+
+Instrumentation needed: sign-up event with source (viral_invite vs organic), invite-sent event with recipient_id, conversion event from invite landing.
 
 ### 2. Paid Loop (Revenue-Funded)
+
 ```
 User pays → Revenue reinvested in ads → New user acquired → Pays → REPEAT
 ```
-Example: DTC brands, SaaS with efficient paid
-Requirement: LTV:CAC > 3:1, payback < 12 months
 
-### 3. Product Loop (Built-in)
+Worked example: DTC brands with strong AOV, SaaS with efficient paid (Notion, Webflow at scale), pure-play e-commerce.
+
+Required unit economics: **LTV/CAC ≥ 3, CAC payback < 12 months**. Below those, the loop runs negative against runway.
+
+Failure modes: Channel saturation drives CAC up faster than LTV improves. Single-channel concentration (90% Meta) collapses on platform changes. Attribution opacity prevents real ROI measurement → you reinvest into losing channels.
+
+Instrumentation needed: per-channel CAC tracking, cohort LTV (D30/D90/D365), payback cohort analysis, attribution model (last-touch + multi-touch comparison).
+
+### 3. Content Loop (Search-Driven)
+
+```
+User searches problem → Lands on content → Converts to lead/customer → Content earns links → Ranks higher → More searchers find it → REPEAT
+```
+
+Worked example: Ahrefs, HubSpot, Investopedia, Wirecutter.
+
+Key metric: **Page-month growth rate** + **Domain Authority compounding**. New page-months publish faster than old page-months decay.
+
+Failure modes: Content quality below SERP threshold → no ranking. No internal linking → no topical authority. AI-flood post-2024 raised the quality floor; thin content doesn't rank.
+
+Instrumentation needed: GSC clicks/impressions per page, organic conversion rate per page, time-to-first-rank, total indexable pages.
+
+### 4. Product Loop (Built-in Virality)
+
+```
+User uses product → Product surface exposes to others → Others see it / receive output → Sign up / install → REPEAT
+```
+
+Worked example: Slack (invite team), Dropbox (share file), Calendly (send invite link), Figma (share design link), Loom (share recording).
+
+Key metric: **Natural rate of growth** = % of new users from product surface (not paid, not virally invited).
+
+Failure modes: Product output stays inside the team (no external exposure surface). Sharing requires extra steps (high friction). Output looks bad outside the product (no brand impression).
+
+Instrumentation needed: source attribution on first session (product_share_url vs organic vs paid), share-link click-to-signup conversion, output-publish event tracking.
+
+### 5. Community Loop (Identity-Driven)
+
 ```
-User uses product → Product exposes to others → Others join → REPEAT
+Practitioner joins community → Status from contributing → Other practitioners notice → Join → Contribute → REPEAT
 ```
-Example: Slack (invite team), Dropbox (share files), Calendly (send invite)
-Key metric: Natural rate of growth (organic + viral, no paid)
 
-## Loop Mapping Process
+Worked example: Stack Overflow, Reddit communities, Substack networks, Slack practitioner groups, Discord servers.
+
+Key metric: **Member-second-order growth** — for every new member, how many new members do they bring within 90 days?
+
+Failure modes: Community grows but doesn't tie to product revenue (community-led ≠ revenue loop). Status hierarchy collapses → top contributors leave. Spam erodes signal → quality contributors disengage.
+
+Instrumentation needed: cohort retention curves (D30/D90/D365), contribution distribution (Gini coefficient), second-order growth attribution.
+
+## Loop Specification Format
+
+Every loop spec must answer these 6 questions in the same shape:
+
+```yaml
+loop_name: <descriptive name>
+loop_type: viral | paid | content | product | community
+
+step_1_trigger:
+  what_happens: <observable event>
+  mechanism: <named mechanism, not vibes>
+  metric: <measurable target>
+  owner: <named human>
+
+step_2_action:
+  what_user_does: <observable user action>
+  mechanism: <what makes this action likely>
+  metric: <conversion rate target>
+  owner: <named human>
+
+step_3_output:
+  what_gets_produced: <artifact, signal, content, money>
+  visibility: <internal | shareable | indexed | broadcast>
+  metric: <output volume target>
+  owner: <named human>
+
+step_4_reinput:
+  how_output_becomes_input: <named mechanism>
+  audience: <who sees the output>
+  metric: <reinput conversion rate>
+  owner: <named human>
+
+cycle_time: <hours / days / weeks per full loop>
+compounding_factor: <K-factor / reinvest ratio / page velocity / NRG / 2nd-order rate>
+breakeven_threshold: <the number where loop self-sustains>
+```
+
+## Loop Design Checklist (pre-instrumentation)
+
+Before instrumenting, the loop must pass these 8 checks. Failing any check means the loop is incoherent — fix the spec before tracking.
+
+- [ ] **Output is observable** — the loop's output (artifact, signal, post, share) can be counted, not inferred
+- [ ] **Re-input mechanism is named** — "users tell their friends" is vibes; "invite link with referral code on Day 7 prompt" is a mechanism
+- [ ] **No infinite resource assumed** — the loop doesn't require infinite content production, infinite paid budget, or infinite founder time
+- [ ] **Step ownership is human-named** — every step has a named owner, not "marketing team"
+- [ ] **Cycle time is sub-quarterly** — at least one full loop completes within 90 days, otherwise feedback is too slow
+- [ ] **Compounding factor is computable** — you can express the math: K-factor, reinvest ratio, NRG percentage
+- [ ] **Breakeven threshold is named** — you know the number at which the loop self-sustains
+- [ ] **Failure modes are listed** — the spec names 2-3 things that would kill the loop and the early signals
+
+## Common Failure Modes Across All Loop Types
+
+1. **Mistaking content for loop** — publishing content monthly isn't a loop unless each piece earns links/searches that bring new users
+2. **No instrumentation** — without per-step tracking, you can't tell if the loop is working or if growth is from somewhere else
+3. **Multiple half-loops** — running 3 loops at 0.3x compounding ≠ 1 loop at 1.0x. Pick a primary
+4. **Loop without retention** — a loop on broken retention amplifies churn. Fix D30 first
+5. **Loop ignores unit economics** — viral loops still need someone to pay eventually; product loops still need conversion rate
 
-1. **Identify the trigger** — What starts the cycle?
-2. **Map the user action** — What does the user do?
-3. **Find the output** — What does the action produce?
-4. **Trace the reinput** — How does output bring new users?
-5. **Measure the cycle** — How long is one loop? What's the conversion at each step?
-6. **Optimize the bottleneck** — Which step has the biggest drop-off?
+## Output → Obsidian: `WizardingCode/Marketing/GrowthLoops/<product>-<date>/`
 
-## Output → Growth loop diagram + metrics per step + optimization plan
+Delivers: retention baseline + loop type selection rationale + full loop spec (all 4 steps with mechanism/metric/owner per step) + compounding math + unit economics check + instrumentation tracking spec + 30-day experiment plan + 1-page executive summary.

package/departments/marketing/workflows/growth-loop.yaml

@@ -0,0 +1,141 @@
+id: mkt-growth-loop
+name: Growth Loop Design
+description: Design a sustainable growth loop (viral / paid / content / product / community) that compounds over time
+department: marketing
+tier: enterprise
+command: "/mkt growth-loop"
+requires_branch: false
+requires_spec: false
+quality_gate_required: true
+
+phases:
+  - id: brief
+    name: Growth Loop Brief
+    description: Frame product, current growth, audience, retention baseline, runway
+    agents:
+      - agent_id: marketing-director-luna
+        role: Frame product, current new-user volume, current retention curve (D1/D7/D30), runway
+    gate:
+      type: user_approval
+      description: User confirms product context, current growth, retention baseline
+
+  - id: retention-baseline
+    name: Retention Baseline
+    description: Measure the current retention curve and identify the activation moment
+    agents:
+      - agent_id: marketing-director-luna
+        role: Compute D1/D7/D30/D90 retention from existing analytics, identify activation event
+      - agent_id: strategy-director-tomas
+        role: Compare retention to category norms; flag whether product-market fit is plausible
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves retention baseline and activation event
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/Marketing/GrowthLoops/Baseline/"
+        description: Retention baseline with activation event and category comparison
+
+  - id: loop-selection
+    name: Loop Type Selection
+    description: Pick the primary loop type (viral / paid / content / product / community) based on product DNA and retention curve
+    agents:
+      - agent_id: marketing-director-luna
+        role: Apply loop-type fitness matrix (retention shape × CAC payback × content production capacity)
+      - agent_id: paid-specialist-pedro
+        role: Paid-loop feasibility math (CAC × LTV × payback window)
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves loop type + secondary loop choice
+
+  - id: loop-design
+    name: Loop Specification
+    description: Spec the loop — Input → Action → Output → Re-input. Define every step's mechanism and metric
+    agents:
+      - agent_id: marketing-director-luna
+        role: Loop spec with named mechanism per step and target metric per step
+    gate:
+      type: user_approval
+      description: User approves the loop spec before instrumentation
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/Marketing/GrowthLoops/Specs/"
+        description: Loop specification with per-step mechanisms and metrics
+
+  - id: compounding-math
+    name: Compounding Math
+    description: Compute the loop's compounding factor — viral coefficient K, content velocity, CAC payback — and the conditions for self-sustaining
+    agents:
+      - agent_id: marketing-director-luna
+        role: Compute K-factor / content compounding rate / payback window; identify the breakeven threshold
+      - agent_id: cfo-helena
+        role: Validate unit economics — LTV/CAC, contribution margin, runway impact
+        parallel: true
+    gate:
+      type: user_approval
+      description: User approves the loop economics
+
+  - id: instrumentation
+    name: Instrumentation
+    description: Define the tracking spec — every loop step needs an event + a dashboard widget
+    agents:
+      - agent_id: marketing-director-luna
+        role: Event schema per step, dashboard layout, owner per metric
+      - agent_id: tech-director-francisca
+        role: Tracking implementation feasibility check
+        parallel: true
+    gate:
+      type: auto
+
+  - id: experiment-plan
+    name: 30-Day Experiment Plan
+    description: First 30 days — what to test, what hypothesis per test, how to declare a win
+    agents:
+      - agent_id: marketing-director-luna
+        role: 3-5 prioritized experiments with hypothesis, MDE, success criteria
+    gate:
+      type: user_approval
+      description: User approves the 30-day experiment plan
+
+  - id: self-critique
+    name: Self-Critique
+    description: Stress-test the loop — is every step instrumented? Are dependencies named? What kills the loop?
+    agents:
+      - agent_id: marketing-director-luna
+        role: Loop coherence + failure-mode enumeration
+    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: Loop documentation clarity, no clichés, mechanism specificity
+        parallel: true
+      - agent_id: tech-director-francisca
+        role: Instrumentation correctness, tracking event integrity, dashboard feasibility
+        parallel: true
+    gate:
+      type: quality_gate
+      required_verdict: APPROVED
+
+  - id: delivery
+    name: Growth Loop Package Delivery
+    description: Compile the loop package — spec + economics + instrumentation + experiment plan
+    agents:
+      - agent_id: marketing-director-luna
+        role: Full growth loop package + 1-page executive summary
+    gate:
+      type: auto
+    outputs:
+      - type: document
+        format: markdown
+        obsidian_path: "WizardingCode/Marketing/GrowthLoops/"
+        description: Complete growth loop package — retention baseline + loop spec + compounding math + instrumentation spec + 30-day experiment plan + 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.52.0",
+  "version": "2.54.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.52.0"
+version = "2.54.0"
 description = "Core engine for ArkaOS — The Operating System for AI Agent Teams"
 readme = "README.md"
 license = {text = "MIT"}