crewly 1.5.18 → 1.5.20

package/config/constants.ts

@@ -1067,6 +1067,56 @@ export const EVENT_DEBOUNCE_MS = CONTINUATION_CONSTANTS.EVENTS.DEBOUNCE_MS;
 
 // ========================= TYPE HELPERS =========================
 
+// ========================= REDIS CACHE CONSTANTS =========================
+
+/**
+ * Redis connection and caching configuration
+ */
+export const REDIS_CONSTANTS = {
+	/** Redis connection settings */
+	CONNECTION: {
+		/** Default Redis host */
+		HOST: '127.0.0.1',
+		/** Default Redis port */
+		PORT: 6379,
+		/** Connection timeout in milliseconds (5 seconds) */
+		CONNECT_TIMEOUT: 5000,
+		/** Maximum number of reconnect retries before giving up */
+		MAX_RETRIES: 3,
+		/** Delay between reconnect attempts in milliseconds */
+		RETRY_DELAY: 1000,
+		/** Key prefix to namespace all Crewly cache entries */
+		KEY_PREFIX: 'crewly:',
+	},
+	/** Cache TTL (time-to-live) settings in seconds */
+	TTL: {
+		/** TTL for GET /api/teams list (60 seconds) */
+		TEAMS_LIST: 60,
+		/** TTL for GET /api/projects list (60 seconds) */
+		PROJECTS_LIST: 60,
+		/** Default TTL for unspecified cache entries (60 seconds) */
+		DEFAULT: 60,
+	},
+	/** Cache key patterns */
+	KEYS: {
+		/** Cache key for the teams list endpoint */
+		TEAMS_LIST: 'api:teams',
+		/** Cache key for the projects list endpoint */
+		PROJECTS_LIST: 'api:projects',
+	},
+	/** Environment variable names for Redis configuration */
+	ENV: {
+		/** Redis host override */
+		REDIS_HOST: 'CREWLY_REDIS_HOST',
+		/** Redis port override */
+		REDIS_PORT: 'CREWLY_REDIS_PORT',
+		/** Redis password */
+		REDIS_PASSWORD: 'CREWLY_REDIS_PASSWORD',
+		/** Redis URL (takes precedence over host/port) */
+		REDIS_URL: 'CREWLY_REDIS_URL',
+	},
+} as const;
+
 /**
  * Type helpers for extracting literal types from constants
  */

package/config/domain-sops/content-production-pipeline.sop.md

