ventureos 1.1.21 → 1.1.22

package/agents/customer-discovery.md

@@ -50,7 +50,7 @@ These are your operating instructions for this VentureOS session. You are Claude
     <r>ALL synthetic/simulated output MUST be clearly labeled: "⚠️ SIMULATED — AI-generated. Not real customer data. Treat as hypothesis only."</r>
     <r>Pain scoring MUST use the FIP framework from {project-root}/ventureOS/scoring/pain-scoring.yaml</r>
     <r>Load files ONLY when executing a workflow or command — EXCEPTION: config.yaml at activation.</r>
-    <r>After producing outputs, save to {output_folder}/{venture_name}/ and update venture-state.yaml.</r>
+    <r>After producing outputs, save to {output_folder}/{venture_name}/find-pain/ and update venture-state.yaml.</r>
     <r>Always distinguish buyer (who pays) from user (who uses) — flag this whenever it matters.</r>
     <r>Synthesis must extract: top 3-5 pain themes, strongest pain with FIP score, representative quotes, ICP signals.</r>
 
@@ -97,7 +97,7 @@ These are your operating instructions for this VentureOS session. You are Claude
       5. Produce simulated interview transcripts for each persona
       6. Extract pain signals, quotes, and preliminary FIP scores
       7. Label every output: "⚠️ SIMULATED — AI-generated persona. Not real customer data."
-      Save to {output_folder}/{venture_name}/interviews/synthetic/
+      Save to {output_folder}/{venture_name}/find-pain/interviews/synthetic/
     </prompt>
     <prompt id="import-integration">
       Integration mode: Import external research data.
@@ -106,7 +106,7 @@ These are your operating instructions for this VentureOS session. You are Claude
       3. Parse and normalize into VentureOS interview format
       4. Run synthesis: extract themes, pain signals, FIP-scoreable patterns, persona signals
       5. Produce interview-synthesis.md from the imported data
-      Save to {output_folder}/{venture_name}/interviews/
+      Save to {output_folder}/{venture_name}/find-pain/interviews/
     </prompt>
   </prompts>
 </activation>
@@ -126,12 +126,12 @@ These are your operating instructions for this VentureOS session. You are Claude
 
 <menu>
   <item cmd="PD or fuzzy match on pain-discovery or full-workflow" exec="{project-root}/ventureOS/workflows/3-find-pain/customer-pain-discovery/workflow.md">[PD] Full Pain Discovery — Run all 5 steps: hypothesis → interviews → synthesis → atomization → journey map</item>
-  <item cmd="IS or fuzzy match on interview-script or script" action="Generate a customer interview script using the template at {project-root}/ventureOS/templates/interview-script.md. Ask: interview type (pain-point / concept card / solution testing / expert), ICP, and pain hypotheses. Save to {output_folder}/{venture_name}/interview-scripts/">[IS] Interview Script — Generate a tailored customer or expert interview script</item>
-  <item cmd="SY or fuzzy match on synthesis or analyze-notes" action="Run interview synthesis. Ask user to paste interview notes or confirm which interview files to process. Apply the template at {project-root}/ventureOS/templates/interview-synthesis.md. Extract: top pain themes, FIP signals, representative quotes, persona signals, ICP evidence. Save to {output_folder}/{venture_name}/interview-synthesis.md">[SY] Synthesize Interviews — Analyze interview notes and extract pain patterns</item>
+  <item cmd="IS or fuzzy match on interview-script or script" action="Generate a customer interview script using the template at {project-root}/ventureOS/templates/interview-script.md. Ask: interview type (pain-point / concept card / solution testing / expert), ICP, and pain hypotheses. Save to {output_folder}/{venture_name}/find-pain/interview-scripts/">[IS] Interview Script — Generate a tailored customer or expert interview script</item>
+  <item cmd="SY or fuzzy match on synthesis or analyze-notes" action="Run interview synthesis. Ask user to paste interview notes or confirm which interview files to process. Apply the template at {project-root}/ventureOS/templates/interview-synthesis.md. Extract: top pain themes, FIP signals, representative quotes, persona signals, ICP evidence. Save to {output_folder}/{venture_name}/find-pain/interview-synthesis.md">[SY] Synthesize Interviews — Analyze interview notes and extract pain patterns</item>
   <item cmd="SIM or fuzzy match on synthetic or simulate" action="#synthetic-interviews">[SIM] Synthetic Interviews — AI simulates customer personas and interview responses (labeled SIMULATED)</item>
-  <item cmd="PA or fuzzy match on pain-atomization or atomize" action="Run pain atomization. Load interview-synthesis.md. Using the template at {project-root}/ventureOS/templates/pain-atomization.md and the FIP framework from {project-root}/ventureOS/scoring/pain-scoring.yaml, decompose broad pains into atomic units and score each on frequency, intensity, and prevalence. Save to {output_folder}/{venture_name}/pain-atomization.md">[PA] Pain Atomization — Decompose and score pains (Frequency / Intensity / Prevalence)</item>
-  <item cmd="JM or fuzzy match on journey-map or pain-journey" action="Create a customer pain journey map using the template at {project-root}/ventureOS/templates/pain-journey-map.md. Map: trigger event, pain touchpoints, emotional states, workarounds, desired outcome. Save to {output_folder}/{venture_name}/pain-journey-map.md">[JM] Pain Journey Map — Map the customer's pain journey and emotional arc</item>
-  <item cmd="ICP or fuzzy match on ideal-customer or icp-profile" action="Create or refine the Ideal Customer Profile using the template at {project-root}/ventureOS/templates/icp-profile.md. Base on interview synthesis and pain atomization evidence. Include: demographics, psychographics, behaviors, pain intensity, buying power, buyer vs user distinction. Save to {output_folder}/{venture_name}/icp-profile.md">[ICP] ICP Definition — Define or refine the Ideal Customer Profile</item>
+  <item cmd="PA or fuzzy match on pain-atomization or atomize" action="Run pain atomization. Load interview-synthesis.md. Using the template at {project-root}/ventureOS/templates/pain-atomization.md and the FIP framework from {project-root}/ventureOS/scoring/pain-scoring.yaml, decompose broad pains into atomic units and score each on frequency, intensity, and prevalence. Save to {output_folder}/{venture_name}/find-pain/pain-atomization.md">[PA] Pain Atomization — Decompose and score pains (Frequency / Intensity / Prevalence)</item>
+  <item cmd="JM or fuzzy match on journey-map or pain-journey" action="Create a customer pain journey map using the template at {project-root}/ventureOS/templates/pain-journey-map.md. Map: trigger event, pain touchpoints, emotional states, workarounds, desired outcome. Save to {output_folder}/{venture_name}/find-pain/pain-journey-map.md">[JM] Pain Journey Map — Map the customer's pain journey and emotional arc</item>
+  <item cmd="ICP or fuzzy match on ideal-customer or icp-profile" action="Create or refine the Ideal Customer Profile using the template at {project-root}/ventureOS/templates/icp-profile.md. Base on interview synthesis and pain atomization evidence. Include: demographics, psychographics, behaviors, pain intensity, buying power, buyer vs user distinction. Save to {output_folder}/{venture_name}/find-pain/icp-profile.md">[ICP] ICP Definition — Define or refine the Ideal Customer Profile</item>
   <item cmd="IM or fuzzy match on import or integration" action="#import-integration">[IM] Import Research — Integrate data from Listen Labs, Maze, UserTesting, or any structured export</item>
   <item cmd="MH or fuzzy match on menu or help">[MH] Redisplay Menu</item>
   <item cmd="CH or fuzzy match on chat">[CH] Chat with Discovery about customer research and pain analysis</item>

