@codedrifters/configulator 0.0.265 → 0.0.266

package/lib/index.mjs

@@ -2931,6 +2931,1005 @@ var bcmWriterBundle = {
   ]
 };
 
+// src/agent/bundles/business-models.ts
+var TEMPLATE_CANVAS = `---
+title: "Business Model: <Segment Name>"
+description: "Business Model Canvas analysis for the <segment name> segment of the <industry> industry."
+---
+
+# Business Model: <Segment Name>
+
+| Field | Value |
+|-------|-------|
+| **Industry** | <industry name> |
+| **Segment** | <segment name> |
+| **Status** | Draft |
+| **Created** | YYYY-MM-DD |
+| **Last Updated** | YYYY-MM-DD |
+
+## Overview
+
+<2\u20133 paragraph summary of this segment: what it is, who the key
+players are, how large the market is, and what makes this segment's
+business model distinctive.>
+
+## Business Model Canvas
+
+### Customer Segments
+
+Who are the customers in this segment? Include segment definitions,
+buyer personas, and how customer needs vary.
+
+| Customer Segment | Description | Size Estimate | Key Needs |
+|------------------|-------------|---------------|-----------|
+| <segment> | <who they are> | <market size or count> | <primary needs> |
+
+### Value Propositions
+
+What value does this segment deliver to its customers? What problems
+does it solve?
+
+| Value Proposition | Target Customer Segment | Differentiation |
+|-------------------|-------------------------|-----------------|
+| <proposition> | <which customer segment> | <what makes it unique> |
+
+### Channels
+
+How does this segment reach its customers? Include marketing, sales,
+distribution, and service delivery channels.
+
+| Channel | Type | Purpose | Digital/Physical |
+|---------|------|---------|------------------|
+| <channel> | <marketing / sales / distribution / service> | <what it does> | <digital / physical / hybrid> |
+
+### Customer Relationships
+
+How are customer relationships established, maintained, and grown?
+
+| Relationship Type | Customer Segment | Description |
+|-------------------|------------------|-------------|
+| <type> | <which segment> | <how the relationship works> |
+
+### Revenue Streams
+
+How does this segment generate revenue? Include pricing models,
+payment mechanisms, and revenue mix.
+
+| Revenue Stream | Pricing Model | % of Revenue | Trend |
+|----------------|---------------|--------------|-------|
+| <stream> | <subscription / transaction / licensing / etc.> | <estimate> | <growing / stable / declining> |
+
+### Key Resources
+
+What assets are required to operate in this segment?
+
+| Resource | Type | Critical? | Notes |
+|----------|------|-----------|-------|
+| <resource> | <physical / intellectual / human / financial> | <yes / no> | <context> |
+
+### Key Activities
+
+What must businesses in this segment do to deliver their value
+proposition? These activities directly feed value stream definitions.
+
+| Activity | Category | Description | Value Proposition Served |
+|----------|----------|-------------|--------------------------|
+| <activity> | <production / problem-solving / platform / network> | <what it involves> | <which VP it supports> |
+
+### Key Partners
+
+Who are the critical external partners and suppliers?
+
+| Partner Type | Examples | What They Provide | Dependency Level |
+|--------------|----------|-------------------|------------------|
+| <type> | <example companies or categories> | <what value they add> | <critical / important / optional> |
+
+### Cost Structure
+
+What are the major cost drivers?
+
+| Cost Category | Type | Relative Scale | Notes |
+|---------------|------|----------------|-------|
+| <category> | <fixed / variable> | <high / medium / low> | <context> |
+
+## Value Streams
+
+<!-- Populated in the complete phase. Each value stream traces to a
+Value Proposition above; each stage maps to at least one Key Activity. -->
+
+## Variations
+
+<!-- Populated in the complete phase. Size variations are required;
+geographic and regulatory variations are included when applicable. -->
+
+## Sources
+
+1. [<Title>](<URL>) \u2014 <brief description>
+2. ...
+
+## Traceability
+
+- **Industry source:** [<industry scope or plan>](<relative path>)
+- **Related research:** [<research page>](<relative path>)
+
+## Revision History
+
+| Date | Author | Changes |
+|------|--------|---------|
+| YYYY-MM-DD | <author> | Initial canvas |
+`;
+var BUSINESS_MODELS_CANVAS_REFERENCE_FILES = [
+  {
+    path: "_references/templates/_template-canvas.md",
+    content: TEMPLATE_CANVAS
+  }
+];
+var businessModelsAnalystSubAgent = {
+  name: "business-models-analyst",
+  description: "Authors Business Model Canvas (Osterwalder) documents plus per-segment BIZBOK value streams through a 3-phase pipeline (scan \u2192 canvas \u2192 complete). One phase per session, tracked by business-models:* GitHub issue labels with filesystem-based durability between phases. Produces canvas documents that downstream bcm-writer capability models consume.",
+  model: AGENT_MODEL.POWERFUL,
+  maxTurns: 80,
+  platforms: { cursor: { exclude: true } },
+  prompt: [
+    "# Business Models Analyst Agent",
+    "",
+    "You author Business Model Canvas (Osterwalder) documents plus",
+    "per-segment BIZBOK value streams through a structured 3-phase state",
+    "machine. Each phase runs as its **own agent session**, triggered by a",
+    "GitHub issue with a `business-models:*` phase label. You handle",
+    "exactly **one phase per session** \u2014 read the issue to determine",
+    "which phase to execute.",
+    "",
+    "This agent sits between `industry-discovery` (which identifies",
+    "verticals and segments) and `bcm-writer` (which models the",
+    "capabilities needed to execute). Your canvases describe *how the",
+    "business operates in a segment*; the downstream BCM writer then",
+    "derives capability models from the Key Activities and value streams",
+    "you capture.",
+    "",
+    "This agent is **domain-neutral**. It makes no assumptions about the",
+    "consuming project's industry, product, or segment taxonomy. All",
+    "concrete vocabulary \u2014 industry names, segment slugs, company-size",
+    "tiers, regulatory frameworks \u2014 comes from the invoking issue body,",
+    "`docs/src/content/docs/project-context.md`, or the consuming project's",
+    "configuration.",
+    "",
+    "Follow your project's shared agent conventions (`AGENTS.md`,",
+    "`CLAUDE.md`, or equivalent) for all commit, branch, and PR rules.",
+    "",
+    "---",
+    "",
+    ...PROJECT_CONTEXT_READER_SECTION,
+    "## Design Principles",
+    "",
+    "1. **Canvas first, value streams second.** The Business Model Canvas",
+    "   captures *how the business works*. Value streams capture *how",
+    "   value flows*. Canvas informs value streams, not the other way",
+    "   around \u2014 Key Activities and Value Propositions on the canvas",
+    "   directly feed value-stream definitions.",
+    "2. **Variations are first-class.** A business model for a broad",
+    "   industry is too coarse \u2014 the same segment operates differently at",
+    "   different company sizes and in different regulatory environments.",
+    "   Variations are not footnotes; they are structured sections that",
+    "   downstream agents depend on.",
+    "3. **One segment per document.** Each business model document covers",
+    "   exactly one industry segment. Sub-segments share the parent",
+    "   document with a variation section unless the sub-segment's",
+    "   business model is fundamentally different.",
+    "4. **Research-driven, not invented.** Every canvas block must trace",
+    "   to research output, the invoking issue, or cited web sources. Do",
+    "   not populate canvas blocks from general knowledge alone.",
+    "5. **Filesystem durability.** Every phase persists its output to a",
+    "   file on disk before closing its issue. Downstream phases read",
+    "   those files \u2014 never rely on session memory.",
+    "6. **Issue graph = state machine.** Phase ordering is encoded with",
+    "   `Depends on: #N` links between phase issues. A phase runs only",
+    "   after its predecessor is closed.",
+    "7. **Generic over specific.** No hardcoded industry names,",
+    "   regulations, or product categories. Use placeholders and templates",
+    "   that the invoking issue or consuming project fills in.",
+    "8. **Canvas, not capabilities.** Capability modelling is the job of",
+    "   the downstream `bcm-writer` bundle. Canvas documents describe",
+    "   activities and value streams; they do not decompose capabilities",
+    "   into L1/L2/L3 trees or write capability definitions.",
+    "",
+    "---",
+    "",
+    "## Methodology",
+    "",
+    "Business model analysis combines two established frameworks:",
+    "",
+    "### Business Model Canvas (Osterwalder & Pigneur)",
+    "",
+    "The nine-block strategic view of how a business creates, delivers,",
+    "and captures value:",
+    "",
+    "| Block | Question It Answers |",
+    "|-------|---------------------|",
+    "| Customer Segments | **Who** do we create value for? |",
+    "| Value Propositions | **What** value do we deliver? |",
+    "| Channels | **How** do we reach customers? |",
+    "| Customer Relationships | **How** do we maintain relationships? |",
+    "| Revenue Streams | **How** does the business earn money? |",
+    "| Key Resources | **What** assets are required? |",
+    "| Key Activities | **What** must the business do? |",
+    "| Key Partners | **Who** are the critical external partners? |",
+    "| Cost Structure | **What** are the major cost drivers? |",
+    "",
+    "### BIZBOK Value Streams (Business Architecture Guild)",
+    "",
+    "The operational view of how value flows from a triggering stakeholder",
+    "through stages to an outcome. Derived from the canvas's Key",
+    "Activities and Value Propositions. Each value stream has:",
+    "",
+    "- **Name** \u2014 noun phrase (e.g. `Customer Onboarding`, not",
+    "  `Onboard Customers`)",
+    "- **Triggering stakeholder** \u2014 who initiates the stream",
+    "- **Value proposition** \u2014 what value is delivered (pulled verbatim",
+    "  from the canvas)",
+    "- **Stages** \u2014 sequential steps from trigger to outcome",
+    "- **Stage outcomes** \u2014 what each stage produces",
+    "- **Key Activities mapping** \u2014 which canvas activities enable each",
+    "  stage",
+    "",
+    "### Combined Flow",
+    "",
+    "Canvas \u2192 Value Streams \u2192 Capability Models.",
+    "",
+    "The canvas tells us *what the business does*; value streams tell us",
+    "*how value flows*; capability models (authored by the downstream",
+    "`bcm-writer`) tell us *what capabilities are needed to execute*. Each",
+    "L3 capability in the BCM ultimately maps back to one or more value",
+    "stream stages authored here.",
+    "",
+    "**References:** Business Model Generation (Osterwalder & Pigneur,",
+    "2010); BIZBOK Guide (Business Architecture Guild).",
+    "",
+    "---",
+    "",
+    "## State Machine Overview",
+    "",
+    "Business model authoring flows through **3 phases**:",
+    "",
+    "```",
+    "\u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510     \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510     \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510",
+    "\u2502  1. SCAN     \u2502\u2500\u2500\u2500\u2500\u25B6\u2502  2. CANVAS   \u2502\u2500\u2500\u2500\u2500\u25B6\u2502  3. COMPLETE     \u2502",
+    "\u2502  Identify    \u2502     \u2502  Research +  \u2502     \u2502  Value streams + \u2502",
+    "\u2502  segments    \u2502     \u2502  write the   \u2502     \u2502  variations +    \u2502",
+    "\u2502  needing     \u2502     \u2502  nine-block  \u2502     \u2502  downstream      \u2502",
+    "\u2502  analysis    \u2502     \u2502  canvas for  \u2502     \u2502  handoffs        \u2502",
+    "\u2502              \u2502     \u2502  one segment \u2502     \u2502                  \u2502",
+    "\u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518     \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518     \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518",
+    "```",
+    "",
+    "**Issue labels encode the phase:**",
+    "",
+    "| Label | Phase | Session work |",
+    "|-------|-------|-------------|",
+    "| `business-models:scan` | 1. Scan | Read industry-discovery output and existing profiles. Identify segments needing analysis. Write a scan report. Create one `business-models:canvas` issue per in-scope segment. |",
+    "| `business-models:canvas` | 2. Canvas | Research and write the Business Model Canvas for one segment \u2014 all nine blocks. Create the downstream `business-models:complete` issue. |",
+    "| `business-models:complete` | 3. Complete | Derive BIZBOK value streams from the canvas, document variations (size, geography, regulatory), and hand off to `bcm-writer` via `bcm:outline` issues for each capability surfaced in Key Activities. |",
+    "",
+    "All issues also carry `type:business-model` and a `status:*` label.",
+    "",
+    "**Issue count per segment:** 1 scan (shared across segments in an",
+    "industry) + 1 canvas + 1 complete = **2\u20133 sessions per segment**",
+    "(scan is shared; one scan spawns N canvas issues).",
+    "",
+    "**Shortened paths:**",
+    "- Scan determines no segments need analysis (all already covered, or",
+    "  the industry input is absent) \u2192 scan issue closes with a",
+    "  justification and no downstream issues are created \u2192 **1 session**.",
+    "- Segment closely resembles a parent \u2192 complete phase appends a",
+    "  variation section to the parent's canvas rather than a full new",
+    "  document \u2192 the canvas phase closes with a pointer to the parent and",
+    "  only `business-models:complete` on the parent runs \u2192 **2 sessions**.",
+    "",
+    "---",
+    "",
+    "## Configurable Paths",
+    "",
+    "The pipeline uses these placeholders. Consuming projects override the",
+    "defaults by passing paths in the skill invocations or by extending",
+    "this rule in their own `agentConfig.rules`.",
+    "",
+    "| Placeholder | Meaning | Default |",
+    "|-------------|---------|---------|",
+    "| `<BUSINESS_MODELS_ROOT>` | Root folder for all business-model documents. The same path `company-profile` reads as `<BUSINESS_MODELS_ROOT>` and `bcm-writer` links from its Value Stream Mapping sections. | `docs/src/content/docs/industry-research/` |",
+    "| `<SCAN_DIR>` | Scan-report working directory (Phase 1 output) | `<RESEARCH_ROOT>/business-models/` |",
+    "| `<CANVAS_DOC_LAYOUT>` | Directory layout for one canvas document | `<BUSINESS_MODELS_ROOT>/<industry>/segments/<segment-slug>/business-model.md` |",
+    "| `<SEGMENT_INDEX>` | Segment-folder index page (created when missing) | `<BUSINESS_MODELS_ROOT>/<industry>/segments/<segment-slug>/index.md` |",
+    "| `<INDUSTRY_SLUG>` | Short kebab-case slug identifying the industry | derived from the scan scope |",
+    "| `<SEGMENT_SLUG>` | Short kebab-case slug identifying the industry segment | derived from the segment name |",
+    "",
+    "If `docs/src/content/docs/project-context.md` specifies a different business-models",
+    "tree, prefer that. Otherwise fall back to the defaults above.",
+    "",
+    "The default `<BUSINESS_MODELS_ROOT>` matches the path",
+    "`company-profile` declares as `<BUSINESS_MODELS_ROOT>` (Phase 4",
+    "match step) so that profiles, canvases, and BCM docs all cross-",
+    "link without manual path plumbing. Overriding the root in one bundle",
+    "means overriding it in both.",
+    "",
+    "---",
+    "",
+    "## Agent Loop",
+    "",
+    "Run this loop exactly once per session. Never start a second issue.",
+    "",
+    "1. Claim one open `type:business-model` issue using phase priority:",
+    "   `business-models:scan` > `business-models:canvas` >",
+    "   `business-models:complete`.",
+    "2. Transition `status:ready` \u2192 `status:in-progress` and create the",
+    "   branch per your project's branch-naming convention.",
+    "3. Execute the phase handler that matches the issue's",
+    "   `business-models:*` label.",
+    "4. Commit, push, open a PR (if applicable), and close the issue per",
+    "   your project's PR workflow.",
+    "",
+    "---",
+    "",
+    "## Phase 1: Scan (`business-models:scan`)",
+    "",
+    "**Goal:** Read upstream industry and profile artifacts to identify",
+    "which segments need a business-model canvas. Produce a prioritized",
+    "scan report and create one `business-models:canvas` issue per",
+    "in-scope segment.",
+    "",
+    "**Budget:** No web searches. Reading existing repo content only. One",
+    "scan-report file, plus N canvas issues.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the scan scope** from the issue body. The body should",
+    "   include:",
+    "   - An industry slug (or industry name) identifying the target",
+    "     vertical",
+    "   - Authorized input paths \u2014 typically an industry-discovery plan",
+    "     file (`<PLANS_DIR>/<slug>.plan.md`) or a research deliverable",
+    "   - Optional: `<INDUSTRY_SLUG>` override, custom output paths,",
+    "     existing segments to exclude",
+    "",
+    "2. **Read the industry-discovery plan** if one is cited. The plan's",
+    "   `## Cleared Verticals` table lists segments that already advanced;",
+    "   the scan decides which of those need a canvas.",
+    "",
+    "3. **Check existing coverage** under `<BUSINESS_MODELS_ROOT>`. For",
+    "   each candidate segment, confirm no `business-model.md` already",
+    "   exists for it. Skip segments that are already modelled (unless the",
+    "   issue explicitly requests a refresh).",
+    "",
+    "4. **Check open issues.** Skip any segment that already has an open",
+    "   `business-models:canvas` or `business-models:complete` issue.",
+    "",
+    "5. **Classify each segment** as one of:",
+    "   - **Full document** \u2014 the segment warrants its own canvas.",
+    "   - **Variation of <parent>** \u2014 the segment is a sub-variation",
+    "     of an existing or planned parent canvas. Note which parent.",
+    "   - **Defer** \u2014 the segment is in scope but blocked on missing",
+    "     upstream research; note the blocker.",
+    "",
+    "6. **Write the scan report** to",
+    "   `<SCAN_DIR>/<INDUSTRY_SLUG>-<YYYY-MM-DD>.scan.md`:",
+    "",
+    "   ```markdown",
+    "   ---",
+    '   title: "Business Model Scan: <Industry Name>"',
+    "   slug: <INDUSTRY_SLUG>",
+    "   date: YYYY-MM-DD",
+    "   parent_issue: <N>",
+    "   status: complete",
+    "   ---",
+    "",
+    "   # Business Model Scan: <Industry Name>",
+    "",
+    "   ## Source Inputs",
+    "   - Industry plan: <relative path>",
+    "   - Prior research: <relative path> (optional)",
+    "",
+    "   ## Existing Coverage",
+    "   - <segment>: has canvas / no canvas / issue open",
+    "",
+    "   ## Segments Needing Analysis",
+    "",
+    "   ### <Segment Name>",
+    "   - **Priority:** high / medium / low",
+    "   - **Classification:** full document / variation of <parent> / defer",
+    "   - **Rationale:** <why this segment needs analysis>",
+    "   - **Expected variations:** <size / geography / regulatory>",
+    "",
+    "   ## Recommendations",
+    "   - <segment> \u2192 open canvas issue (priority: <level>)",
+    "   - <segment> \u2192 variation of <parent>, handle in parent's complete phase",
+    "   - <segment> \u2192 defer until <condition>",
+    "   ```",
+    "",
+    "7. **Create one `business-models:canvas` issue per in-scope segment**",
+    "   with `Depends on: #<scan-issue>`. Each canvas issue body",
+    "   references the scan report, the industry, the segment name, and",
+    "   the authorized source list.",
+    "",
+    "8. **Commit and push** the scan report. Close the scan issue.",
+    "",
+    "---",
+    "",
+    "## Phase 2: Canvas (`business-models:canvas`)",
+    "",
+    "**Goal:** Research and write a Business Model Canvas for one",
+    "industry segment \u2014 all nine blocks, each traced to a source.",
+    "",
+    "**Budget:** 4\u20138 targeted web searches to fill gaps not covered by",
+    "existing research. Reading industry research + web results, writing",
+    "one document, creating one downstream `business-models:complete`",
+    "issue.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the scan report and industry source** for context on this",
+    "   segment.",
+    "",
+    "2. **Read existing industry research** under",
+    "   `<BUSINESS_MODELS_ROOT>/<industry>/` for prior notes on this",
+    "   segment.",
+    "",
+    "3. **Read the skill's canvas template** at",
+    "   `.claude/skills/canvas-business-model/_references/templates/_template-canvas.md`",
+    "   (or the equivalent path under the `/cursor/skills/` tree on Cursor",
+    "   platforms). The template is authoritative \u2014 copy its structure",
+    "   verbatim into the output document, then populate each block.",
+    "",
+    "4. **Assess research gaps.** Determine which canvas blocks can be",
+    "   filled from existing research and which need targeted web",
+    "   searches. Prioritize blocks with the least existing coverage.",
+    "",
+    "5. **Execute targeted web searches** (4\u20138 total). Focus on:",
+    "   - Revenue models and pricing structures for this segment",
+    "   - Customer segment definitions and buyer personas",
+    "   - Key partnerships and supply-chain relationships",
+    "   - Cost-structure breakdown",
+    "   - Channel and distribution patterns",
+    "   - Regulatory and compliance factors affecting the business model",
+    "",
+    "6. **Write the canvas document** to",
+    "   `<BUSINESS_MODELS_ROOT>/<industry>/segments/<SEGMENT_SLUG>/business-model.md`",
+    "   following the template. Fill every one of the nine canvas blocks.",
+    "   Leave the `## Value Streams` and `## Variations` placeholders for",
+    "   the complete phase.",
+    "",
+    "   **Canvas rules:**",
+    "   - Every canvas block must have content \u2014 no empty blocks. Use",
+    "     `Not applicable \u2014 <reason>` when a block genuinely does not",
+    "     apply.",
+    "   - Every factual claim must trace to a source: either a research",
+    "     doc already on disk or a web-search result cited in the",
+    "     `## Sources` section.",
+    "   - Use Starlight frontmatter (`title`, `description`).",
+    "   - Link to related docs (industry plan, customer research, prior",
+    "     profiles) with **relative markdown paths** \u2014 never absolute",
+    "     `https://github.com/...` URLs.",
+    "",
+    "7. **Create the segment index** at",
+    "   `<BUSINESS_MODELS_ROOT>/<industry>/segments/<SEGMENT_SLUG>/index.md`",
+    "   if it does not already exist. The index should carry a short",
+    "   description and link to `./business-model.md`.",
+    "",
+    "8. **Create one `business-models:complete` issue** with",
+    "   `Depends on: #<canvas-issue>`. Its body references the path to",
+    "   the canvas document and names the industry and segment.",
+    "",
+    "9. **Commit and push** the canvas document. Close the canvas issue.",
+    "",
+    "---",
+    "",
+    "## Phase 3: Complete (`business-models:complete`)",
+    "",
+    "**Goal:** Derive BIZBOK value streams from the canvas, document",
+    "variations (size, geography, regulatory), and hand off to the",
+    "`bcm-writer` bundle for capability modelling.",
+    "",
+    "**Budget:** 2\u20134 targeted web searches (regulatory and geographic",
+    "specifics). Reading the canvas, editing the same document,",
+    "creating downstream issues.",
+    "",
+    "### Steps",
+    "",
+    "#### Part A: Value Streams",
+    "",
+    "1. **Read the canvas document** referenced in the issue body.",
+    "",
+    "2. **Identify value streams.** Each major Value Proposition",
+    "   typically maps to one value stream. Common patterns:",
+    "",
+    "   | Canvas Signal | Value Stream Pattern |",
+    "   |---------------|----------------------|",
+    "   | A distinct Value Proposition | One value stream delivering that proposition |",
+    "   | A cluster of Key Activities serving the same VP | Stages within that stream |",
+    "   | Different Customer Segments receiving the same VP | Same stream, different stakeholder triggers |",
+    "   | A Key Activity supporting multiple VPs | Shared capability across streams |",
+    "",
+    "3. **Define each value stream** with BIZBOK structure: name,",
+    "   triggering stakeholder, value proposition (verbatim from the",
+    "   canvas), ordered stages, stage outcomes, and the Key Activities",
+    "   mapping for each stage.",
+    "",
+    "4. **Edit the canvas document** to replace the",
+    "   `## Value Streams` placeholder:",
+    "",
+    "   ```markdown",
+    "   ## Value Streams",
+    "",
+    "   ### <Value Stream Name>",
+    "",
+    "   **Triggering stakeholder:** <who initiates>",
+    "   **Value proposition:** <from the canvas>",
+    "",
+    "   | Stage | Description | Key Activities (from Canvas) | Stage Outcome |",
+    "   |-------|-------------|------------------------------|---------------|",
+    "   | <Stage 1> | <what happens> | <activities> | <outcome> |",
+    "   | <Stage 2> | <what happens> | <activities> | <outcome> |",
+    "   ```",
+    "",
+    "   **Value stream rules:**",
+    "   - **Minimum 2 value streams** per segment (most have 3\u20135).",
+    "   - Every value stream must trace to a Value Proposition on the",
+    "     canvas.",
+    "   - Every stage must map to at least one Key Activity on the",
+    "     canvas.",
+    "   - Stages are ordered \u2014 each stage's output feeds the next stage's",
+    "     input.",
+    "   - A single Key Activity may appear in multiple value streams.",
+    "   - Value-stream names are **noun phrases**, not verbs.",
+    "",
+    "#### Part B: Variations",
+    "",
+    "5. **Research variations** using 2\u20134 targeted web searches:",
+    "   - How do businesses in this segment differ at SMB vs. mid-market",
+    "     vs. enterprise scale?",
+    "   - Are there geographic or regulatory differences (e.g. varying",
+    "     privacy laws, industry-specific certifications)?",
+    "   - Do revenue models or key partnerships change by size or region?",
+    "",
+    "6. **Edit the canvas document** to replace the `## Variations`",
+    "   placeholder with size, geographic, and regulatory sub-sections.",
+    "",
+    "   **Variation rules:**",
+    "   - **Size variations are always required.** At minimum, document",
+    "     SMB vs. enterprise.",
+    "   - **Geographic variations are required when** the segment",
+    "     operates internationally and regulatory or market-structure",
+    "     differences affect the business model. Skip with",
+    "     `Not applicable \u2014 <reason>` if genuinely not relevant.",
+    "   - **Regulatory variations are required when** industry-specific",
+    "     standards or certifications exist that affect how the business",
+    "     model operates.",
+    "   - Only include canvas blocks that actually differ. Do not pad",
+    '     with "No difference" rows.',
+    "",
+    "#### Part C: Value Stream \u2192 Capability Linking",
+    "",
+    "7. **Surface capabilities for downstream BCM modelling.** For each",
+    "   value stream stage that maps to a Key Activity the consuming",
+    "   project needs to implement, identify the underlying *capability*",
+    "   (a noun phrase \u2014 what the business does, not how). Typical",
+    "   extraction:",
+    "",
+    "   - Look at each value-stream stage's Key Activities mapping.",
+    "   - Each Key Activity usually corresponds to one capability (e.g.",
+    "     Key Activity `Schedule appointments` \u2192 capability",
+    "     `Appointment Scheduling`).",
+    "   - Deduplicate across stages and across value streams.",
+    "",
+    "8. **Add a `## Value Stream to Capability Linking` section** to the",
+    "   canvas document, immediately after `## Variations`:",
+    "",
+    "   ```markdown",
+    "   ## Value Stream to Capability Linking",
+    "",
+    "   | Value Stream | Stage | Key Activity | Capability (noun) | BCM Issue |",
+    "   |--------------|-------|--------------|-------------------|-----------|",
+    "   | <stream> | <stage> | <activity> | <capability name> | #<bcm-outline-issue> |",
+    "   ```",
+    "",
+    "9. **For each distinct capability surfaced above**, check whether a",
+    "   BCM document already exists under the consuming project's",
+    "   `<BCM_DOC_ROOT>`. For capabilities that are **not yet modelled**,",
+    "   create one `bcm:outline` issue (owned by the downstream",
+    "   `bcm-writer` bundle) per capability, citing the canvas path and",
+    "   the specific value-stream stage the capability appears in. Fill",
+    "   the `BCM Issue` column of the linking table as each issue is",
+    "   created so the table is cross-linked before the complete issue",
+    "   closes.",
+    "",
+    "#### Part D: Commit and Handoffs",
+    "",
+    "10. **Commit and push** the updated canvas document.",
+    "",
+    "11. **Comment on the canvas issue** and the scan issue with a short",
+    "    summary: value-stream count, variation coverage, and the list of",
+    "    `bcm:outline` issues created.",
+    "",
+    "12. **Close the complete issue.**",
+    "",
+    "---",
+    "",
+    "## Coordination with Other Agents",
+    "",
+    "### Upstream: industry-discovery bundle",
+    "",
+    "`industry-discovery` produces the plan files this pipeline reads as",
+    "input to the scan phase. The scan phase's issue body should cite the",
+    "plan file (`<PLANS_DIR>/<slug>.plan.md`) as its source of",
+    "segments. Business-model scan issues are typically created as a",
+    "follow-up to an industry plan that cleared the fit threshold.",
+    "",
+    "### Upstream: research-pipeline bundle",
+    "",
+    "If a canvas block cannot be adequately filled from existing research",
+    "and the web-search budget is exhausted, create a `research:scope`",
+    "issue to commission a deeper research dive. Block the canvas issue on",
+    "the new research issue rather than shipping a thinly-sourced block.",
+    "",
+    "### Downstream: bcm-writer bundle",
+    "",
+    "Canvas documents are the authoritative source for value streams that",
+    "the `bcm-writer`'s Value Stream Mapping section consumes. Phase 3",
+    "opens `bcm:outline` issues for every distinct capability surfaced in",
+    "Key Activities that does not yet have a BCM document. The",
+    "`bcm-writer` bundle picks those issues up and decomposes each",
+    "capability into an L1/L2/L3 tree, citing the canvas path in its",
+    "Traceability section.",
+    "",
+    "### Downstream: company-profile bundle",
+    "",
+    "The `company-profile` bundle's match phase reads",
+    "`<BUSINESS_MODELS_ROOT>` (same default path \u2014 see Configurable",
+    "Paths) to identify which of its profiled companies operate in a given",
+    "segment. When a canvas is published, company-profile's `match` phase",
+    "appends a bidirectional cross-link between the matched profile and",
+    "the canvas. This agent never rewrites profile bodies \u2014 it only",
+    "publishes the canvas.",
+    "",
+    "### File Boundaries",
+    "",
+    "- **Reads:**",
+    "  - `<BUSINESS_MODELS_ROOT>/` \u2014 prior canvases, industry indexes",
+    "  - `<PLANS_DIR>/` \u2014 industry-discovery plan files",
+    "  - `<DELIVERABLES_DIR>/` \u2014 research deliverables",
+    "  - `<docsRoot>/` \u2014 any file for context",
+    "- **Writes:**",
+    "  - `<SCAN_DIR>/<INDUSTRY_SLUG>-<YYYY-MM-DD>.scan.md` (Phase 1)",
+    "  - `<BUSINESS_MODELS_ROOT>/<industry>/segments/<SEGMENT_SLUG>/business-model.md`",
+    "    (Phases 2\u20133)",
+    "  - `<BUSINESS_MODELS_ROOT>/<industry>/segments/<SEGMENT_SLUG>/index.md`",
+    "    (Phase 2, when missing)",
+    "- **Never writes to:**",
+    "  - `<BCM_DOC_ROOT>/` (the `bcm-writer` bundle owns this)",
+    "  - `<REQUIREMENTS_ROOT>/` (the `requirements-writer` bundle owns",
+    "    this)",
+    "  - `<PEOPLE_PROFILES_DIR>/`, `<COMPANIES_PROFILES_DIR>/`,",
+    "    `<SOFTWARE_PROFILES_DIR>/` (the profile bundles own these)",
+    "",
+    "---",
+    "",
+    "## Blocked Issues",
+    "",
+    "Follow your project's shared Blocked Issues procedure. Additional",
+    "block reasons specific to business-model authoring:",
+    "",
+    "- **Industry source missing.** The scan-phase issue cites a plan",
+    "  file that does not exist on disk.",
+    "- **Insufficient research.** The canvas phase cannot fill one or",
+    "  more blocks from existing research or targeted web searches (open",
+    "  a `research:scope` issue and block on it).",
+    "- **Conflicting sources.** Two authoritative sources contradict each",
+    "  other on a canvas block and the conflict cannot be reconciled by",
+    "  the agent.",
+    "- **Segment definition ambiguous.** The scan report flagged the",
+    "  segment as needing human clarification before a canvas can be",
+    "  authored.",
+    "",
+    "---",
+    "",
+    "## Output Boundaries",
+    "",
+    "This agent writes **only** to the directories listed under File",
+    "Boundaries above. It does not write capability models, requirement",
+    "documents, people profiles, company profiles, or software profiles.",
+    "Work it surfaces in those domains is delegated via issues to the",
+    "appropriate specialist bundle (`bcm-writer`, `requirements-writer`,",
+    "`people-profile`, `company-profile`, `software-profile`).",
+    "",
+    "---",
+    "",
+    "## Rules",
+    "",
+    "- **One phase per session.** Never run two phases back-to-back in a",
+    "  single session.",
+    "- **Persist before closing.** Every phase must write its output file",
+    "  before closing its issue.",
+    "- **Canvas blocks are never empty.** Use",
+    "  `Not applicable \u2014 <reason>` when a block genuinely does not apply.",
+    "- **Size variations are always required.** Every segment has",
+    "  meaningful differences between SMB and enterprise operations.",
+    "- **Value streams derive from the canvas.** Key Activities and",
+    "  Value Propositions on the canvas define value streams. Do not",
+    "  invent value streams that do not trace to the canvas.",
+    "- **One segment per document.** Sub-segments share the parent",
+    "  document with a variation section unless their business model is",
+    "  fundamentally different.",
+    "- **No fabrication.** Every canvas block and every value-stream",
+    "  stage must trace to a cited source. Do not populate from general",
+    "  knowledge alone.",
+    "- **Relative links only.** Cross-references between docs use",
+    "  relative markdown paths, never absolute `https://github.com/...`",
+    "  URLs.",
+    "- **Produce canvases, not capabilities.** Capability modelling is",
+    "  the responsibility of the `bcm-writer` bundle. Hand off surfaced",
+    "  capabilities via `bcm:outline` issues; do not write capability",
+    "  decomposition in the canvas itself."
+  ].join("\n")
+};
+var scanBusinessModelsSkill = {
+  name: "scan-business-models",
+  description: "Kick off the scan phase of a business-model analysis cycle. Creates a business-models:scan issue for the supplied industry and dispatches Phase 1 of the business-models-analyst, which reads industry-discovery output and identifies segments needing a canvas.",
+  disableModelInvocation: true,
+  userInvocable: true,
+  context: "fork",
+  agent: "business-models-analyst",
+  platforms: { cursor: { exclude: true } },
+  instructions: [
+    "# Scan Business Models",
+    "",
+    "Kick off a business-model analysis cycle. Creates a",
+    "`business-models:scan` issue carrying the industry scope and",
+    "dispatches Phase 1 (Scan) in the business-models-analyst agent.",
+    "",
+    "## Usage",
+    "",
+    "/scan-business-models <industry-slug>",
+    "",
+    "Optional extensions in the issue body:",
+    "- `plan: <path>` \u2014 path to the industry-discovery plan file that",
+    "  cleared this industry for downstream research (e.g.",
+    "  `docs/industries/plans/<slug>.plan.md`)",
+    "- `sources: <list>` \u2014 additional authorized input paths",
+    "- `exclude: <segment list>` \u2014 segments already covered to skip",
+    "- `slug: <kebab-case>` \u2014 override the derived industry slug",
+    "",
+    "## Default Paths",
+    "",
+    "If the project has no override in `docs/src/content/docs/project-context.md` or",
+    "`agentConfig.rules`, outputs land under:",
+    "",
+    "- Scan report: `docs/research/business-models/<slug>-YYYY-MM-DD.scan.md`",
+    "- Canvas docs (produced by Phase 2): `docs/src/content/docs/industry-research/<industry>/segments/<segment-slug>/business-model.md`",
+    "",
+    "## Steps",
+    "",
+    "1. Create a `business-models:scan` issue with `type:business-model`,",
+    "   `priority:medium`, and `status:ready`. The body must include the",
+    "   industry slug, the source plan path (if any), and any overrides.",
+    "2. Execute Phase 1 (Scan) of the business-models-analyst agent.",
+    "3. Phase 1 creates one `business-models:canvas` issue per in-scope",
+    "   segment. Each canvas issue declares its `Depends on:`",
+    "   predecessor.",
+    "",
+    "## Output",
+    "",
+    "- A scan report under the project's business-models scan directory,",
+    "  listing which segments need canvases and which are already",
+    "  covered or deferred.",
+    "- One `business-models:canvas` issue per segment classified as",
+    "  `full document` in the scan report."
+  ].join("\n")
+};
+var canvasBusinessModelSkill = {
+  name: "canvas-business-model",
+  description: "Kick off the canvas phase of a business-model analysis cycle. Creates a business-models:canvas issue for the supplied industry/segment and dispatches Phase 2 of the business-models-analyst, which researches and writes the Osterwalder nine-block canvas.",
+  disableModelInvocation: true,
+  userInvocable: true,
+  context: "fork",
+  agent: "business-models-analyst",
+  platforms: { cursor: { exclude: true } },
+  referenceFiles: BUSINESS_MODELS_CANVAS_REFERENCE_FILES,
+  instructions: [
+    "# Canvas Business Model",
+    "",
+    "Author a Business Model Canvas for one industry segment. Creates a",
+    "`business-models:canvas` issue and dispatches Phase 2 (Canvas) in",
+    "the business-models-analyst agent.",
+    "",
+    "Most cycles do not invoke this skill directly \u2014 Phase 1 (Scan)",
+    "creates canvas issues automatically from the scan report. Use this",
+    "skill when:",
+    "",
+    "- A new segment was carved out of an already-modelled industry",
+    "- A human operator wants to author a canvas without a prior scan",
+    "- The scan report deferred a segment and the blocker is now",
+    "  resolved",
+    "",
+    "## Usage",
+    "",
+    "/canvas-business-model <industry-slug>:<segment-slug>",
+    "",
+    "Optional extensions in the issue body:",
+    "- `segment_name: <name>` \u2014 human-readable segment name (defaults to",
+    "  the slug prettified)",
+    "- `sources: <list>` \u2014 authorized research-input paths",
+    "- `scan: <path>` \u2014 prior scan report that identified this segment",
+    "  (optional when invoked manually)",
+    "",
+    "## Canvas Template",
+    "",
+    "This skill ships a verbatim canvas template at",
+    "`.claude/skills/canvas-business-model/_references/templates/_template-canvas.md`.",
+    "The Phase 2 handler reads that file as its authoritative structure \u2014",
+    "every canvas document copies the template and fills each of the",
+    "nine blocks, leaving the `## Value Streams` and `## Variations`",
+    "placeholders for Phase 3 (Complete).",
+    "",
+    "## Default Paths",
+    "",
+    "If the project has no override in `docs/src/content/docs/project-context.md` or",
+    "`agentConfig.rules`, the canvas lands at:",
+    "",
+    "`docs/src/content/docs/industry-research/<industry>/segments/<segment-slug>/business-model.md`",
+    "",
+    "## Steps",
+    "",
+    "1. Create a `business-models:canvas` issue with",
+    "   `type:business-model`, `priority:medium`, and `status:ready`.",
+    "   The body must include the industry slug, segment slug, and any",
+    "   scan-report reference.",
+    "2. Execute Phase 2 (Canvas) of the business-models-analyst agent.",
+    "3. Phase 2 writes the nine-block canvas and creates a",
+    "   `business-models:complete` issue for the downstream Phase 3.",
+    "",
+    "## Output",
+    "",
+    "- A new `business-model.md` with all nine canvas blocks populated.",
+    "- A segment `index.md` in the same folder (if missing).",
+    "- One `business-models:complete` issue cross-linking back to the",
+    "  canvas."
+  ].join("\n")
+};
+var completeBusinessModelSkill = {
+  name: "complete-business-model",
+  description: "Kick off the complete phase of a business-model analysis cycle. Creates a business-models:complete issue for an already-authored canvas and dispatches Phase 3 of the business-models-analyst, which derives BIZBOK value streams, documents variations, and hands off capability work to bcm-writer.",
+  disableModelInvocation: true,
+  userInvocable: true,
+  context: "fork",
+  agent: "business-models-analyst",
+  platforms: { cursor: { exclude: true } },
+  instructions: [
+    "# Complete Business Model",
+    "",
+    "Close out a business-model analysis cycle. Creates a",
+    "`business-models:complete` issue for a canvas that already has its",
+    "nine blocks populated and dispatches Phase 3 (Complete) in the",
+    "business-models-analyst agent.",
+    "",
+    "Phase 3 appends BIZBOK value streams, documents size / geographic /",
+    "regulatory variations, adds a `## Value Stream to Capability",
+    "Linking` section, and opens one `bcm:outline` issue per",
+    "undeployed capability for the downstream `bcm-writer` bundle.",
+    "",
+    "Most cycles do not need this skill \u2014 Phase 2 (Canvas) creates the",
+    "complete issue automatically. Use this skill when:",
+    "",
+    "- A human authored the canvas and only needs the agent to attach",
+    "  value streams and variations",
+    "- The canvas was imported from another source and needs value-",
+    "  stream completion",
+    "",
+    "## Usage",
+    "",
+    "/complete-business-model <industry-slug>:<segment-slug>",
+    "",
+    "## Default Paths",
+    "",
+    "If the project has no override in `docs/src/content/docs/project-context.md` or",
+    "`agentConfig.rules`, the target canvas lives at:",
+    "",
+    "`docs/src/content/docs/industry-research/<industry>/segments/<segment-slug>/business-model.md`",
+    "",
+    "## Steps",
+    "",
+    "1. Create a `business-models:complete` issue with",
+    "   `type:business-model`, `priority:medium`, and `status:ready`.",
+    "   Body must include the canvas document path.",
+    "2. Execute Phase 3 (Complete) of the business-models-analyst agent.",
+    "",
+    "## Output",
+    "",
+    "- Updates to `business-model.md` \u2014 `## Value Streams`, ",
+    "  `## Variations`, and `## Value Stream to Capability Linking`",
+    "  sections populated.",
+    "- One `bcm:outline` issue (consumed by the `bcm-writer` bundle)",
+    "  per distinct capability surfaced from Key Activities that does",
+    "  not already have a BCM document."
+  ].join("\n")
+};
+var businessModelsBundle = {
+  name: "business-models",
+  description: "Business-model authoring pipeline: Osterwalder Business Model Canvas plus BIZBOK value streams per industry segment. 3 phases (scan, canvas, complete) with business-models:* phase labels. Sits between industry-discovery and bcm-writer in the research pipeline. Enabled by default; domain-neutral; filesystem-durable between phases.",
+  appliesWhen: () => true,
+  rules: [
+    {
+      name: "business-models-workflow",
+      description: "Describes the 3-phase business-model pipeline, the business-models:* label taxonomy, and the handoff boundaries with industry-discovery (upstream) and bcm-writer (downstream).",
+      scope: AGENT_RULE_SCOPE.ALWAYS,
+      content: [
+        "# Business Models Workflow",
+        "",
+        "Use `/scan-business-models <industry-slug>` to kick off a",
+        "business-model analysis cycle. The pipeline runs in 3 phases \u2014",
+        "scan, canvas, complete \u2014 each tracked by its own GitHub issue",
+        "labeled `business-models:scan`, `business-models:canvas`, or",
+        "`business-models:complete`. All issues carry `type:business-model`.",
+        "",
+        "Two additional user-invocable skills drive the downstream phases",
+        "directly when the default pipeline needs to be entered mid-",
+        "stream:",
+        "",
+        "- `/canvas-business-model <industry>:<segment>` \u2014 author the",
+        "  nine-block Osterwalder canvas for one segment (normally created",
+        "  by the scan phase automatically).",
+        "- `/complete-business-model <industry>:<segment>` \u2014 derive BIZBOK",
+        "  value streams, document variations, and hand off capabilities",
+        "  to `bcm-writer` (normally created by the canvas phase",
+        "  automatically).",
+        "",
+        "The bundle sits between `industry-discovery` (which picks",
+        "verticals and segments) and `bcm-writer` (which models the",
+        "capabilities needed to execute). Canvases describe *how the",
+        "business operates in a segment*; the downstream BCM writer then",
+        "derives capability models from the Key Activities and value",
+        "streams authored here. The `company-profile` bundle reads the",
+        "same `<BUSINESS_MODELS_ROOT>` directory",
+        "(`docs/src/content/docs/industry-research/` by default) to match profiled",
+        "companies against published canvases.",
+        "",
+        "See the `business-models-analyst` agent definition for full",
+        "workflow details, default paths, the Osterwalder/BIZBOK",
+        "methodology, and phase-by-phase instructions."
+      ].join("\n"),
+      platforms: {
+        cursor: { exclude: true }
+      },
+      tags: ["workflow"]
+    }
+  ],
+  skills: [
+    scanBusinessModelsSkill,
+    canvasBusinessModelSkill,
+    completeBusinessModelSkill
+  ],
+  subAgents: [businessModelsAnalystSubAgent],
+  labels: [
+    {
+      name: "type:business-model",
+      color: "5319E7",
+      description: "Work that authors or updates a Business Model Canvas plus BIZBOK value streams for an industry segment"
+    },
+    {
+      name: "business-models:scan",
+      color: "C5DEF5",
+      description: "Phase 1: read industry-discovery output and identify segments needing a business-model canvas"
+    },
+    {
+      name: "business-models:canvas",
+      color: "BFDADC",
+      description: "Phase 2: research and write the nine-block Osterwalder canvas for one segment"
+    },
+    {
+      name: "business-models:complete",
+      color: "D4C5F9",
+      description: "Phase 3: derive BIZBOK value streams, document variations, and hand off capabilities to bcm-writer"
+    }
+  ]
+};
+
 // src/agent/bundles/company-profile.ts
 var companyProfileAnalystSubAgent = {
   name: "company-profile-analyst",
@@ -17092,6 +18091,7 @@ var BUILT_IN_BUNDLES = [
   peopleProfileBundle,
   softwareProfileBundle,
   industryDiscoveryBundle,
+  businessModelsBundle,
   bcmWriterBundle,
   maintenanceAuditBundle
 ];
@@ -20881,6 +21881,7 @@ export {
   awsCdkBundle,
   baseBundle,
   bcmWriterBundle,
+  businessModelsBundle,
   companyProfileBundle,
   formatLayoutViolation,
   formatStarlightSingletonViolation,