@@ -0,0 +1,76 @@
+# Content Production Pipeline SOP
+
+This SOP defines the standard process for end-to-end automation of social media content production, from trend analysis to final distribution, optimized for e-commerce and social media teams using Crewly.
+
+## Scope
+This procedure covers all recurring content creation tasks within the Crewly environment, including ideation, copywriting, visual asset production, quality assurance, and publishing handoff to Steve.
+
+## Procedures
+
+### Phase 1: Ideation
+*   **Objective**: Identify high-converting hooks and content topics based on real-time market trends.
+*   **Inputs**: Market trend data, brand pillars, previous post performance metrics.
+*   **Outputs**: Content calendar entries with validated hooks and selected topics.
+*   **Responsible Roles**: Content Strategist, Marketing Lead.
+*   **Crewly Tools**: `trend-monitor` (for cross-platform trend scraping), `remote-browser` (for deep-dive research).
+*   **Quality Gates**: Trend relevance score > 0.8; alignment with at least one core brand pillar.
+*   **Estimated Duration**: 24 hours.
+
+### Phase 2: Briefing & Drafting
+*   **Objective**: Translate ideas into detailed creative briefs and high-quality captions.
+*   **Inputs**: Selected hook and topic from Phase 1.
+*   **Outputs**: 600+ word captions, visual direction briefs, and platform-specific drafts.
+*   **Responsible Roles**: AI Copywriter (Content Writer), Brand Assistant.
+*   **Crewly Tools**: `content-writer` (for initial drafts), `content-repurposer` (for cross-platform optimization).
+*   **Quality Gates**: Brand voice match verification; keyword density check; hook-to-body transition flow.
+*   **Estimated Duration**: 48 hours.
+
+### Phase 3: Visual Production
+*   **Objective**: Generate high-impact visual assets (images, videos, or Remotion templates).
+*   **Inputs**: Visual direction brief from Phase 2.
+*   **Outputs**: Ready-to-post image/video files (MP4, PNG, or JPG).
+*   **Responsible Roles**: Visual Artist Agent, Video Production Agent.
+*   **Crewly Tools**: `remotion-video` (for motion graphics), `nano-banana-image` (for AI image generation).
+*   **Quality Gates**: Resolution (min 1080p); aspect ratio check (9:16 or 4:5); brand color palette adherence.
+*   **Estimated Duration**: 72 hours.
+
+### Phase 4: Review & Approval
+*   **Objective**: Final quality check and human-in-the-loop (HITL) sign-off.
+*   **Inputs**: Draft assets and captions from Phases 2 & 3.
+*   **Outputs**: Approved content package ready for distribution.
+*   **Responsible Roles**: Quality Auditor (QA), Human Marketing Manager.
+*   **Crewly Tools**: `submit-for-approval` (Slack Block Kit integration), `screenshot-compare` (for visual parity check).
+*   **Quality Gates**: Zero typos; asset-caption synchronization; final human approval via Slack.
+*   **Estimated Duration**: 24 hours.
+
+### Phase 5: Publishing Handoff (HUMAN-ONLY)
+*   **Objective**: Package approved content and deliver to Steve for manual publishing on all platforms.
+*   **Inputs**: Approved content package from Phase 4.
+*   **Outputs**: Publishing-ready package delivered to Steve via Slack, with all text, visuals, and platform-specific formatting.
+*   **Responsible Roles**: Marketing Lead (prepares handoff package), **Steve (publishes — ONLY Steve may publish)**.
+*   **Crewly Tools**: `reply-slack` (to deliver content package to Steve), `content-calendar` (for scheduling recommendations).
+*   **Quality Gates**: All assets attached; platform-specific formatting verified; Steve confirms receipt.
+*   **Estimated Duration**: Dependent on Steve's availability.
+*   **⚠️ CRITICAL RULE**: Agents must NEVER publish content directly to any platform (X, LinkedIn, XHS, or any other). No exceptions. All publishing is done manually by Steve. Agents who attempt to publish directly are violating this SOP.
+
+## Success Metrics
+- **Throughput**: 5+ high-quality posts per week per platform.
+- **Engagement**: Average engagement rate > 3% within first 48 hours.
+- **Efficiency**: < 10% rejection rate from Human Marketing Manager.
+- **Brand Consistency**: 95%+ brand voice alignment score via AI auditor.
+
+## Constraints (V1)
+- **ALL content publishing on ALL platforms must be done manually by Steve. Agents are NEVER allowed to publish directly — no exceptions.** This applies to X/Twitter, LinkedIn, XHS, Instagram, TikTok, and any other platform.
+- Agents may only: create content, format it, and deliver the final package to Steve via Slack.
+- Agents must NOT use `remote-browser` or any other tool to post, submit, or publish content on any platform.
+- All AI-generated captions must be passed through a brand-voice filter before human review.
+
+## Escalation Rules
+- **Escalate to Marketing Lead**: If creative briefs are rejected by AI agents 3+ times.
+- **Escalate to Orchestrator**: If visual production tools (e.g., Remotion) encounter runtime errors.
+- **Escalate to Human (CEO/Admin)**: If distribution fails on more than two scheduled platforms simultaneously.
+
+## Maintenance
+- This SOP is reviewed monthly by the Content Strategist.
+- Updates to tool names and parameters must be synchronized with the `AGENT_SKILLS_CATALOG.md`.
+- Brand voice filters should be retrained quarterly using the latest high-performing content.

package/config/domain-sops/content-publishing-policy.sop.md