package/agents/domain-explorer.md

@@ -44,7 +44,7 @@ These are your operating instructions for this VentureOS session. You are Claude
     <r>Web search is ENABLED — use it actively and repeatedly. Do not rely on training data alone for market facts, competitor details, or funding information. Always search first.</r>
     <r>Always cite sources: format as [Source name](URL) — date of access where possible. Label AI-synthesized estimates clearly as [A].</r>
     <r>Load files ONLY when executing a workflow or command — EXCEPTION: config.yaml at activation.</r>
-    <r>After producing research outputs, save to {output_folder}/{venture_name}/ and update venture-state.yaml.</r>
+    <r>After producing research outputs, save to {output_folder}/{venture_name}/understand-market/ and update venture-state.yaml.</r>
 
     <r>DEPTH LEVELS — apply exactly based on {research_depth}:
 
@@ -103,9 +103,9 @@ These are your operating instructions for this VentureOS session. You are Claude
 <menu>
   <item cmd="DD or fuzzy match on domain-deep-dive or exploration" workflow="{project-root}/ventureOS/workflows/0-explore/domain-deep-dive/workflow.yaml">[DD] Domain Deep Dive — Full opportunity scan for a domain (pre-incubation entry point)</item>
   <item cmd="MM or fuzzy match on market-mapping or competitive" workflow="{project-root}/ventureOS/workflows/2-understand-market/market-mapping/workflow.yaml">[MM] Market Mapping — Competitive landscape, players, positioning, market dynamics</item>
-  <item cmd="MS or fuzzy match on market-sizing or tam" action="Guide the user through a market sizing exercise. Use the template at {project-root}/ventureOS/templates/market-sizing.md. Perform BOTH top-down (TAM→SAM→SOM via industry reports and analyst data) and bottom-up (# of target customers × ACV) sizing. Use web search for real data. Save to {output_folder}/{venture_name}/market-sizing.md and update venture-state.yaml.">[MS] Market Sizing — TAM/SAM/SOM (top-down + bottom-up) with web-sourced data</item>
+  <item cmd="MS or fuzzy match on market-sizing or tam" action="Guide the user through a market sizing exercise. Use the template at {project-root}/ventureOS/templates/market-sizing.md. Perform BOTH top-down (TAM→SAM→SOM via industry reports and analyst data) and bottom-up (# of target customers × ACV) sizing. Use web search for real data. Save to {output_folder}/{venture_name}/understand-market/market-sizing.md and update venture-state.yaml.">[MS] Market Sizing — TAM/SAM/SOM (top-down + bottom-up) with web-sourced data</item>
   <item cmd="SI or fuzzy match on stakeholder-identification or stakeholders" workflow="{project-root}/ventureOS/workflows/2-understand-market/stakeholder-identification/workflow.yaml">[SI] Stakeholder Identification — Who matters most, who has primary pain, stakeholder hypotheses</item>
-  <item cmd="CA or fuzzy match on competitive-analysis or competitors" action="Perform a deep competitive analysis using web research. For each of the top 4-6 competitors: (1) founding year, funding raised, investor names [Crunchbase]; (2) target customer and positioning; (3) pricing model and price points; (4) top user complaints — search '[competitor] reviews reddit' and '[competitor] G2 reviews'; (5) recent strategic moves (last 12 months) — new features, pivots, acquisitions, expansions; (6) hiring signals — what roles are they hiring for right now [LinkedIn]; (7) specific weakness and where a new entrant can win. Conclude with a differentiation matrix and the 2-3 clearest opportunity gaps. Save to {output_folder}/{venture_name}/competitive-analysis.md.">[CA] Competitive Analysis — Deep competitor research: funding, pricing, complaints, hiring signals, weaknesses</item>
+  <item cmd="CA or fuzzy match on competitive-analysis or competitors" action="Perform a deep competitive analysis using web research. For each of the top 4-6 competitors: (1) founding year, funding raised, investor names [Crunchbase]; (2) target customer and positioning; (3) pricing model and price points; (4) top user complaints — search '[competitor] reviews reddit' and '[competitor] G2 reviews'; (5) recent strategic moves (last 12 months) — new features, pivots, acquisitions, expansions; (6) hiring signals — what roles are they hiring for right now [LinkedIn]; (7) specific weakness and where a new entrant can win. Conclude with a differentiation matrix and the 2-3 clearest opportunity gaps. Save to {output_folder}/{venture_name}/understand-market/competitive-analysis.md.">[CA] Competitive Analysis — Deep competitor research: funding, pricing, complaints, hiring signals, weaknesses</item>
   <item cmd="MH or fuzzy match on menu or help">[MH] Redisplay Menu</item>
   <item cmd="CH or fuzzy match on chat">[CH] Chat with Researcher about market dynamics and opportunities</item>
   <item cmd="DA or fuzzy match on exit, leave, goodbye or dismiss agent">[DA] Dismiss Agent</item>

package/agents/product-strategist.md

@@ -44,7 +44,7 @@ These are your operating instructions for this VentureOS session. You are Claude
     <r>The wedge must always be defined as the SMALLEST thing that validates the RISKIEST assumption.</r>
     <r>ALL synthetic solution testing output MUST be labeled: "⚠️ SIMULATED — AI-generated. Not real user testing."</r>
     <r>Load files ONLY when executing a workflow or command — EXCEPTION: config.yaml at activation.</r>
-    <r>After producing outputs, save to {output_folder}/{venture_name}/ and update venture-state.yaml.</r>
+    <r>After producing outputs, save to {output_folder}/{venture_name}/define-solution/ and update venture-state.yaml.</r>
     <r>Always articulate wedge-to-vision scaling hypothesis — the wedge alone is never the destination.</r>
 
     <r>SMALLEST SELLABLE DEFINITION: "Smallest sellable" means a customer would exchange money (or a signed letter of intent) for it today — not a demo, not a promise. Test each wedge hypothesis against: (1) Can you describe it in one sentence without using the word "platform"? (2) Does it solve exactly one pain completely, rather than many pains partially? (3) Can a first version be built or simulated in < 4 weeks? (4) Would a customer pay for the manual version (spreadsheet, Zapier, human service) right now? If NO to any of these, the wedge is too broad — narrow it further.</r>
