arkaos 2.5.3 → 2.7.0

package/VERSION

@@ -1 +1 @@
-2.5.3
+2.7.0

package/config/constitution.yaml

@@ -58,6 +58,10 @@ enforcement_levels:
         rule: "ArkaOS instructions override runtime defaults"
         enforcement: "ArkaOS context injected with highest priority"
 
+      - id: context-verification
+        rule: "Orchestrators must confirm understanding, ask clarifying questions, and challenge assumptions before executing any task"
+        enforcement: "Pre-execution gate — restate request, ask at least 1 clarifying question, apply devil's advocate to at least 1 assumption"
+
   quality_gate:
     description: "Mandatory pre-delivery review. Nothing ships without APPROVED verdict."
     trigger: "After the last execution phase, before delivery to user"
@@ -105,6 +109,10 @@ enforcement_levels:
         rule: "Key decisions persisted in agent memory files"
         enforcement: "Post-execution hook saves decisions to agent MEMORY.md"
 
+      - id: workflow-standard
+        rule: "All ecosystem skills must follow the standard 7-phase workflow defined in config/standards/ecosystem-workflow.md"
+        enforcement: "Ecosystem SKILL.md files must reference or implement all 7 phases"
+
   should:
     description: "Best practices. Encouraged but not enforced."
     rules:

package/config/hooks/user-prompt-submit-v2.sh

@@ -18,6 +18,56 @@ for v1_path in "${V1_PATHS[@]}"; do
   fi
 done
 