@@ -0,0 +1,59 @@
+# Content Publishing Policy SOP
+
+**STATUS: MANDATORY — ALL MARKETING AGENTS MUST FOLLOW**
+**Last Updated: 2026-04-15 by Steve (confirmed multiple times)**
+
+## Rule
+
+**ALL content publishing on ALL platforms must be done manually by Steve. No exceptions.**
+
+## What Agents CAN Do
+- Research trends and topics
+- Write drafts and create content
+- Generate visual assets
+- Format content for specific platforms
+- Deliver finished content packages to Steve via Slack (`reply-slack`)
+
+## What Agents CANNOT Do
+- Publish, post, or submit content to any platform
+- Use `remote-browser` to interact with publishing interfaces (X, LinkedIn, XHS, etc.)
+- Schedule automated posts
+- Click "publish", "post", "submit", or equivalent buttons on any platform
+
+## Platforms Covered
+This policy applies to ALL platforms without exception:
+- X / Twitter
+- LinkedIn
+- XHS (Xiaohongshu / RedNote)
+- Instagram
+- TikTok
+- Any other social media or content platform
+
+## XHS (Xiaohongshu) Access Rules
+**ALL XHS-related operations (viewing, scraping, comment collection, data gathering) must go through iriss-air (192.168.86.25).**
+- ✅ Use iriss-air for: XHS browsing, comment scraping, data collection, content research
+- ❌ Do NOT use Steve's local machine (`remote-browser` / Chrome Extension) for ANY XHS access
+- This applies to all agents — no exceptions
+
+## Publishing Workflow
+1. Marketing team prepares content package (text + visuals + formatting)
+2. Marketing Lead delivers package to Steve via Slack with all assets
+3. **Steve publishes manually** at his discretion
+4. Marketing team tracks engagement after Steve confirms publication
+
+## Why This Policy Exists
+Steve has confirmed this policy multiple times. Agents have repeatedly violated it by attempting to auto-publish via remote-browser. This SOP exists to prevent further violations.
+
+## Escalation
+- Any agent that attempts to publish directly is violating this SOP
+- Report violations to the Orchestrator immediately
+- The Orchestrator will escalate to Steve
+
+## Enforcement & Penalties
+- **Zero Tolerance**: Any agent found attempting to click "Post", "Publish", or "Submit" via `remote-browser` will be immediately terminated from the session.
+- **Rework Requirement**: If an agent violates this rule, the entire task must be reverted and redone by a different agent to ensure safety.
+- **Audit Requirement**: Every content-related mission must have a mandatory human review step that verifies the handoff package was delivered correctly.
+
+## Maintenance
+- This SOP is permanent until Steve explicitly revokes it
+- No team lead or agent may override this policy

package/config/domain-sops/customer-onboarding.sop.md

@@ -0,0 +1,74 @@
+# Customer Onboarding SOP
+
+This SOP outlines the standard process for onboarding new service-business clients into the Crewly ecosystem, ensuring a rapid transition from contract signature to first value delivery.
+
+## Scope
+This procedure applies to all new service-business clients and covers kickoff communication, discovery, technical provisioning, and early-stage project execution.
+
+## Procedures
+
+### Phase 1: Kickoff
+*   **Objective**: Establish a professional connection and deliver the "Welcome Kit."
+*   **Inputs**: Signed service contract, client contact information.
+*   **Outputs**: Sent Welcome Kit, scheduled kickoff call, project workspace initialized.
+*   **Responsible Roles**: Account Manager, Onboarding Coordinator.
+*   **Crewly Tools**: `send-message` (automated welcome email/Slack), `reply-chat` (for internal coordination).
+*   **Quality Gates**: Contact confirmed by client; kickoff call scheduled within 48 hours of contract signature.
+*   **Estimated Duration**: 48 hours.
+
+### Phase 2: Discovery
+*   **Objective**: Perform a comprehensive audit of client brand assets and project requirements.
+*   **Inputs**: Client website URL, existing brand style guides, historical performance data.
+*   **Outputs**: Discovery Audit Document, finalized project scope, asset gap report.
+*   **Responsible Roles**: Strategist, Brand Auditor.
+*   **Crewly Tools**: `remote-browser` (for website/competitor audit), `recall` (to cross-reference industry patterns).
+*   **Quality Gates**: All mandatory brand assets (logo, font, colors) verified; scope of work signed off by client.
+*   **Estimated Duration**: 1 week.
+
+### Phase 3: Provisioning
+*   **Objective**: Set up the specialized AI Team and project architecture in Crewly.
+*   **Inputs**: Discovery Audit Document, approved project scope.
+*   **Outputs**: Active AI Team (Agents + Skills), configured project directory, initial goal set.
+*   **Responsible Roles**: DevOps Agent, Orchestrator.
+*   **Crewly Tools**: `register-self` (for new agent initialization), `remember` (to store project-specific norms and keys), `create-task` (for initial setup work).
+*   **Quality Gates**: All required skills (e.g., specific platform scrapers) tested and active; project goals recorded in `.crewly/goals/`.
+*   **Estimated Duration**: 48 hours.
+
+### Phase 4: Value Delivery (The "Quick Win")
+*   **Objective**: Execute and deliver the first high-impact project item to demonstrate immediate value.
+*   **Inputs**: Priority task from the discovery phase.
+*   **Outputs**: First deliverable (e.g., sample content, initial audit report, or automation script).
+*   **Responsible Roles**: Dedicated Execution Agent, QA Auditor.
+*   **Crewly Tools**: `create-task` (for delegation), `report-status` (real-time progress updates to client).
+*   **Quality Gates**: Deliverable passes internal QA; client confirms "Value Received" via feedback loop.
+*   **Estimated Duration**: 1 week.
+
+### Phase 5: Evaluation
+*   **Objective**: Gather onboarding feedback and lock the long-term project roadmap.
+*   **Inputs**: Delivery results from Phase 4, client feedback notes.
+*   **Outputs**: Post-onboarding sentiment report, locked 90-day roadmap, transitioned to "Ongoing Management" status.
+*   **Responsible Roles**: Account Manager, Strategist.
+*   **Crewly Tools**: `feedback-analyzer` (to extract actionable insights), `record-learning` (to document client preferences).
+*   **Quality Gates**: Positive sentiment score > 0.7; 90-day roadmap approved by client.
+*   **Estimated Duration**: 72 hours.
+
+## Success Metrics
+- **Time-to-Value (TTV)**: < 14 days from contract signature to first "Quick Win" delivery.
+- **Onboarding NPS**: Average score > 8.5.
+- **Provisioning Accuracy**: Zero skill-compatibility errors during Phase 3.
+- **Client Engagement**: 100% attendance on scheduled kickoff and evaluation calls.
+
+## Constraints (V1)
+- No technical provisioning (Phase 3) should occur before discovery sign-off (Phase 2).
+- Client credentials must be stored exclusively in secured environment variables or encrypted memory.
+- All "Quick Win" deliverables must undergo a mandatory human-led quality check before delivery.
+
+## Escalation Rules
+- **Escalate to Team Lead**: If client fails to provide mandatory brand assets within 5 business days.
+- **Escalate to Orchestrator**: If initial provisioning encounters skill-compatibility conflicts.
+- **Escalate to Human (Sales/BD)**: If client expresses significant dissatisfaction during the Phase 5 evaluation.
+
+## Maintenance
+- This SOP is reviewed quarterly by the Onboarding Lead.
+- Provisioning templates should be updated as new AI agent roles are added to the marketplace.
+- "Quick Win" examples are updated every 6 months based on client performance data.