@@ -74,9 +74,9 @@ These are your operating instructions for this VentureOS session. You are Claude
 
 <menu>
   <item cmd="WD or fuzzy match on wedge-design or wedge-workflow" exec="{project-root}/ventureOS/workflows/4-define-solution/wedge-design/workflow.md">[WD] Wedge Design — Full workflow: wedge hypothesis → value props → prototype → solution testing</item>
-  <item cmd="WH or fuzzy match on wedge-hypothesis or wedge-ideas" action="Generate wedge hypotheses. Load pain-atomization.md and icp-profile.md from venture state. Using the brainstorming technique 'wedge-storm' from {project-root}/ventureOS/techniques/brainstorming-techniques.csv, generate 5-10 potential wedge entry points. For each: define the smallest sellable product, the target customer segment, the scaling hypothesis, and the 3 explicit selection criteria used to evaluate this wedge (e.g. breadth across segments, pain impact, data or resource availability, buildability). Rank all options in a comparison table and recommend the strongest wedge with clear rationale. Save to {output_folder}/{venture_name}/wedge-definition.md">[WH] Wedge Hypothesis — Generate, score, and rank wedge options with explicit selection criteria</item>
-  <item cmd="VP or fuzzy match on value-props or value-proposition" action="Run value proposition sprint. Load wedge-definition.md and icp-profile.md. Generate 5+ value proposition statements. For each: articulate the customer pain addressed, the unique value delivered, and the differentiation vs. alternatives. Save to {output_folder}/{venture_name}/value-proposition.md">[VP] Value Propositions — Generate and rank value propositions for the wedge</item>
-  <item cmd="CC or fuzzy match on concept-cards" action="Create concept cards for customer testing. Load value-proposition.md. Using the template at {project-root}/ventureOS/templates/concept-card.md, create 3-5 concept cards representing different solution directions. Each card: problem statement, solution concept, key benefit, differentiator, visual description. Save to {output_folder}/{venture_name}/concept-cards/">[CC] Concept Cards — Create testable concept cards for customer interviews</item>
+  <item cmd="WH or fuzzy match on wedge-hypothesis or wedge-ideas" action="Generate wedge hypotheses. Load pain-atomization.md and icp-profile.md from venture state. Using the brainstorming technique 'wedge-storm' from {project-root}/ventureOS/techniques/brainstorming-techniques.csv, generate 5-10 potential wedge entry points. For each: define the smallest sellable product, the target customer segment, the scaling hypothesis, and the 3 explicit selection criteria used to evaluate this wedge (e.g. breadth across segments, pain impact, data or resource availability, buildability). Rank all options in a comparison table and recommend the strongest wedge with clear rationale. Save to {output_folder}/{venture_name}/define-solution/wedge-definition.md">[WH] Wedge Hypothesis — Generate, score, and rank wedge options with explicit selection criteria</item>
+  <item cmd="VP or fuzzy match on value-props or value-proposition" action="Run value proposition sprint. Load wedge-definition.md and icp-profile.md. Generate 5+ value proposition statements. For each: articulate the customer pain addressed, the unique value delivered, and the differentiation vs. alternatives. Save to {output_folder}/{venture_name}/define-solution/value-proposition.md">[VP] Value Propositions — Generate and rank value propositions for the wedge</item>
+  <item cmd="CC or fuzzy match on concept-cards" action="Create concept cards for customer testing. Load value-proposition.md. Using the template at {project-root}/ventureOS/templates/concept-card.md, create 3-5 concept cards representing different solution directions. Each card: problem statement, solution concept, key benefit, differentiator, visual description. Save to {output_folder}/{venture_name}/define-solution/concept-cards/">[CC] Concept Cards — Create testable concept cards for customer interviews</item>
   <item cmd="FA or fuzzy match on feasibility or technical-feasibility" workflow="{project-root}/ventureOS/workflows/4-define-solution/feasibility-assessment/workflow.yaml">[FA] Feasibility Assessment — Technical feasibility, ecosystem mapping, build/buy/partner/invest analysis</item>
   <item cmd="TA or fuzzy match on tech-architecture or architecture or system-design" action="Design the high-level technical architecture. Load wedge-definition.md, value-proposition.md, and solution-feasibility.md. Produce:
     (1) Architecture overview — a layered description of the full system from data ingestion to user interface, written in plain language with the role of each layer clearly stated.
@@ -89,9 +89,9 @@ These are your operating instructions for this VentureOS session. You are Claude
     (3) Build vs. buy rationale — for each layer: what the venture builds (core IP and competitive moat), what it buys or uses off-the-shelf (commodity components, faster with vendors), what it integrates (ecosystem leverage). Make explicit where 'build the intelligence, buy the plumbing' applies.
     (4) Key technical risks — top 3 technical assumptions that could break the architecture, with mitigation approaches.
     (5) MVP architecture scope — the minimal subset of the full architecture needed to run the first pilot. What can be manual, mocked, or deferred.
-    Save to {output_folder}/{venture_name}/technical-architecture.md and update venture-state.yaml.">[TA] Technical Architecture — Layered system design, build/buy rationale, MVP scope</item>
+    Save to {output_folder}/{venture_name}/define-solution/technical-architecture.md and update venture-state.yaml.">[TA] Technical Architecture — Layered system design, build/buy rationale, MVP scope</item>
   <item cmd="PR or fuzzy match on prototype or vibe-code" action="Guide vibe coding of an early wedge product. Load wedge-definition.md, value-proposition.md, and technical-architecture.md if it exists. Reference the 'vibe-code-wedge' tool from {project-root}/ventureOS/techniques/synthetic-tools.csv. Provide step-by-step prompts for using Claude Code / Cursor / Replit to build the earliest testable version of the wedge product. Generate the core feature specification and prompting guidance.">[PR] Prototype — Vibe code an early wedge product (AI-assisted rapid prototyping)</item>
-  <item cmd="VS or fuzzy match on vision-story" action="Create the From/To vision story. Load all solution artifacts. Using the template at {project-root}/ventureOS/templates/vision-story.md, articulate: the world before the solution (pain state), the world after (transformed state), and the venture's role in the shift. Save to {output_folder}/{venture_name}/vision-story.md">[VS] Vision Story — Craft the From/To transformation story</item>
+  <item cmd="VS or fuzzy match on vision-story" action="Create the From/To vision story. Load all solution artifacts. Using the template at {project-root}/ventureOS/templates/vision-story.md, articulate: the world before the solution (pain state), the world after (transformed state), and the venture's role in the shift. Save to {output_folder}/{venture_name}/define-solution/vision-story.md">[VS] Vision Story — Craft the From/To transformation story</item>
   <item cmd="RM or fuzzy match on roadmap or product-roadmap" action="Create a multi-dimensional product roadmap. Load wedge-definition.md, value-proposition.md, solution-feasibility.md, and technical-architecture.md if it exists. Structure the roadmap across three phases (Validate / Automate / Scale) and the following dimensions — for each cell state the specific objective and 1-3 concrete deliverables:
     - Data &amp; Integrations: what data sources are connected per phase, what connectors are built, how data coverage expands.
     - Intelligence: what models or analytical capabilities are live per phase, how the intelligence matures (rule-based → ML → autonomous recommendations).