+# ─── Sync Version Detection ────────────────────────────────────────────
+SYNC_STATE="$HOME/.arkaos/sync-state.json"
+ARKAOS_VERSION_FILE="$HOME/.arkaos/.repo-path"
+
+if [ -f "$ARKAOS_VERSION_FILE" ]; then
+  _REPO_PATH=$(cat "$ARKAOS_VERSION_FILE")
+  if [ -f "$_REPO_PATH/VERSION" ]; then
+    _CURRENT_VERSION=$(cat "$_REPO_PATH/VERSION")
+  elif [ -f "$_REPO_PATH/package.json" ]; then
+    _CURRENT_VERSION=$(python3 -c "import json; print(json.load(open('$_REPO_PATH/package.json'))['version'])" 2>/dev/null || echo "")
+  fi
+
+  if [ -n "${_CURRENT_VERSION:-}" ]; then
+    if [ -f "$SYNC_STATE" ]; then
+      _SYNCED_VERSION=$(python3 -c "import json; print(json.load(open('$SYNC_STATE'))['version'])" 2>/dev/null || echo "none")
+    else
+      _SYNCED_VERSION="none"
+    fi
+
+    if [ "$_CURRENT_VERSION" != "$_SYNCED_VERSION" ]; then
+      _SYNC_NOTICE="[arka:update-available] ArkaOS v${_CURRENT_VERSION} installed (synced: ${_SYNCED_VERSION}). Run /arka update to sync all projects. "
+    fi
+  fi
+fi
+
+# ─── Session Greeting ───────────────────────────────────────────────────
+_SESSION_MARKER="/tmp/arkaos-session-$$"
+if [ ! -f "$_SESSION_MARKER" ] && [ ! -f "/tmp/arkaos-greeted-today" ]; then
+  touch "$_SESSION_MARKER"
+  touch "/tmp/arkaos-greeted-today"
+
+  _GREETING_NAME=""
+  _GREETING_COMPANY=""
+  _GREETING_VERSION=""
+
+  if [ -f "$HOME/.arkaos/profile.json" ] && command -v python3 &>/dev/null; then
+    _GREETING_NAME=$(python3 -c "import json; p=json.load(open('$HOME/.arkaos/profile.json')); print(p.get('name', p.get('role', 'founder')))" 2>/dev/null)
+    _GREETING_COMPANY=$(python3 -c "import json; print(json.load(open('$HOME/.arkaos/profile.json')).get('company', ''))" 2>/dev/null)
+  fi
+
+  if [ -f "$HOME/.arkaos/.repo-path" ]; then
+    _GR_REPO=$(cat "$HOME/.arkaos/.repo-path")
+    if [ -f "$_GR_REPO/VERSION" ]; then
+      _GREETING_VERSION=$(cat "$_GR_REPO/VERSION")
+    fi
+  fi
+
+  _ARKA_GREETING="[arka:greeting]     _    ____  _  __    _    ___  ____     / \\  |  _ \\| |/ /   / \\  / _ \\/ ___|   / _ \\ | |_) | ' /   / _ \\| | | \\___ \\  / ___ \\|  _ <| . \\  / ___ \\ |_| |___) | /_/   \\_\\_| \\_\\_|\\_\\/_/   \\_\\___/|____/  Welcome back, ${_GREETING_NAME:-founder} (${_GREETING_COMPANY:-WizardingCode}). ArkaOS v${_GREETING_VERSION:-2.x} ready. Type /arka help or just describe what you need. "
+fi
+
 # ─── Performance Timing ──────────────────────────────────────────────────
 _HOOK_START_NS=$(date +%s%N 2>/dev/null || echo "0")
 _hook_ms() {
@@ -103,7 +153,7 @@ if [ -z "$python_result" ]; then
 fi
 
 # ─── Output ──────────────────────────────────────────────────────────────
-echo "{\"additionalContext\": \"$python_result\"}"
+echo "{\"additionalContext\": \"${_ARKA_GREETING:-}${_SYNC_NOTICE:-}$python_result\"}"
 
 # ─── Metrics ─────────────────────────────────────────────────────────────
 elapsed=$(_hook_ms)

package/config/standards/ecosystem-workflow.md

@@ -0,0 +1,60 @@
+# ArkaOS -- Standard Ecosystem Workflow
+
+> All ecosystem skills MUST follow this workflow. No exceptions.
+> This is referenced by all ecosystem SKILL.md files.
+
+## Phase 1: Context Loading
+
+- Read ecosystem registry (`~/.claude/skills/arka/knowledge/ecosystems.json`)
+- Read project descriptor(s) for affected project(s)
+- Read project CLAUDE.md if it exists
+- Check git status and current branch
+- Load relevant memory from claude-mem
+
+## Phase 2: Context Verification (NON-NEGOTIABLE)
+
+- Restate the request to confirm understanding
+- Ask at least 1 clarifying question about scope or intent
+- Challenge at least 1 assumption (devil's advocate)
+- Search memory/knowledge base for prior related work
+- Only proceed after user confirms understanding
+
+## Phase 3: Analysis & Planning
+
+- Identify affected projects within the ecosystem
+- Determine which squad roles are needed
+- Assess complexity (simple/medium/complex)
+- Create execution plan with specific steps
+
+## Phase 4: Plan Presentation & Approval
+
+- Present the plan to the user with:
+  - Affected files/projects
+  - Squad roles assigned
+  - Estimated scope (small/medium/large)
+  - Risks or concerns
+- Wait for explicit user approval
+- Options: Approve / Modify / Cancel
+
+## Phase 5: Execution
+
+- Create feature branch (NON-NEGOTIABLE for code changes)
+- Use worktree isolation for multi-file changes
+- Squad agents execute in their domain
+- Follow TDD where applicable
+- Commit frequently with conventional commit messages
+
+## Phase 6: Quality Gate (NON-NEGOTIABLE)
+
+- **Marta** (CQO) orchestrates the review
+- **Eduardo** (Copy Director) reviews all text output
+- **Francisca** (Tech/UX Director) reviews all code and technical output
+- Verdict: APPROVED or REJECTED
+- REJECTED -> return to Phase 5 with specific feedback
+- APPROVED -> proceed to Phase 7
+
+## Phase 7: Documentation & Report
+
+- Update Obsidian vault with deliverables
+- Present final report to user
+- Include: what was done, files changed, tests run, next steps

package/installer/update.js

@@ -135,6 +135,20 @@ export async function update() {
   writeFileSync(manifestPath, JSON.stringify(manifest, null, 2));
   console.log("         ✓ Manifest updated");
 
+  // Reset sync state to trigger /arka update on next session
+  const syncStatePath = join(installDir, "sync-state.json");
+  const syncState = {
+    version: "pending-sync",
+    last_sync: null,
+    projects_synced: 0,
+    skills_synced: 0,
+    errors: [],
+    core_updated_to: VERSION,
+    core_updated_at: new Date().toISOString()
+  };
+  writeFileSync(syncStatePath, JSON.stringify(syncState, null, 2));
+  console.log("         ✓ Sync state reset (run /arka update to sync projects)");
+
   console.log(`
   ╔══════════════════════════════════════════╗
   ║  ArkaOS updated to v${VERSION}              ║
@@ -146,6 +160,6 @@ export async function update() {
     Projects:  ${profile.projectsDir || "not set"}
     Vault:     ${profile.vaultPath || "not set"}
 
-  Run 'npx arkaos doctor' to verify.
+  ⚠ Run /arka update in Claude Code to sync all projects.
   `);
 }

package/knowledge/agents-registry.json

@@ -116,10 +116,10 @@
       "id": "coo",
       "display_name": "Sofia",
       "role": "COO",
-      "department": "operations",
+      "department": "ops",
       "tier": 0,
       "disc": { "primary": "S", "secondary": "C", "combination": "S+C", "label": "Supporter-Analyst" },
-      "file": "departments/operations/agents/coo.md",
+      "file": "departments/ops/agents/ops-lead.yaml",
       "memory_path": "~/.claude/agent-memory/arka-coo/MEMORY.md",
       "key_authority": ["veto", "approve_operations", "cross_department"]
     },
@@ -138,10 +138,10 @@
       "id": "ecommerce-manager",
       "display_name": "Ricardo",
       "role": "E-commerce Manager",
-      "department": "ecommerce",
+      "department": "ecom",
       "tier": 1,
       "disc": { "primary": "D", "secondary": "I", "combination": "D+I", "label": "Driver-Inspirer" },
-      "file": "departments/ecommerce/agents/ecommerce-manager.md",
+      "file": "departments/ecom/agents/ecom-director.yaml",
       "memory_path": "~/.claude/agent-memory/arka-ecommerce-manager/MEMORY.md",
       "key_authority": ["manage_store", "pricing_decisions"]
     },