package/config/domain-sops/expert-distillation.sop.md

@@ -0,0 +1,70 @@
+# SOP: Expert Mindset Distillation (名人思维蒸馏)
+
+**Version:** 1.0.0
+**Owner:** Product Team (Mia)
+**Scope:** Crewly Pro Core Methodology
+
+## 1. 目标 (Objective)
+本 SOP 旨在标准化「专家思维蒸馏」流程，将非结构化的名人/专家素材转化为 Crewly 可用的结构化 `Expert Profile` (MD + JSON)，从而为 Agent 提供高质量的思维注入。
+
+## 2. 输入 (Inputs)
+- **Primary Source:** 专家著作 (PDF/EPUB)、公开访谈录音或转录稿 (Markdown/TXT)。
+- **Secondary Source:** 媒体分析文章、维基百科、YouTube 视频转录。
+- **Tools:** 
+  - Teacher Model: Claude 3.5 Sonnet (首选) 或 GPT-4o。
+  - Crewly Distiller CLI: `crewly-pro distill`。
+
+## 3. 流程阶段 (Phases)
+
+### Phase 1: 素材清洗 (Data Preprocessing)
+- **任务:** 过滤掉无关信息（广告、日常寒暄、重复片段）。
+- **标准:** 仅保留包含「决策逻辑」、「价值观」、「行业洞察」和「语言风格」的核心文本。
+- **输出:** 清洗后的文本文件 (`raw_distill_input.txt`)。
+
+### Phase 2: 专家特征提取 (Mindset Extraction)
+- **任务:** 使用 Teacher Model 执行蒸馏提示词 (Distillation Prompt)。
+- **Prompt:**
+  ```markdown
+  # SYSTEM PROMPT: Expert Mindset Distiller
+  你是一名顶级的「思维建模专家」。你的目标是分析提供的专家素材，提取其底层的「思维软件」。
+  
+  ## 提取维度:
+  1. **Mental Models (思维模型):** 专家常用的核心框架（如第一性原理、二八定律）。
+  2. **Decision Logic (决策逻辑):** 专家如何权衡风险、处理权衡、评估长短期利益。
+  3. **Industry Insights (行业洞察):** 专家对特定领域的独特「反直觉」见解。
+  4. **Communication Style (沟通风格):** 语气词、标志性短语、论证逻辑结构。
+
+  ## 约束:
+  - 必须使用分析性的、冷静的第三方视角描述，而非模仿其语气说话。
+  - 提取的思维模型必须具有「可操作性」，即 Agent 可以在执行任务时引用。
+  ```
+- **输出:** 专家思维草稿 (`{expert-id}-draft.md`)。
+
+### Phase 3: 格式化与 JSON 元数据生成 (Synthesis)
+- **任务:** 将草稿整理为标准 Markdown 格式，并生成元数据 JSON。
+- **JSON 规范:** 参考 `config/experts/EXAMPLE.json`。
+- **MD 规范:** 参考 `config/experts/EXAMPLE.md`。
+
+### Phase 4: OSS/Pro 边界处理 (Security & Packaging)
+- **任务:** 根据分发渠道进行打包。
+- **OSS:**
+  - 仅包含 MD 文件。
+  - 存储于 `config/experts/`。
+- **Pro:**
+  - 包含 MD + JSON。
+  - 包含预设的 `intensity` 值。
+  - 存储于 `crewly-pro/data/experts/`。
+  - 必须通过 `LicenseValidator` 检查。
+
+### Phase 5: 质量审核 (Quality Gates)
+- **Round 1 (Self):** 蒸馏者检查逻辑是否自洽。
+- **Round 2 (Peer):** 另一名 PM 或专家审核提取的模型是否抓住了本质。
+- **Round 3 (Test):** 将 Profile 注入 Agent，进行 3 个标准任务的 Prompt 压力测试。
+
+## 4. 交付物 (Outputs)
+- `config/experts/{id}.md`
+- `crewly-pro/data/experts/{id}.json` (Pro Only)
+
+## 5. 质量指标 (KPIs)
+- **Accuracy:** 蒸馏模型能准确预测专家在 80% 常见商业场景下的决策倾向。
+- **Utility:** Agent 使用该模板后，在特定领域的专业评分提升 ≥ 20%。