@@ -99,7 +99,7 @@ These are your operating instructions for this VentureOS session. You are Claude
     - Infrastructure: deployment model, security posture, scalability investments per phase.
     - Asset Classes / Verticals: which customer segments, use cases, or geographies are targeted per phase — start narrow, expand deliberately.
     Also include: milestone timeline (Month 0 / Month 6 / Month 12 / Month 24), the scaling hypothesis connecting each phase to the next, and the per-phase success metrics that must be hit before advancing.
-    Save to {output_folder}/{venture_name}/product-roadmap.md and update venture-state.yaml.">[RM] Product Roadmap — Multi-dimensional: Data/Intelligence/UX/Infra/Verticals per phase</item>
+    Save to {output_folder}/{venture_name}/define-solution/product-roadmap.md and update venture-state.yaml.">[RM] Product Roadmap — Multi-dimensional: Data/Intelligence/UX/Infra/Verticals per phase</item>
   <item cmd="MH or fuzzy match on menu or help">[MH] Redisplay Menu</item>
   <item cmd="CH or fuzzy match on chat">[CH] Chat with Product about solution design and wedge strategy</item>
   <item cmd="DA or fuzzy match on exit, leave, goodbye or dismiss agent">[DA] Dismiss Agent</item>

package/config.yaml

@@ -8,6 +8,14 @@ user_name: ""
 # Active venture name — leave blank to start a new venture
 venture_name: ""
 
+# Program context (set automatically — do not edit manually)
+# program_name: name of the incubator/accelerator/innovation program
+# venture_context: independent | org
+# program_type: A=Incubator/Accelerator | C=Corporate Innovation | R=Research Commercialization | S=Venture Studio
+program_name: ""
+venture_context: ""
+program_type: ""
+
 # Language for all agent communication
 # Options: English | French | Arabic | Spanish | Portuguese | Other
 communication_language: "English"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ventureos",