@@ -160,10 +160,10 @@
       "id": "knowledge-curator",
       "display_name": "Clara",
       "role": "Knowledge Curator",
-      "department": "knowledge",
+      "department": "kb",
       "tier": 1,
       "disc": { "primary": "S", "secondary": "C", "combination": "S+C", "label": "Supporter-Analyst" },
-      "file": "departments/knowledge/agents/knowledge-curator.md",
+      "file": "departments/kb/agents/knowledge-curator.yaml",
       "memory_path": "~/.claude/agent-memory/arka-knowledge-curator/MEMORY.md",
       "key_authority": ["manage_knowledge", "create_personas"]
     },

package/package.json

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

package/departments/ecommerce/SKILL.md

@@ -1,363 +0,0 @@
----
-name: ecom
-description: >
-  E-commerce department. Full store audits with 5 parallel agents (UX, SEO, performance,
-  content, conversion), product listing optimization, pricing strategy analysis, store launch
-  plans, e-commerce ad campaigns, competitor analysis, e-commerce SEO audits, automated email
-  flows (cart abandonment, post-purchase, win-back), and store performance reports. Integrates
-  with Shopify MCP for direct product/order/customer management. All output saved to Obsidian.
-  Use when user says "ecom", "store", "product", "shop", "shopify", "ecommerce", "e-commerce",
-  "sales", "conversion", "pricing", "catalog", "inventory", "cart", "checkout", "listing",
-  or any online store task.
----
-
-# E-commerce Department — ARKA OS
-
-Store management, product optimization, and e-commerce growth.
-
-## Universal Workflow (7-Phase — NON-NEGOTIABLE)
-
-Every e-commerce command follows this workflow. No exceptions. No shortcuts.
-
-### Phase 0: BRIEF (Ricardo)
-- Clarify the request: store data, objective, current metrics, constraints
-- Load store context via Shopify MCP or WebFetch
-- Save brief to Obsidian: `WizardingCode/Ecommerce/Briefs/BRIEF-<slug>.md`
-- **Gate:** Brief confirmed by user before proceeding
-
-### Phase 1: CHALLENGE & RESEARCH (Tomas — Strategy + Helena — CFO)
-- Tomas: market positioning, competitor analysis, strategic angle
-- Helena: financial viability, margin impact, ROI projection
-- Challenge assumptions: "Data shows X, are you sure about Y?"
-- Research benchmarks and competitor pricing
-- Present findings and alternatives to user
-- **Gate:** User approves the approach
-
-### Phase 2: PLANNING (Ricardo)
-- Define strategy with supporting data
-- Create TODO list with `TaskCreate` (one task per deliverable)
-- For pricing: define 3 scenarios (conservative, realistic, aggressive)
-- For products: define optimization priorities
-
-### Phase 3: EXECUTION (Ricardo)
-- Execute the approved plan
-- Product optimization: copy, SEO, variants, attributes
-- Pricing: competitor-informed, margin-validated
-- Tasks executed ONE AT A TIME, each validated before the next
-
-### Phase 4: SELF-CRITIQUE (Ricardo)
-- Do the data support the recommendations?
-- Are all product attributes correct for the category? (NO WiFi on shoes)
-- Are margins positive in all scenarios?
-- Does the copy follow human-writing standards?
-
-### Phase 5: SUPERVISION (Helena — CFO)
-- Financial impact review: margins, ROI, cash flow impact
-- Data validation: are the numbers correct and consistent?
-- **Gate:** Helena approves or sends back to Phase 3
-
-### Phase 6: QUALITY GATE (Marta — CQO)
-- Marta dispatches Eduardo (copy review) + Francisca (data/technical review)
-- Eduardo: product copy quality, descriptions, email campaigns
-- Francisca: data integrity (attributes match category), Shopify push validation, pricing consistency
-- Marta aggregates verdict:
-  - **APPROVED** → Proceed to Phase 7
-  - **REJECTED** → Exact issue list, return to Phase 3
-- **NO OUTPUT REACHES THE USER WITHOUT MARTA'S APPROVAL**
-
-### Phase 7: DELIVERY (Ricardo)
-- Apply via Shopify MCP (only if user approved push)
-- Save to Obsidian: `WizardingCode/Ecommerce/<type>/`
-- Report with before/after metrics where applicable
-- Report what was delivered vs. what was in the brief
-
-### Visibility (NON-NEGOTIABLE)
-Every phase transition is announced to the user:
-- "📋 Phase 0: Loading store context and creating brief..."
-- "🔍 Phase 1: Tomas and Helena challenging the approach..."
-- "💰 Phase 5: Helena reviewing financial impact..."
-- "🔒 Phase 6: Quality Gate — Eduardo + Francisca reviewing..."
-- "✅ Phase 6: APPROVED by Marta. Proceeding to delivery."
-
-## Commands
-
-| Command | Description |
-|---------|-------------|
-| `/ecom audit <url>` | Full store audit (5 agents) |
-| `/ecom product <description>` | Create optimized product listing |
-| `/ecom pricing <product>` | Pricing strategy analysis |
-| `/ecom launch <store>` | New store launch plan |
-| `/ecom ads <product>` | E-commerce ad campaigns |
-| `/ecom competitors <url>` | Competitive e-commerce analysis |
-| `/ecom seo <url>` | E-commerce SEO audit |
-| `/ecom email <type>` | E-commerce email flows (cart, post-purchase, win-back) |
-| `/ecom report <store>` | Store performance report |
-
-## Obsidian Output
-
-All e-commerce output goes to the Obsidian vault at `{{OBSIDIAN_VAULT}}`:
-
-| Content Type | Vault Path |
-|-------------|-----------|
-| Store audits | `WizardingCode/Ecommerce/Audits/<date> <store>.md` |
-| Product analyses | `WizardingCode/Ecommerce/Products/<name>.md` |
-| Competitor research | `WizardingCode/Ecommerce/Competitors/<date> <name>.md` |
-| Launch plans | `WizardingCode/Ecommerce/Launches/<store>.md` |
-| Performance reports | `WizardingCode/Ecommerce/Reports/<date> <store>.md` |
-
-**Obsidian format:**
-```markdown
----
-type: report
-department: ecommerce
-title: "<title>"
-date_created: <YYYY-MM-DD>
-tags:
-  - "report"
-  - "ecommerce"
-  - "<specific-tag>"
----
-```
-
-All files use wikilinks `[[]]` for cross-references and kebab-case tags.
-
-## Workflows
-
-### /ecom audit <url>
-
-**Step 1: Fetch Store Data**
-- Use WebFetch to crawl the store URL
-- Capture homepage, key product pages, cart, checkout flow
-
-**Step 2: Run 5 Parallel Audit Agents**
-
-Launch these agents simultaneously:
-
-**Agent 1: UX Auditor**
-- Navigation and information architecture
-- Mobile responsiveness
-- Page load perception
-- Cart and checkout friction
-- Search and filtering usability
-
-**Agent 2: SEO Auditor**
-- Title tags, meta descriptions, heading structure
-- Product page SEO (schema markup, alt text, URLs)
-- Internal linking and site structure
-- Collection/category page optimization
-- Technical SEO (canonical URLs, sitemap, robots.txt)
-
-**Agent 3: Performance Auditor**
-- Page load speed indicators
-- Image optimization assessment
-- Third-party script overhead
-- Core Web Vitals estimation
-- Mobile performance
-
-**Agent 4: Content Auditor**
-- Product descriptions (quality, length, persuasion)
-- Product photography assessment
-- Trust signals (reviews, badges, guarantees)
-- Brand consistency across pages
-- Copy effectiveness (headlines, CTAs)
-
-**Agent 5: Conversion Auditor**
-- Call-to-action clarity and placement
-- Social proof visibility
-- Urgency/scarcity elements
-- Upsell and cross-sell opportunities
-- Abandoned cart recovery signals
-- Email capture strategy
-
-**Step 3: Synthesize Results**
-- Combine all 5 agent reports
-- Prioritize findings by impact (high/medium/low)
-- Create actionable recommendations with estimated effort
-
-**Step 4: Save to Obsidian**
-
-**File:** `WizardingCode/Ecommerce/Audits/<YYYY-MM-DD> <store>.md`
-```markdown
----
-type: audit
-department: ecommerce
-title: "<store> — E-commerce Audit"
-url: "<url>"
-date_created: <YYYY-MM-DD>
-tags:
-  - "audit"
-  - "ecommerce"
----
-
-# <store> — E-commerce Audit
-
-## Executive Summary
-[Top 3-5 findings and overall score]
-
-## UX Analysis
-[Agent 1 findings]
-
-## SEO Analysis
-[Agent 2 findings]
-
-## Performance Analysis
-[Agent 3 findings]
-
-## Content Analysis
-[Agent 4 findings]
-
-## Conversion Analysis
-[Agent 5 findings]
-
-## Priority Actions
-| # | Action | Impact | Effort | Category |
-|---|--------|--------|--------|----------|
-| 1 | [action] | High | [effort] | [category] |
-
----
-*Part of the [[WizardingCode MOC]]*
-```
-
-**Step 5: Report**
-```
-═══ ARKA ECOM — Store Audit Complete ═══
-Store:       <store>
-URL:         <url>
-Issues:      <count> (High: X, Medium: Y, Low: Z)
-Top action:  <highest impact recommendation>
-Obsidian:    WizardingCode/Ecommerce/Audits/<date> <store>.md
-═════════════════════════════════════════
-```
-
-### /ecom product <description>
-
-**Step 1: Research**
-- Understand the product from the description
-- If URL provided, use WebFetch to analyze the current listing
-- If Shopify MCP available, pull existing product data
-
-**Step 2: Optimize Product Listing**
-- Title: SEO-optimized, keyword-rich, clear benefit
-- Description: Problem → Solution → Benefits → Features → CTA
-- Bullet points: Feature → Benefit format
-- SEO tags: Primary keyword, long-tail variants, related terms
-- Meta description: 155 chars, keyword-included, click-worthy
-
-**Step 3: Generate Variants**
-- 3 title options (SEO vs. emotional vs. benefit-led)
-- Short description (50 words) and long description (200+ words)
-- Suggested collections/categories
-- Cross-sell and upsell suggestions
-
-**Step 4: Save to Obsidian**
-
-**File:** `WizardingCode/Ecommerce/Products/<name>.md`
-```markdown
----
-type: product
-department: ecommerce
-title: "<product name>"
-date_created: <YYYY-MM-DD>
-tags:
-  - "product"
-  - "ecommerce"
----
-
-# <product name>
-
-## Optimized Listing
-### Title Options
-1. [SEO-focused]
-2. [Emotion-focused]
-3. [Benefit-focused]
-
-### Description
-[Optimized product description]
-
-### Bullet Points
-- [Feature → Benefit]
-
-### SEO
-- Primary keyword: [keyword]
-- Tags: [list]
-- Meta description: [155 chars]
-
-### Upsell/Cross-sell
-- [Suggestions]
-
----
-*Part of the [[WizardingCode MOC]]*
-```
-
-**Step 5: Apply via Shopify MCP**
-- If Shopify MCP is available and user confirms, push the optimized listing directly
-
-### /ecom pricing <product>
-
-**Step 1: Gather Product Data**
-- Current price (if exists)
-- Cost of goods / margin
-- Product category and positioning
-
-**Step 2: Competitor Analysis**
-- Use WebFetch to research 3-5 competitor prices for similar products
-- Map price range: budget → mid-range → premium
-
-**Step 3: Pricing Strategy**
-- Calculate margin at different price points
-- Apply psychological pricing (charm pricing, anchoring, decoy)
-- Consider bundling opportunities
-- Evaluate penetration vs. skimming strategy
-
-**Step 4: Generate Recommendation**
-
-**File:** `WizardingCode/Ecommerce/Products/<product>-pricing.md`
-```markdown
----
-type: pricing-analysis
-department: ecommerce
-title: "<product> — Pricing Strategy"
-date_created: <YYYY-MM-DD>
-tags:
-  - "pricing"
-  - "ecommerce"
----
-
-# <product> — Pricing Strategy
-
-## Competitor Landscape
-| Competitor | Product | Price | Positioning |
-|-----------|---------|-------|-------------|
-| [name] | [product] | [price] | [budget/mid/premium] |
-
-## Margin Analysis
-| Price Point | Margin | Margin % | Notes |
-|------------|--------|----------|-------|
-| [price] | [margin] | [%] | [note] |
-
-## Recommendation
-- **Recommended price:** [price]
-- **Strategy:** [penetration/skimming/competitive]
-- **Rationale:** [why this price wins]
-
-## Psychological Pricing
-- [Techniques to apply]
-
-## Bundle Opportunities
-- [Bundle suggestions with margin impact]
-
----
-*Part of the [[WizardingCode MOC]]*
-```
-
-## MCP Integration
-
-Uses Shopify MCP when available for:
-- Product management (get-products, get-collections)
-- Order management (get-orders, get-order)
-- Customer management (get-customers, tag-customer)
-- Discount creation (create-discount)
-- Store info (get-shop-details)
-
----
-*All output: `WizardingCode/Ecommerce/` — Part of the [[WizardingCode MOC]]*