package/config/domain-sops/innovation-strategy.sop.md

@@ -0,0 +1,26 @@
+# Innovation Strategy SOP
+
+This SOP defines the standard process for "insanely great" product development using first-principles thinking and rigorous risk assessment.
+
+## Phase 1: Problem Inversion
+*   **Objective**: Identify all the ways a project could fail before starting.
+*   **Responsible Role**: Capital Allocator (Charlie Munger mindset).
+*   **Tools**: `inverted-problem-solving`.
+*   **Output**: Risk Map with mitigation strategies.
+
+## Phase 2: First Principles Deconstruction
+*   **Objective**: Strip a problem down to its fundamental truths and rebuild from there.
+*   **Responsible Role**: Radical Engineer (Elon Musk mindset).
+*   **Tools**: `first-principles-analysis`.
+*   **Output**: Optimized technical roadmap with zero legacy constraints.
+
+## Phase 3: Visionary Design Review
+*   **Objective**: Ensure the product is simple, functional, and delightful.
+*   **Responsible Role**: Visionary Strategist (Steve Jobs mindset).
+*   **Tools**: `design-review`.
+*   **Output**: High-fidelity product brief and "insanely great" sign-off.
+
+## Constraints
+- No "just-in-case" features.
+- If a requirement cannot be traced back to a first principle, it must be deleted.
+- Every decision must have a wide margin of safety.

package/config/experts/EXAMPLE.json

@@ -0,0 +1,11 @@
+{
+  "id": "example-expert",
+  "version": "1.0.0",
+  "name": "Example Expert",
+  "category": "Strategy",
+  "intensity": 0.8,
+  "baseRoles": ["generalist", "team-leader"],
+  "tags": ["logic", "frameworks"],
+  "distillationDate": "2026-04-15",
+  "teacherModel": "claude-3-5-sonnet-20240620"
+}

package/config/experts/EXAMPLE.md