-  "version": "1.1.21",
+  "version": "1.1.22",
   "description": "VentureOS — AI-powered venture building framework. From raw idea to validated venture — 12 weeks of structured ideation and incubation.",
   "type": "module",
   "bin": {

package/templates/conversion-analysis.md

@@ -30,17 +30,45 @@ GROWTH (expansion / renewal)
 
 ## Funnel Metrics by Channel
 
-| Stage | Metric | LinkedIn | Google | Email | Outbound | Total |
-|-------|--------|---------|--------|-------|---------|-------|
-| Awareness | Impressions | | | | | |
-| Interest | Clicks / Opens | | | | | |
-| Interest | CTR | | | | | |
-| Signup | Form fills | | | | | |
-| Signup | Conversion rate | | | | | |
-| Evaluation | Demo requests | | | | | |
-| Evaluation | Demos completed | | | | | |
-| Activation | Pilots started | | | | | |
-| Revenue | Paying customers | | | | | |
+**LinkedIn**
+- Awareness — Impressions:
+- Interest — Clicks / CTR:
+- Signup — Form fills / Conversion rate:
+- Evaluation — Demos requested / completed:
+- Activation — Pilots started:
+- Revenue — Paying customers:
+
+**Google**
+- Awareness — Impressions:
+- Interest — Clicks / CTR:
+- Signup — Form fills / Conversion rate:
+- Evaluation — Demos requested / completed:
+- Activation — Pilots started:
+- Revenue — Paying customers:
+
+**Email**
+- Awareness — Opens:
+- Interest — Clicks / CTR:
+- Signup — Form fills / Conversion rate:
+- Evaluation — Demos requested / completed:
+- Activation — Pilots started:
+- Revenue — Paying customers:
+
+**Outbound**
+- Awareness — Contacts reached:
+- Interest — Responses / CTR:
+- Signup — Form fills / Conversion rate:
+- Evaluation — Demos requested / completed:
+- Activation — Pilots started:
+- Revenue — Paying customers:
+
+**Totals (all channels)**
+- Awareness impressions:
+- Interest clicks:
+- Signups:
+- Demos:
+- Pilots:
+- Paying customers:
 
 ---
 

package/templates/venture-brief.md

@@ -0,0 +1,111 @@
+# {venture_name} — Venture Brief
+<!-- VentureOS Entry Point — Victor updates this after every completed workflow -->
+<!-- Always read this first for the current state of the venture -->
+
+| | |
+|---|---|
+| **Phase** | {current_phase}/6 |
+| **Week** | {current_week} |
+| **Status** | {status} |
+| **Last Updated** | {date} |
+
+---
+
+## The Problem
+
+_(1-3 sentences: who experiences this pain, what it is, and why it matters now)_
+
+**Evidence label:** [ ] [V] Validated by real interviews  [ ] [P] Provisional — some signal  [ ] [A] Assumption — not yet tested
+
+---
+
+## The Solution
+
+_(1-3 sentences: the wedge — the smallest thing we are building first, and why)_
+
+**Wedge:** _(one-liner)_
+
+**Vision:** _(where this leads in 3-5 years)_
+
+---
+
+## Market
+
+- **TAM:** $___  [V/P/A]
+- **SAM:** $___  [V/P/A]
+- **SOM (Year 3):** $___  [V/P/A]
+- **ICP:** _(job title, company type, trigger event)_
+
+---
+
+## Evidence
+
+_(Key findings that support or challenge the venture. Label each: [V] = validated from real data/interviews, [P] = provisional from secondary research, [A] = assumption)_
+
+- [V/P/A] _(finding 1)_
+- [V/P/A] _(finding 2)_
+- [V/P/A] _(finding 3)_
+
+**Strongest signal:** _(the most convincing evidence we have right now)_
+
+**Biggest open question:** _(the assumption most likely to kill this venture if wrong)_
+
+---
+
+## Business Model
+
+- **Revenue model:** _(how we charge — subscription, usage, transaction)_
+- **ACV:** $___  [V/P/A]
+- **Gross margin:** ___%  [V/P/A]
+- **LTV:CAC:** ___  [V/P/A]
+
+---
+
+## Gate Status
+
+| Gate | Status | Decision | Date |
+|------|--------|----------|------|
+| Week 8 Check-in | Pending / Complete | GO / PIVOT / KILL / — | |
+| Week 12 Final | Pending / Complete | GO / PIVOT / KILL / — | |
+
+**Next step:** _(the single most important thing to do right now)_
+
+---
+
+## Artifacts
+
+_(Links to phase outputs — update as each workflow completes)_
+
+**setup-team/**
+- [ ] team-charter.md
+- [ ] mothership-asset-map.md
+
+**understand-market/**
+- [ ] market-map.md
+- [ ] competitive-analysis.md
+- [ ] market-sizing.md
+- [ ] stakeholder-map.md
+
+**find-pain/**
+- [ ] pain-hypothesis.md
+- [ ] interview-synthesis.md
+- [ ] pain-atomization.md
+- [ ] icp-profile.md
+- [ ] pain-journey-map.md
+
+**define-solution/**
+- [ ] wedge-definition.md
+- [ ] value-proposition.md
+- [ ] vision-story.md
+- [ ] product-roadmap.md
+
+**business-case/**
+- [ ] financial-model.md
+- [ ] experiment-plan.md
+- [ ] gate-evaluation.md
+- [ ] pitch/checkin-pitch.md
+
+**design-business/**
+- [ ] gtm-plan.md
+- [ ] market-experiment.md
+- [ ] pitch/pitch-deck.md

package/templates/venture-killer-risks.md

@@ -23,71 +23,298 @@
 
 ### Category 1: Market & Customer Risks
 
-| # | Risk | Likelihood | Impact | Score | Priority | Owner | Mitigation | Status |
-|---|------|-----------|--------|-------|---------|-------|-----------|--------|
-| M1 | Pain does not exist at scale | | | | | | | |
-| M2 | Market too small or declining | | | | | | | |
-| M3 | Customer won't pay what we need them to | | | | | | | |
-| M4 | Customer discovery fails to find ICP | | | | | | | |
-| M5 | [venture-specific market risk] | | | | | | | |
+**M1 — Pain does not exist at scale**
+- Likelihood (1-5):
+- Impact (1-5):
+- Score:
+- Priority: High / Medium / Low
+- Owner:
+- Mitigation:
+- Status:
+
+**M2 — Market too small or declining**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+**M3 — Customer won't pay what we need them to**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+**M4 — Customer discovery fails to find ICP**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+**M5 — [venture-specific market risk]**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+---
 
 ### Category 2: Competitive Risks
 
-| # | Risk | Likelihood | Impact | Score | Priority | Owner | Mitigation | Status |
-|---|------|-----------|--------|-------|---------|-------|-----------|--------|
-| C1 | Major competitor launches before us | | | | | | | |
-| C2 | Incumbent copies our wedge quickly | | | | | | | |
-| C3 | No defensible differentiation | | | | | | | |
-| C4 | [venture-specific competitive risk] | | | | | | | |
+**C1 — Major competitor launches before us**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+**C2 — Incumbent copies our wedge quickly**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+**C3 — No defensible differentiation**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+**C4 — [venture-specific competitive risk]**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+---
 
 ### Category 3: Technical / Product Risks
 
-| # | Risk | Likelihood | Impact | Score | Priority | Owner | Mitigation | Status |
-|---|------|-----------|--------|-------|---------|-------|-----------|--------|
-| T1 | Solution technically infeasible | | | | | | | |
-| T2 | Key partner/technology unavailable | | | | | | | |
-| T3 | Data access blocked | | | | | | | |
-| T4 | Prototype takes too long to build | | | | | | | |
-| T5 | [venture-specific tech risk] | | | | | | | |
+**T1 — Solution technically infeasible**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+**T2 — Key partner/technology unavailable**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+**T3 — Data access blocked**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+**T4 — Prototype takes too long to build**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+**T5 — [venture-specific tech risk]**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+---
 
 ### Category 4: Business Model Risks
 
-| # | Risk | Likelihood | Impact | Score | Priority | Owner | Mitigation | Status |
-|---|------|-----------|--------|-------|---------|-------|-----------|--------|
-| B1 | Unit economics never work | | | | | | | |
-| B2 | CAC too high relative to LTV | | | | | | | |
-| B3 | Revenue model not viable | | | | | | | |
-| B4 | [venture-specific business risk] | | | | | | | |
+**B1 — Unit economics never work**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+**B2 — CAC too high relative to LTV**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+**B3 — Revenue model not viable**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+**B4 — [venture-specific business risk]**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+---
 
 ### Category 5: Regulatory & Legal Risks
 
-| # | Risk | Likelihood | Impact | Score | Priority | Owner | Mitigation | Status |
-|---|------|-----------|--------|-------|---------|-------|-----------|--------|
-| R1 | Regulatory change blocks business model | | | | | | | |
-| R2 | IP conflict with mothership or third party | | | | | | | |
-| R3 | Data privacy / compliance blocker | | | | | | | |
-| R4 | [venture-specific regulatory risk] | | | | | | | |
+**R1 — Regulatory change blocks business model**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+**R2 — IP conflict with mothership or third party**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+**R3 — Data privacy / compliance blocker**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+**R4 — [venture-specific regulatory risk]**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+---
 
 ### Category 6: Mothership / Organizational Risks
 
-| # | Risk | Likelihood | Impact | Score | Priority | Owner | Mitigation | Status |
-|---|------|-----------|--------|-------|---------|-------|-----------|--------|
-| O1 | Mothership withdraws support or funding | | | | | | | |
-| O2 | Sponsor loses role or commitment | | | | | | | |
-| O3 | Team capability gap | | | | | | | |
-| O4 | Internal politics slow progress | | | | | | | |
+**O1 — Mothership withdraws support or funding**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+**O2 — Sponsor loses role or commitment**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+**O3 — Team capability gap**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
+
+**O4 — Internal politics slow progress**
+- Likelihood:
+- Impact:
+- Score:
+- Priority:
+- Owner:
+- Mitigation:
+- Status:
 
 ---
 
 ## Top 5 Venture Killer Risks (Prioritized)
 
-| Priority | Risk ID | Risk Description | Score | Mitigation Action | Owner | Deadline |
-|---------|--------|-----------------|-------|------------------|-------|---------|
-| 1 | | | | | | |
-| 2 | | | | | | |
-| 3 | | | | | | |
-| 4 | | | | | | |
-| 5 | | | | | | |
+**#1 — [Risk ID]:**
+- Description:
+- Score:
+- Mitigation action:
+- Owner:
+- Deadline:
+
+**#2 — [Risk ID]:**
+- Description:
+- Score:
+- Mitigation action:
+- Owner:
+- Deadline:
+
+**#3 — [Risk ID]:**
+- Description:
+- Score:
+- Mitigation action:
+- Owner:
+- Deadline:
+
+**#4 — [Risk ID]:**
+- Description:
+- Score:
+- Mitigation action:
+- Owner:
+- Deadline:
+
+**#5 — [Risk ID]:**
+- Description:
+- Score:
+- Mitigation action:
+- Owner:
+- Deadline:
 
 ---
 

package/venture-master.md

@@ -11,14 +11,14 @@ These are your operating instructions for this VentureOS session. You are Claude
   <step n="1">Load persona from this current agent file (already in context)</step>
   <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
     - Load and read {project-root}/ventureOS/config.yaml NOW
-    - Store ALL fields as session variables: {venture_name}, {user_name}, {communication_language}, {output_folder}, {research_depth}, {llm}, {default_mode}, {region}
+    - Store ALL fields as session variables: {venture_name}, {program_name}, {venture_context}, {program_type}, {user_name}, {communication_language}, {output_folder}, {research_depth}, {llm}, {default_mode}, {region}
     - VERIFY: If config not loaded, STOP and report: "Config not found. Please ensure ventureOS/config.yaml exists in your project root and has user_name filled in."
     - DO NOT PROCEED to step 3 until config is successfully loaded
   </step>
   <step n="3">Load venture state: read {project-root}/ventureOS/_memory/venture-state.yaml — store {current_phase}, {current_week}, {entry_point}, {pivot_count}, {status}</step>
   <step n="4">Greet {user_name} in {communication_language}. Then:
 
-IF venture_name is empty (first run) → skip the status table and the menu entirely. Instead show only:
+IF venture_name is empty AND program_name is empty (first run) → skip the status table and the menu entirely. Instead show only:
 
 ---
 ### VentureOS
@@ -30,8 +30,9 @@ Are you building **as a founder** (one venture, hands-on), or running **a progra
 
 Then STOP and wait. Process the answer as:
 - Any form of "founder" / "solo" / "one venture" / "building" → ask: "Would you like to **start a new venture**, or **explore a domain** first?" → trigger NV or EX accordingly
-- Any form of "program" / "incubator" / "accelerator" / "lab" / "organization" / "portfolio" → trigger the program-setup prompt: ask program name, program type ([A] Incubator/Accelerator | [C] Corporate Innovation / EIR | [R] Research Commercialization | [S] Venture Studio), then show PO (Portfolio Overview)
+- Any form of "program" / "incubator" / "accelerator" / "lab" / "organization" / "portfolio" → trigger the program-setup prompt: ask program name, ask program type ([A] Incubator/Accelerator | [C] Corporate Innovation / EIR | [R] Research Commercialization | [S] Venture Studio), then write program_name + venture_context: "org" + program_type to config.yaml, then show PO (Portfolio Overview)
 
+IF program_name is set AND venture_name is empty → show the program banner (no active venture yet) and proceed to step 5.
 IF venture_name is set → display the venture context banner and proceed to step 5.
 IF venture_context is "org" → show the program banner with portfolio summary:
 
@@ -39,10 +40,10 @@ IF venture_context is "org" → show the program banner with portfolio summary:
 ### VentureOS — Program Dashboard
 | | |
 |---|---|
-| **Active Venture** | {venture_name} |
+| **Program** | {program_name} |
+| **Active Venture** | {venture_name} _(type `PO` to switch)_ |
 | **Phase** | {current_phase} · Week {current_week} |
 | **Status** | {status} |
-| **Portfolio** | Type `PO` to see all ventures in your program |
 ---
 
 IF venture_context is "independent" → show the standard banner:
@@ -122,6 +123,23 @@ _Type a number or a command (e.g. **NV**, **FP**, "market research", "start a ve
     <r>After any NVB gate decision: read the updated venture-state.yaml gate_history. If PIVOT — execute the pivot-archive prompt. If KILL — execute pivot-archive and set status to "killed". If GO — announce the conditions NVB attached and ask the team to confirm they are clear before continuing.</r>
     <r>EVIDENCE REGISTRY RULE: Every time an agent produces any output containing numbers, Victor must verify the output was cross-checked against {output_folder}/{venture_name}/evidence-registry.yaml before it was saved. If a number appears in an output that is NOT in the registry, remind the agent to register it and update the registry. If a number in the output CONFLICTS with the registry, flag it immediately: "⚠️ Consistency check: [metric] shows [value] but the Evidence Registry has [registered value]. Which is correct?"</r>
     <r>ASSUMPTION ALERT RULE: When reviewing any output or when a user reports an error, scan for [A] labels. If Phase ≥ 5 and [A] labels are present on key metrics (pricing, ACV, market size, unit economics), warn: "⚠️ These metrics are still unvalidated assumptions ([A]) and will be challenged by NVB at the gate. Recommend validating before the gate."</r>
+    <r>OUTPUT FOLDER STRUCTURE — All agents MUST save outputs to these phase subfolders under {output_folder}/{venture_name}/. This is the authoritative structure:
+    - venture-brief.md (root, always current) — Victor updates this after every completed workflow
+    - setup-team/ → team-charter.md, operating-plan.md, mothership-asset-map.md
+    - understand-market/ → market-map.md, competitive-analysis.md, market-sizing.md, stakeholder-map.md
+    - find-pain/ → pain-hypothesis.md, icp-profile.md, interview-synthesis.md, pain-atomization.md, pain-journey-map.md, interviews/
+    - define-solution/ → wedge-definition.md, value-proposition.md, vision-story.md, solution-feasibility.md, product-roadmap.md, concept-cards/, prototype/
+    - business-case/ → business-model-canvas.md, financial-model.md, pricing-model.md, experiment-plan.md, gate-evaluation.md, pitch/checkin-pitch.md
+    - design-business/ → gtm-plan.md, pilot-pipeline.md, market-experiment.md, pitch/pitch-deck.md, pitch/deck.html
+    Example: pain-hypothesis.md → {output_folder}/{venture_name}/find-pain/pain-hypothesis.md</r>
+    <r>TABLE FORMATTING RULE — Max 6 columns in any markdown table. For any item with 7 or more attributes, use structured sections instead of a table row:
+
+    **Item Name**
+    - Attribute 1: value
+    - Attribute 2: value
+    - Attribute 3: value
+
+    Apply this rule to ALL generated output.</r>
   </rules>
 
   <prompts>
@@ -139,9 +157,9 @@ _Type a number or a command (e.g. **NV**, **FP**, "market research", "start a ve
       Start a new venture:
       1. Ask for the venture name
       2. Ask for entry point: [D] Domain (I have a domain to explore) | [I] Idea (I have a specific idea)
-      3. Ask for venture context: [S] Solo / independent (solo founder or small startup team) | [O] Within an organization (incubator, accelerator, corporate innovation, research commercialization, venture studio)
+      3. If venture_context is not already set in config.yaml: ask for venture context: [S] Solo / independent | [O] Within an organization
          Store as {venture_context}: "independent" | "org"
-      4. If org context: ask for program type:
+      4. If org context and program_type not already set: ask for program type:
          [A] Incubator / Accelerator — managing a portfolio of startups through a structured program
          [C] Corporate Innovation / EIR — internal venture building within a parent organization
          [R] Research Commercialization — turning academic IP or research into a venture
@@ -150,7 +168,7 @@ _Type a number or a command (e.g. **NV**, **FP**, "market research", "start a ve
          - program_type "A" or "R": Victor frames outputs as portfolio artifacts, emphasizes gate decisions and standardized evaluation across ventures
          - program_type "C": Victor emphasizes mothership assets and sponsor alignment
          - program_type "S": Victor emphasizes speed and parallel validation
-      5. Update {project-root}/ventureOS/config.yaml — set venture_name
+      5. Update {project-root}/ventureOS/config.yaml — set venture_name ONLY (never overwrite program_name, venture_context, or program_type)
       6. Create {project-root}/ventureOS/_memory/venture-state.yaml with initial state (phase: 0 or 1, venture_context: {venture_context}, program_type: {program_type}, status: active)
       7. Create output folder: {output_folder}/{venture_name}/
       8. Initialize the Evidence Registry: copy {project-root}/ventureOS/templates/evidence-registry.yaml to {output_folder}/{venture_name}/evidence-registry.yaml — set venture_name and last_updated. Tell the user: "Evidence Registry initialized. Every number generated by VentureOS will be registered here and cross-checked for consistency across all your documents."

package/workflows/3-find-pain/customer-pain-discovery/step-1-pain-hypothesis.md

@@ -82,7 +82,7 @@ Consolidate findings into `social-signal-scan.md`:
 - Do NOT use these as interview substitutes — use them to sharpen hypotheses
 ```
 
-Save to: `{output_folder}/{venture_name}/social-signal-scan.md`
+Save to: `{output_folder}/{venture_name}/find-pain/social-signal-scan.md`
 
 Register the top 3–5 quantitative signals (e.g. "X% of G2 reviews mention Y") in the evidence registry as `[B]` entries.
 
@@ -124,7 +124,7 @@ Work with the user to sharpen the pain hypothesis:
 **Prioritization rationale:**
 - Why is the primary hypothesis the most promising to test first?
 
-Save updates to `{output_folder}/{venture_name}/pain-hypothesis.md`.
+Save updates to `{output_folder}/{venture_name}/find-pain/pain-hypothesis.md`.
 
 ---
 
@@ -138,7 +138,7 @@ Define the interview target list:
 5. **Outreach message:** (brief, value-exchange framing — "I want to learn from your experience, not sell anything")
 6. **Timeline:** First batch of ___ interviews by Week ___
 
-Create `{output_folder}/{venture_name}/interview-outreach-plan.md` with the target list and approach.
+Create `{output_folder}/{venture_name}/find-pain/interview-outreach-plan.md` with the target list and approach.
 
 ---
 
@@ -153,7 +153,7 @@ Based on the pain hypothesis and stakeholder map, generate interview scripts usi
 **Script 2: Expert Interview Script** (for domain experts who can validate prevalence)
 - Tailor to elicit: how common is this pain? What do most companies do about it?
 
-Save scripts to `{output_folder}/{venture_name}/interview-scripts/`.
+Save scripts to `{output_folder}/{venture_name}/find-pain/interview-scripts/`.
 
 ---
 

package/workflows/3-find-pain/customer-pain-discovery/step-3-synthesis.md

@@ -87,8 +87,8 @@ Using the `interview-synthesis.md` template, produce the batch synthesis report:
 - Quotes bank
 - Next steps
 
-Save: `{output_folder}/{venture_name}/interview-synthesis-batch-{N}.md`
-Update cumulative synthesis: `{output_folder}/{venture_name}/interview-synthesis.md`
+Save: `{output_folder}/{venture_name}/find-pain/interview-synthesis-batch-{N}.md`
+Update cumulative synthesis: `{output_folder}/{venture_name}/find-pain/interview-synthesis.md`
 
 ---
 

package/workflows/3-find-pain/customer-pain-discovery/step-4-pain-atomization.md

@@ -110,7 +110,7 @@ Using the `pain-atomization.md` template, fill in the full matrix:
 - FIP ranking summary
 - Prioritized pain to solve with rationale
 
-Save: `{output_folder}/{venture_name}/pain-atomization.md`
+Save: `{output_folder}/{venture_name}/find-pain/pain-atomization.md`
 Update `pain-hypothesis.md` with refined primary pain.
 Update `venture-state.yaml`: hypotheses.problem, completed_artifacts.
 

package/workflows/3-find-pain/customer-pain-discovery/step-5-pain-journey-map.md

@@ -92,10 +92,10 @@ Who explicitly does NOT fit? (Helps focus GTM.)
 Save all final documents:
 
 **Pain Journey Map:**
-Save: `{output_folder}/{venture_name}/pain-journey-map.md`
+Save: `{output_folder}/{venture_name}/find-pain/pain-journey-map.md`
 
 **ICP Profile:**
-Save: `{output_folder}/{venture_name}/icp-profile.md`
+Save: `{output_folder}/{venture_name}/find-pain/icp-profile.md`
 
 **Update venture-state.yaml:**
 - `hypotheses.customer` → update with final ICP definition

package/workflows/4-define-solution/wedge-design/step-2-value-propositions.md

@@ -32,7 +32,7 @@ For each concept card:
 - Unlike alternatives section
 - Visual description for interview use
 
-Save cards to `{output_folder}/{venture_name}/concept-cards/card-{N}.md`
+Save cards to `{output_folder}/{venture_name}/define-solution/concept-cards/card-{N}.md`
 
 ---
 

package/workflows/4-define-solution/wedge-design/step-3-prototype.md

@@ -60,7 +60,7 @@ Prompt 2 (Core feature):
 Prompt 3 (UI/UX):
 > "Style this for [ICP context — e.g., enterprise SaaS, clean and minimal]. Add [specific UI elements]."
 
-Produce a prompting guide with 5-8 prompts that will build the prototype when used in Claude Code / Cursor. Save to `{output_folder}/{venture_name}/prototype/build-guide.md`.
+Produce a prompting guide with 5-8 prompts that will build the prototype when used in Claude Code / Cursor. Save to `{output_folder}/{venture_name}/define-solution/prototype/build-guide.md`.
 
 ---
 

package/workflows/4-define-solution/wedge-design/step-4-solution-testing.md

@@ -60,7 +60,7 @@ Using the `product-roadmap.md` template, create the wedge-to-vision roadmap:
 
 Note what we explicitly are NOT building in Phase 1.
 
-Save: `{output_folder}/{venture_name}/product-roadmap.md`
+Save: `{output_folder}/{venture_name}/define-solution/product-roadmap.md`
 
 ---
 
@@ -71,7 +71,7 @@ Using the `vision-story.md` template, write the From/To narrative:
 - ACT 2: The shift — the enabling insight / technology
 - ACT 3: The world after — the transformed customer experience
 
-Save: `{output_folder}/{venture_name}/vision-story.md`
+Save: `{output_folder}/{venture_name}/define-solution/vision-story.md`
 
 ---
 

package/workflows/5-business-case/checkin-pitch/step-1-evidence-compilation.md

@@ -71,7 +71,7 @@ Write a 1-page evidence brief:
 - What we still don't know (honest gaps)
 - Our recommendation: do we think we should proceed to Phase 6?
 
-Save: `{output_folder}/{venture_name}/checkin-evidence.md`
+Save: `{output_folder}/{venture_name}/business-case/checkin-evidence.md`
 
 ---
 

package/workflows/5-business-case/checkin-pitch/step-2-pitch-creation.md

@@ -80,7 +80,7 @@ Present draft to user slide by slide. Ask:
 
 ## 2.4 Save Deck
 
-Save: `{output_folder}/{venture_name}/pitch/checkin-pitch.md`
+Save: `{output_folder}/{venture_name}/business-case/pitch/checkin-pitch.md`
 
 ---
 

package/workflows/5-business-case/checkin-pitch/step-3-nvb-review.md

@@ -102,7 +102,7 @@ Produce the NVB check-in decision record:
 
 ## 3.5 Update Venture State
 
-Save: `{output_folder}/{venture_name}/pitch/checkin-nvb-decision.md`
+Save: `{output_folder}/{venture_name}/business-case/pitch/checkin-nvb-decision.md`
 
 Update `venture-state.yaml`:
 - `gate_history[0].date` and `gate_history[0].decision`

package/workflows/6-design-business/final-pitch/step-1-narrative.md

@@ -33,7 +33,7 @@ Load or create the vision story using `vision-story.md` template:
 - Is every claim backed by evidence from the venture's research?
 - Is the vision big enough but grounded in the wedge?
 
-Save: `{output_folder}/{venture_name}/vision-story.md` (final version)
+Save: `{output_folder}/{venture_name}/define-solution/vision-story.md` (final version)
 
 ---
 
@@ -49,7 +49,7 @@ Using all available data:
 5. Cash flow: burn rate, break-even month, funding requirements
 6. Use of proceeds: how the raise will be allocated
 
-Save: `{output_folder}/{venture_name}/financial-model.md`
+Save: `{output_folder}/{venture_name}/business-case/financial-model.md`
 
 ---
 

package/workflows/6-design-business/final-pitch/step-2-slides.md

@@ -118,4 +118,4 @@ Before declaring the deck complete:
 
 ---
 
-Save: `{output_folder}/{venture_name}/pitch/pitch-deck.md`
+Save: `{output_folder}/{venture_name}/design-business/pitch/pitch-deck.md`

package/workflows/6-design-business/final-pitch/step-3-excalidraw.md

@@ -79,13 +79,13 @@ Using the investor-qa.md (from pitch-master.md [QA] menu item), generate the 15
 
 For each question: provide a confident, evidence-backed suggested answer.
 
-Save: `{output_folder}/{venture_name}/pitch/investor-qa.md`
+Save: `{output_folder}/{venture_name}/design-business/pitch/investor-qa.md`
 
 ---
 
 ## 3.5 Save All Pitch Assets
 
-Save Excalidraw frames: `{output_folder}/{venture_name}/pitch/excalidraw-frames.md`
+Save Excalidraw frames: `{output_folder}/{venture_name}/design-business/pitch/excalidraw-frames.md`
 
 **Checkpoint:**
 **GUIDED MODE:** Review visual frame descriptions with user. Ask: "Are these the right visuals? Any slide you want to visualize differently?"

package/workflows/6-design-business/final-pitch/step-4-nvb-final-review.md

@@ -113,8 +113,8 @@ Save gate evaluation to `gate-evaluation.md` using the template.
 
 ## 4.6 Save Final Gate Record
 
-Save: `{output_folder}/{venture_name}/pitch/final-nvb-decision.md`
-Save: `{output_folder}/{venture_name}/gate-evaluation.md`
+Save: `{output_folder}/{venture_name}/design-business/pitch/final-nvb-decision.md`
+Save: `{output_folder}/{venture_name}/business-case/gate-evaluation.md`
 
 Update `venture-state.yaml`:
 - `gate_history[1].date`, `gate_history[1].score`, `gate_history[1].decision`

package/workflows/6-design-business/market-experiments/step-1-gtm-plan.md

@@ -28,7 +28,7 @@ Using the `messaging-infrastructure.md` template, build the full messaging stack
 5. **Objection-handling map** (5 key objections + responses)
 6. **Channel-specific messaging:** LinkedIn outreach, cold email, landing page, paid ads
 
-Save: `{output_folder}/{venture_name}/messaging-infrastructure.md`
+Save: `{output_folder}/{venture_name}/design-business/messaging-infrastructure.md`
 
 ---
 
@@ -42,7 +42,7 @@ Using the `market-experiment.md` template (GTM section):
 4. **CAC hypothesis by channel** (what do we expect to pay per acquired customer?)
 5. **90-day GTM playbook** (weeks 10-12: what happens in each week?)
 
-Save GTM plan to: `{output_folder}/{venture_name}/market-experiment.md` (GTM section)
+Save GTM plan to: `{output_folder}/{venture_name}/design-business/market-experiment.md` (GTM section)
 
 ---
 
@@ -55,7 +55,7 @@ Using the `sales-process-map.md` template:
 4. Identify typical objections and responses
 5. Set sales KPI targets for Weeks 10-12
 
-Save: `{output_folder}/{venture_name}/sales-process-map.md`
+Save: `{output_folder}/{venture_name}/design-business/sales-process-map.md`
 
 ---
 

package/workflows/6-design-business/market-experiments/step-2-landing-page.md

@@ -48,7 +48,7 @@ Generate prompting guidance for building the landing page with Claude Code / Cur
 **Prompt 4 (Analytics):**
 > "Add Google Analytics / Plausible / simple event tracking to track: page views, time on page, CTA clicks, form submissions."
 
-Save: `{output_folder}/{venture_name}/landing-page-spec.md`
+Save: `{output_folder}/{venture_name}/design-business/landing-page-spec.md`
 
 ---
 
@@ -73,7 +73,7 @@ For **Retargeting / Remarketing:**
 
 Include: targeting parameters for each ad variant (LinkedIn job titles, company sizes, industries).
 
-Save: `{output_folder}/{venture_name}/ad-variants.md`
+Save: `{output_folder}/{venture_name}/design-business/ad-variants.md`
 
 ---
 

package/workflows/6-design-business/market-experiments/step-4-measure.md

@@ -106,8 +106,8 @@ Compile all experiment data into the `market-experiment.md` template (Results se
 Also complete `conversion-analysis.md` template with all funnel data.
 
 Save:
-- `{output_folder}/{venture_name}/market-experiment.md`
-- `{output_folder}/{venture_name}/conversion-analysis.md`
+- `{output_folder}/{venture_name}/design-business/market-experiment.md`
+- `{output_folder}/{venture_name}/design-business/conversion-analysis.md`
 
 Update `venture-state.yaml`:
 - `completed_artifacts` — market-experiment, conversion-analysis