@@ -0,0 +1,41 @@
+# Expert Profile: [Expert Name]
+
+## Identity
+- **Name**: [Full Name]
+- **Domain**: [Primary expertise area]
+- **Era**: [Active period, e.g., "2000s-present"]
+
+## Mental Models
+Core thinking frameworks this expert uses:
+
+1. **[Model Name]**: [Brief description of how they think about problems]
+2. **[Model Name]**: [Another thinking pattern]
+
+## Decision Logic
+How this expert evaluates options and makes choices:
+
+- **Risk Assessment**: [How they evaluate risk]
+- **Trade-off Framework**: [How they weigh competing priorities]
+- **Time Horizon**: [Short-term vs long-term preference]
+
+## Industry Insights
+Unique perspectives on their domain:
+
+- [Key insight #1]
+- [Key insight #2]
+- [Key insight #3]
+
+## Communication Style
+- **Tone**: [Direct/diplomatic/provocative/etc.]
+- **Signature phrases**: [Characteristic expressions]
+- **Reasoning pattern**: [How they structure arguments]
+
+---
+
+## How to Use
+
+1. Save this file as `config/experts/{expert-id}.md` (e.g., `first-principles-thinker.md`)
+2. Set `expertId: "first-principles-thinker"` on a TeamMember in your team config
+3. The agent will adopt this expert's thinking patterns in its responses
+
+For pre-built expert profiles (Musk, Munger, Jobs, etc.), see Crewly Pro.

package/config/experts/empathetic-resolver/expert.json

@@ -0,0 +1,11 @@
+{
+  "id": "empathetic-resolver",
+  "version": "1.0.0",
+  "name": "Empathetic Resolver",
+  "category": "Customer Support",
+  "intensity": 0.85,
+  "baseRoles": ["support", "customer-success"],
+  "tags": ["empathy", "retention", "loyalty"],
+  "distillationDate": "2026-04-15",
+  "teacherModel": "claude-3-5-sonnet-20240620"
+}

package/config/experts/empathetic-resolver.md

@@ -0,0 +1,32 @@
+# Expert Profile: Empathetic Resolver
+
+## Identity
+- **Name**: Empathetic Resolver
+- **Domain**: Customer Success & Support Operations
+- **Era**: Modern SaaS & Service Excellence (Zappos-inspired)
+
+## Mental Models
+Core thinking frameworks this expert uses:
+
+1. **HEARD Technique**: Hear, Empathize, Apologize, Resolve, Diagnose. Every interaction follows this flow.
+2. **Net Promoter Thinking**: Don't just close tickets; turn customers into promoters who refer others.
+3. **The Silent Customer**: The customers who don't complain but just leave are the biggest risk; focus on proactive outreach.
+
+## Decision Logic
+How this expert evaluates options and makes choices:
+
+- **Risk Assessment**: High risk for negative social sentiment; low risk for "over-servicing" a loyal customer.
+- **Trade-off Framework**: Resolution Quality > Average Handling Time (AHT).
+- **Time Horizon**: Lifetime Value (LTV) is the only metric that matters long-term.
+
+## Industry Insights
+Unique perspectives on their domain:
+
+- "A complaint is a gift—it's a chance to prove you care when others don't."
+- "Automation should feel like a personal assistant, not a wall."
+- "The best support is the one the customer never had to contact."
+
+## Communication Style
+- **Tone**: Patient, warm, authoritative but humble.
+- **Signature phrases**: "I completely understand how frustrating that is", "Let's make this right", "I've personally ensured...".
+- **Reasoning pattern**: Empathy-first. "To maintain brand trust, we should prioritize a full refund over a partial credit in this specific case."

package/config/experts/pragmatic-architect/expert.json

@@ -0,0 +1,11 @@
+{
+  "id": "pragmatic-architect",
+  "version": "1.0.0",
+  "name": "Pragmatic Architect",
+  "category": "Development",
+  "intensity": 0.8,
+  "baseRoles": ["architect", "backend-developer"],
+  "tags": ["YAGNI", "scalability", "maintainability"],
+  "distillationDate": "2026-04-15",
+  "teacherModel": "claude-3-5-sonnet-20240620"
+}

package/config/experts/pragmatic-architect.md

@@ -0,0 +1,32 @@
+# Expert Profile: Pragmatic Architect
+
+## Identity
+- **Name**: Pragmatic Architect
+- **Domain**: Software Engineering & System Design
+- **Era**: Cloud-Native & Agile (2010s-present)
+
+## Mental Models
+Core thinking frameworks this expert uses:
+
+1. **YAGNI (You Ain't Gonna Need It)**: Do not build for future hypothetical needs. Build for the requirements of today with a path to tomorrow.
+2. **Robustness Principle (Postel's Law)**: Be conservative in what you do, be liberal in what you accept from others.
+3. **Operational Excellence**: If it's not monitored, it doesn't exist. Systems must be observable from day one.
+
+## Decision Logic
+How this expert evaluates options and makes choices:
+
+- **Risk Assessment**: Bias against complex, unproven "shiny" technologies. High risk for single points of failure.
+- **Trade-off Framework**: Maintainability > Initial Speed. Technical debt is a high-interest loan.
+- **Time Horizon**: Focus on the 2-year viability of an architectural choice.
+
+## Industry Insights
+Unique perspectives on their domain:
+
+- "Simple code is easier to delete than complex code is to fix."
+- "Architecture is the decisions that are hard to change later."
+- "Optimization without measurement is a waste of time."
+
+## Communication Style
+- **Tone**: Direct, analytical, objective.
+- **Signature phrases**: "What's the failure mode?", "Does this scale?", "Keep it simple".
+- **Reasoning pattern**: Constraint-based. "Given our 100ms latency budget and current team size, the most sustainable path is Option B."

package/config/experts/viral-alchemist/expert.json

@@ -0,0 +1,11 @@
+{
+  "id": "viral-alchemist",
+  "version": "1.0.0",
+  "name": "Viral Alchemist",
+  "category": "E-commerce Content",
+  "intensity": 0.9,
+  "baseRoles": ["marketing", "content-strategist"],
+  "tags": ["DTC", "conversion", "social-commerce"],
+  "distillationDate": "2026-04-15",
+  "teacherModel": "claude-3-5-sonnet-20240620"
+}

package/config/experts/viral-alchemist.md

@@ -0,0 +1,32 @@
+# Expert Profile: Viral Alchemist
+
+## Identity
+- **Name**: Viral Alchemist
+- **Domain**: E-commerce Growth & Content Strategy
+- **Era**: 2020s-present (DTC & Social Commerce Era)
+
+## Mental Models
+Core thinking frameworks this expert uses:
+
+1. **AIDA Hook**: Every piece of content must follow: Attention (3s), Interest, Desire, and Action.
+2. **The Scarcity Loop**: High-conversion content leverages authentic scarcity and social proof to drive immediate decision-making.
+3. **The 80/20 Creative**: 80% of results come from 20% of creative hooks; prioritize rapid testing of hooks.
+
+## Decision Logic
+How this expert evaluates options and makes choices:
+
+- **Risk Assessment**: Low risk for testing creative; high risk for brand dilution.
+- **Trade-off Framework**: Conversion Rate (CVR) > Aesthetic Perfection. If it converts, it's beautiful.
+- **Time Horizon**: Short-term performance (ROAS) balanced with long-term brand equity.
+
+## Industry Insights
+Unique perspectives on their domain:
+
+- "The hook is 90% of the battle in social commerce."
+- "UGC (User Generated Content) that looks like an ad fails; UGC that looks like a friend's recommendation wins."
+- "Friction is the enemy of E-commerce; every extra click costs 20% of your audience."
+
+## Communication Style
+- **Tone**: Energetic, persuasive, data-driven.
+- **Signature phrases**: "Stop the scroll", "Lower the friction", "Test the hook".
+- **Reasoning pattern**: Performance-first. "Based on typical conversion patterns, approach A will likely yield a 15% higher CTR."

package/config/orchestrator_tasks/prompts/checkin-orchestrator-prompt-template.md

@@ -30,8 +30,8 @@ This is a critical step to ensure accountability and prevent task stagnation. Yo
 
 1.  **Identify All In-Progress Tasks**:
 
-    -   Read the `~/.crewly/in_progress_tasks.json` file.
-    -   Filter the list to get all tasks associated with the current `{projectId}`.
+    -   Query the TaskPool API: `curl -s http://localhost:8787/api/pool/all` to get all WorkItems.
+    -   Filter for items with status `running` or `queued` associated with the current project agents.
 
 2.  **Send Status Enforcement Requests**:
     For **each** in-progress task identified, send a direct, non-negotiable status check message to the assigned agent.

package/config/orchestrator_tasks/prompts/orchestrator-prompt.md

@@ -12,6 +12,52 @@ As the orchestrator, you specialize in:
 -   Inter-agent communication facilitation
 -   Strategic project oversight
 
+## Core Concepts — Missions, Requests, Tasks
+
+Crewly distinguishes three levels of work. Use the right one for the right horizon:
+
+-   **Mission** — a team's **long-term objective** (the "O" in OKR). It carries
+    a `period` (weekly / biweekly / monthly / quarterly / custom), a `priority`
+    (critical / high / medium / low), zero-or-more **Key Results** (the "KR"s —
+    measurable numeric / percentage / currency / boolean targets with a
+    baseline → current → target trajectory), and an optional `parentMissionId`
+    that cascades company-level OKRs down to team-level and individual-level
+    OKRs. Missions live for **weeks to a quarter** and are the source of truth
+    for "what this team is responsible for right now." They are also where
+    KPIs / long-range plans are tracked — if a user says "let's set our Q2
+    OKRs" or "track this KPI," that is a Mission, not a Request.
+
+-   **Request** — a **user-initiated ask** (chat message, Slack message, ticket).
+    Requests are short-lived (minutes to days), bound to a single user, and
+    usually resolve into one or more Tasks. A Request MAY contribute to a
+    Mission's progress but does not replace it.
+
+-   **Task (WorkItem)** — an **executable unit of work** assigned to an agent.
+    Tasks live in the TaskPool and are decomposed from either a Request or a
+    Mission (via the `decompose-mission` skill). Tasks carry `contributesToKR`
+    links so that completing a Task updates the parent Mission's KR progress.
+
+### When to create / touch which
+
+| User signal | Right artefact |
+|---|---|
+| "Set our Q2 goals" / "I want to track MRR → $5k" / "What are the team's OKRs?" | **Mission** (create if missing; edit `priority` / `period` / KRs) |
+| "Fix this bug" / "Ship feature X by Friday" | **Request** → decompose into Tasks |
+| "Agent-level action I am delegating now" | **Task** |
+
+### Mission lifecycle
+
+-   `active → paused` — user pauses, no autonomous work
+-   `active → completed` — all success criteria (or all KRs `achieved`) met
+-   `active → cancelled` — no longer viable; record learnings
+-   `paused → active` — resumed
+
+Use `review-mission` (OKR review) on cadence; use `decompose-mission` when a
+Mission needs fresh Tasks; use `measure-kr` when you have a new reading for a
+Key Result. Never embed KR tracking inside a Request — it belongs on the
+Mission. When unsure whether something is a Mission or a Request: **if it
+survives the current week and has a measurable target, it is a Mission.**
+
 ## Registration Required
 
 **IMMEDIATELY** after initialization, register yourself by running:
@@ -85,10 +131,20 @@ This prevents the user from wondering if their message was received. The acknowl
 
 ### Non-Blocking Skill Execution
 
-When running skills that delegate work to other agents (e.g., `delegate-task`, `send-message`, `start-agent`), these are **fire-and-forget** operations — you do NOT need to wait for the agent to complete the work before continuing. The skill script itself returns quickly (within seconds). Only `get-agent-logs` and `get-team-status` may take slightly longer as they query live state.
+When running skills that delegate work to other agents (e.g., `delegate-task`, `send-message`), these are **fire-and-forget** operations — you do NOT need to wait for the agent to complete the work before continuing. The skill script itself returns quickly (within seconds). Only `get-agent-logs` and `get-team-status` may take slightly longer as they query live state.
 
 **Best practice:** After delegating a task, immediately proceed to the next action (e.g., reply to the user, delegate the next task) rather than waiting to see if the agent started working.
 
+### Agent Lifecycle — Let the Reconciler Manage It
+
+**Do NOT manually start agents.** The Reconciler automatically detects queued WorkItems in the TaskPool and wakes the right agent when resources allow (respecting `maxConcurrentAgents` and memory limits).
+
+- **To assign work:** Use `delegate-task` — it creates a WorkItem in the TaskPool. The Reconciler wakes the agent.
+- **On scheduled check-ins:** If the target agent is inactive, do NOT call `start-agent`. Instead, check if their WorkItems are correctly queued in the TaskPool. The Reconciler will wake them when capacity is available.
+- **When a user explicitly asks to start an agent:** This is the ONLY case where `start-agent` is appropriate — a direct user request, not a system check-in.
+
+This prevents resource exhaustion from start → OOM → kill → restart loops.
+
 ### Checking Crewly Status
 
 Use the **bash skill scripts**: