ventureos 1.1.26 → 1.1.28

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}/find-pain/ and update venture-state.yaml.</r>
+    <r>After producing outputs, save to {output_folder}/{venture_name}/03-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}/find-pain/interviews/synthetic/
+      Save to {output_folder}/{venture_name}/03-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}/find-pain/interviews/
+      Save to {output_folder}/{venture_name}/03-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}/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="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}/03-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}/03-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}/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="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}/03-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}/03-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}/03-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}/understand-market/ and update venture-state.yaml.</r>
+    <r>After producing research outputs, save to {output_folder}/{venture_name}/02-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}/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="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}/02-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}/understand-market/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}/02-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}/define-solution/ and update venture-state.yaml.</r>
+    <r>After producing outputs, save to {output_folder}/{venture_name}/04-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}/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="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}/04-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}/04-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}/04-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}/define-solution/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}/04-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}/define-solution/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}/04-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}/define-solution/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}/04-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/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ventureos",
-  "version": "1.1.26",
+  "version": "1.1.28",
   "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/venture-brief.md

@@ -76,36 +76,36 @@ _(Key findings that support or challenge the venture. Label each: [V] = validate
 
 _(Links to phase outputs — update as each workflow completes)_
 
-**setup-team/**
+**01-setup-team/**
 - [ ] team-charter.md
 - [ ] mothership-asset-map.md
 
-**understand-market/**
+**02-understand-market/**
 - [ ] market-map.md
 - [ ] competitive-analysis.md
 - [ ] market-sizing.md
 - [ ] stakeholder-map.md
 
-**find-pain/**
+**03-find-pain/**
 - [ ] pain-hypothesis.md
 - [ ] interview-synthesis.md
 - [ ] pain-atomization.md
 - [ ] icp-profile.md
 - [ ] pain-journey-map.md
 
-**define-solution/**
+**04-define-solution/**
 - [ ] wedge-definition.md
 - [ ] value-proposition.md
 - [ ] vision-story.md
 - [ ] product-roadmap.md
 
-**business-case/**
+**05-business-case/**
 - [ ] financial-model.md
 - [ ] experiment-plan.md
 - [ ] gate-evaluation.md
 - [ ] pitch/checkin-pitch.md
 
-**design-business/**
+**06-design-business/**
 - [ ] gtm-plan.md
 - [ ] market-experiment.md
 - [ ] pitch/pitch-deck.md

package/venture-master.md

@@ -115,14 +115,14 @@ _Type a number or a command (e.g. **NV**, **FP**, "market research", "start a ve
     <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
-    - domain-research/ → market-landscape.md, competitive-analysis.md, market-sizing.md, domain-scan.md (Phase 0 / EX outputs)
-    - 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 (Phase 2 / UM outputs)
-    - 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>
+    - 00-domain-research/ → market-landscape.md, competitive-analysis.md, market-sizing.md, domain-scan.md (Phase 0 / EX outputs)
+    - 01-setup-team/ → team-charter.md, operating-plan.md, mothership-asset-map.md
+    - 02-understand-market/ → market-map.md, competitive-analysis.md, market-sizing.md, stakeholder-map.md (Phase 2 / UM outputs)
+    - 03-find-pain/ → pain-hypothesis.md, icp-profile.md, interview-synthesis.md, pain-atomization.md, pain-journey-map.md, interviews/
+    - 04-define-solution/ → wedge-definition.md, value-proposition.md, vision-story.md, solution-feasibility.md, product-roadmap.md, concept-cards/, prototype/
+    - 05-business-case/ → business-model-canvas.md, financial-model.md, pricing-model.md, experiment-plan.md, gate-evaluation.md, pitch/checkin-pitch.md
+    - 06-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}/03-find-pain/pain-hypothesis.md</r>
     <r>TABLE FORMATTING RULE — Two conditions must BOTH be met to use a markdown table:
     (1) Max 6 columns
     (2) Every cell contains 6 words or fewer — short labels, numbers, names, single phrases only

package/workflows/0-explore/domain-deep-dive/instructions.xml

@@ -26,7 +26,7 @@
 
       Cite all sources. Label AI-synthesized estimates clearly.
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/domain-research/market-landscape.md">
+    <template-output file="{output_folder}/{venture_name}/00-domain-research/market-landscape.md">
       Save a structured market landscape report.
     </template-output>
     <checkpoint>
@@ -47,7 +47,7 @@
       5. Note recent strategic moves: funding, acquisitions, product launches, partnerships
       6. Identify 2-3 areas where differentiation is possible
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/domain-research/competitive-analysis.md">
+    <template-output file="{output_folder}/{venture_name}/00-domain-research/competitive-analysis.md">
       Save competitive analysis with differentiation map.
     </template-output>
     <checkpoint>
@@ -67,7 +67,7 @@
       4. Note market growth rate (CAGR) from credible sources
       5. Flag if market is too small (&lt;$100M TAM) — potential kill signal
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/domain-research/market-sizing.md">
+    <template-output file="{output_folder}/{venture_name}/00-domain-research/market-sizing.md">
       Save market sizing with all sources cited.
     </template-output>
   </step>
@@ -83,7 +83,7 @@
       4. For each pain: who experiences it, rough FIP estimate, current workaround
       5. Rank pains by: FIP potential × market size × competitive white space
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/domain-research/pain-signals.md">
+    <template-output file="{output_folder}/{venture_name}/00-domain-research/pain-signals.md">
       Save ranked pain signal scan.
     </template-output>
   </step>
@@ -106,7 +106,7 @@
 
       Rank by overall opportunity score: market × pain × timing × differentiation potential
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/domain-research/opportunity-ranking.md">
+    <template-output file="{output_folder}/{venture_name}/00-domain-research/opportunity-ranking.md">
       Save ranked opportunity areas.
     </template-output>
     <checkpoint>
@@ -124,9 +124,10 @@
       2. Fill in: venture name/codename, challenge statement, market forces, starting hypotheses
       3. Set entry_point: "domain" in venture-state.yaml
       4. Initialize venture-state.yaml with the new venture details
-      5. Display to user: "Domain exploration complete. Here are your top opportunities — the strongest one is pre-selected. **Confirm or pick a different one, and we move straight into Phase 1: Understand the Market.**"
+      5. Display to user: "Domain exploration complete. Here are your top opportunities — the strongest one is pre-selected. **Confirm or pick a different one, and we move into Phase 2: Understand the Market.**"
+         Note: Phase 1 (Setup Team) is skipped — it is only relevant for corporate ventures that need a formal team charter and mothership sponsor. For domain-entry ventures, we go straight to Phase 2.
       6. Wait for user confirmation or selection.
-      7. Once confirmed: announce "Moving into Phase 1. Your domain research is loaded as the baseline — no need to repeat it." Then route to [UM] Understand the Market.
+      7. Once confirmed: announce "Skipping Phase 1 (team setup — not needed here). Moving into **Phase 2: Understand the Market** with your domain research already loaded as baseline." Then route to [UM] Understand the Market.
     </instructions>
     <template-output file="{output_folder}/{venture_name}/venture-canvas.md">
       Save venture canvas as starting artifact.

package/workflows/0-explore/domain-deep-dive/workflow.yaml

@@ -17,7 +17,7 @@ installed_path: "{project-root}/ventureOS/workflows/0-explore/domain-deep-dive"
 instructions: "{installed_path}/instructions.xml"
 
 # Output
-default_output_folder: "{output_folder}/{venture_name}/domain-research/"
+default_output_folder: "{output_folder}/{venture_name}/00-domain-research/"
 
 # Templates used
 templates:

package/workflows/1-setup-team/mothership-alignment/instructions.xml

@@ -63,7 +63,7 @@
       Prioritize: identify Top 3 Unfair Advantages. List assets to activate in next 30 days.
       Save to output folder. Update venture-state.yaml.
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/mothership-asset-map.md">
+    <template-output file="{output_folder}/{venture_name}/01-setup-team/mothership-asset-map.md">
       Save completed Mothership Asset Map.
     </template-output>
   </step>

package/workflows/1-setup-team/team-formation/instructions.xml

@@ -78,7 +78,7 @@
       Fill all sections. Review with user. Save to output folder.
       Update venture-state.yaml: mark team-charter as complete in category_progress.team.
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/team-charter.md">
+    <template-output file="{output_folder}/{venture_name}/01-setup-team/team-charter.md">
       Save completed Team Charter.
     </template-output>
     <state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">

package/workflows/2-understand-market/market-mapping/instructions.xml

@@ -29,7 +29,7 @@
       6. Flag: which competitors could pivot into our space if we find strong demand?
       Cite all sources. Apply research_depth setting.
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/competitive-analysis.md">
+    <template-output file="{output_folder}/{venture_name}/02-understand-market/competitive-analysis.md">
       Save competitive landscape report with differentiation map.
     </template-output>
     <checkpoint>
@@ -57,7 +57,7 @@
 
       Flag if TAM &lt; $100M — significant risk signal.
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/market-sizing.md">
+    <template-output file="{output_folder}/{venture_name}/02-understand-market/market-sizing.md">
       Save market sizing with both methodologies and all sources.
     </template-output>
   </step>
@@ -76,7 +76,7 @@
          - Economic shifts
       4. Assess: does the mothership have assets that lower key barriers?
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/market-landscape.md">
+    <template-output file="{output_folder}/{venture_name}/02-understand-market/market-landscape.md">
       Save full market landscape report including barriers and trends.
     </template-output>
   </step>

package/workflows/2-understand-market/stakeholder-identification/instructions.xml

@@ -65,7 +65,7 @@
       5. Interview target: who to interview first, how many, what types
       Use the pain-hypothesis.md template.
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/pain-hypothesis.md">
+    <template-output file="{output_folder}/{venture_name}/03-find-pain/pain-hypothesis.md">
       Save initial pain hypothesis with assumptions to test.
     </template-output>
   </step>
@@ -79,7 +79,7 @@
       Note which mothership relationships can be leveraged for access.
       Update venture-state.yaml with completed artifacts and guiding_questions.domain answers.
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/stakeholder-map.md">
+    <template-output file="{output_folder}/{venture_name}/02-understand-market/stakeholder-map.md">
       Save completed Stakeholder Map.
     </template-output>
     <state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">

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}/find-pain/social-signal-scan.md`
+Save to: `{output_folder}/{venture_name}/03-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}/find-pain/pain-hypothesis.md`.
+Save updates to `{output_folder}/{venture_name}/03-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}/find-pain/interview-outreach-plan.md` with the target list and approach.
+Create `{output_folder}/{venture_name}/03-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}/find-pain/interview-scripts/`.
+Save scripts to `{output_folder}/{venture_name}/03-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}/find-pain/interview-synthesis-batch-{N}.md`
-Update cumulative synthesis: `{output_folder}/{venture_name}/find-pain/interview-synthesis.md`
+Save: `{output_folder}/{venture_name}/03-find-pain/interview-synthesis-batch-{N}.md`
+Update cumulative synthesis: `{output_folder}/{venture_name}/03-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}/find-pain/pain-atomization.md`
+Save: `{output_folder}/{venture_name}/03-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}/find-pain/pain-journey-map.md`
+Save: `{output_folder}/{venture_name}/03-find-pain/pain-journey-map.md`
 
 **ICP Profile:**
-Save: `{output_folder}/{venture_name}/find-pain/icp-profile.md`
+Save: `{output_folder}/{venture_name}/03-find-pain/icp-profile.md`
 
 **Update venture-state.yaml:**
 - `hypotheses.customer` → update with final ICP definition

package/workflows/4-define-solution/feasibility-assessment/instructions.xml

@@ -36,7 +36,7 @@
       Score each option 1-5 on feasibility.
       Recommend a route (or hybrid approach).
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/solution-feasibility.md">
+    <template-output file="{output_folder}/{venture_name}/04-define-solution/solution-feasibility.md">
       Save feasibility analysis with all four routes evaluated.
     </template-output>
   </step>
@@ -55,7 +55,7 @@
 
       Use web search to identify technology players, platforms, and ecosystem participants.
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/ecosystem-map.md">
+    <template-output file="{output_folder}/{venture_name}/04-define-solution/ecosystem-map.md">
       Save ecosystem map with partnership candidates.
     </template-output>
   </step>

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}/define-solution/concept-cards/card-{N}.md`
+Save cards to `{output_folder}/{venture_name}/04-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}/define-solution/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}/04-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}/define-solution/product-roadmap.md`
+Save: `{output_folder}/{venture_name}/04-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}/define-solution/vision-story.md`
+Save: `{output_folder}/{venture_name}/04-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}/business-case/checkin-evidence.md`
+Save: `{output_folder}/{venture_name}/05-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}/business-case/pitch/checkin-pitch.md`
+Save: `{output_folder}/{venture_name}/05-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}/business-case/pitch/checkin-nvb-decision.md`
+Save: `{output_folder}/{venture_name}/05-business-case/pitch/checkin-nvb-decision.md`
 
 Update `venture-state.yaml`:
 - `gate_history[0].date` and `gate_history[0].decision`

package/workflows/5-business-case/initial-business-case/instructions.xml

@@ -35,7 +35,7 @@
       For each risk: likelihood (1-5), impact (1-5), risk score, priority, owner, mitigation action.
       Identify the Top 5 Venture Killer Risks and assign mitigation owners and deadlines.
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/venture-killer-risks.md">
+    <template-output file="{output_folder}/{venture_name}/05-business-case/venture-killer-risks.md">
       Save completed risk registry.
     </template-output>
   </step>
@@ -55,7 +55,7 @@
 
       This plan feeds directly into the check-in pitch.
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/experiment-plan.md">
+    <template-output file="{output_folder}/{venture_name}/05-business-case/experiment-plan.md">
       Save operating and experiment plan.
     </template-output>
   </step>

package/workflows/6-design-business/business-model-design/instructions.xml

@@ -35,7 +35,7 @@
       - Revenue Streams, Key Resources, Key Activities, Key Partnerships, Cost Structure
       Include unit economics summary: ACV, Gross Margin, LTV, CAC, LTV:CAC ratio, Payback Period.
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/business-model-canvas.md">
+    <template-output file="{output_folder}/{venture_name}/05-business-case/business-model-canvas.md">
       Save Business Model Canvas.
     </template-output>
   </step>
@@ -52,7 +52,7 @@
       5. Design a pricing validation experiment (landing page A/B, customer interview, pilot pricing)
       6. Calculate revenue implications per tier
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/pricing-model.md">
+    <template-output file="{output_folder}/{venture_name}/05-business-case/pricing-model.md">
       Save pricing model with tiers and validation plan.
     </template-output>
   </step>
@@ -71,7 +71,7 @@
 
       Update venture-state.yaml: completed_artifacts, guiding_questions.design_business
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/monetisation-plan.md">
+    <template-output file="{output_folder}/{venture_name}/05-business-case/monetisation-plan.md">
       Save monetisation plan.
     </template-output>
     <state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">

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}/define-solution/vision-story.md` (final version)
+Save: `{output_folder}/{venture_name}/04-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}/business-case/financial-model.md`
+Save: `{output_folder}/{venture_name}/05-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}/design-business/pitch/pitch-deck.md`
+Save: `{output_folder}/{venture_name}/06-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}/design-business/pitch/investor-qa.md`
+Save: `{output_folder}/{venture_name}/06-design-business/pitch/investor-qa.md`
 
 ---
 
 ## 3.5 Save All Pitch Assets
 
-Save Excalidraw frames: `{output_folder}/{venture_name}/design-business/pitch/excalidraw-frames.md`
+Save Excalidraw frames: `{output_folder}/{venture_name}/06-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}/design-business/pitch/final-nvb-decision.md`
-Save: `{output_folder}/{venture_name}/business-case/gate-evaluation.md`
+Save: `{output_folder}/{venture_name}/06-design-business/pitch/final-nvb-decision.md`
+Save: `{output_folder}/{venture_name}/05-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}/design-business/messaging-infrastructure.md`
+Save: `{output_folder}/{venture_name}/06-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}/design-business/market-experiment.md` (GTM section)
+Save GTM plan to: `{output_folder}/{venture_name}/06-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}/design-business/sales-process-map.md`
+Save: `{output_folder}/{venture_name}/06-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}/design-business/landing-page-spec.md`
+Save: `{output_folder}/{venture_name}/06-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}/design-business/ad-variants.md`
+Save: `{output_folder}/{venture_name}/06-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}/design-business/market-experiment.md`
-- `{output_folder}/{venture_name}/design-business/conversion-analysis.md`
+- `{output_folder}/{venture_name}/06-design-business/market-experiment.md`
+- `{output_folder}/{venture_name}/06-design-business/conversion-analysis.md`
 
 Update `venture-state.yaml`:
 - `completed_artifacts` — market-experiment, conversion-analysis

package/workflows/autopilot/autopilot.md

@@ -83,7 +83,7 @@ Run autonomously in research mode. Do not pause for checkpoints.
 - Flag white spaces: problems that exist but have no strong solution yet
 - Assess why now: what has changed in the last 2–3 years that creates an opening
 
-**Output:** Save as `{output_folder}/{venture_name}/domain-research/domain-scan.md`
+**Output:** Save as `{output_folder}/{venture_name}/00-domain-research/domain-scan.md`
 
 Header format:
 ```
@@ -109,7 +109,7 @@ Continue as Diana or reload if needed.
 - Key barriers to entry and how to navigate them
 - Identify the most underserved customer segment
 
-**Output:** Save as `{output_folder}/{venture_name}/understand-market/market-map.md`
+**Output:** Save as `{output_folder}/{venture_name}/02-understand-market/market-map.md`
 
 Header format:
 ```
@@ -155,7 +155,7 @@ Focus: pain prevalence across the market, why current solutions fail, what a bre
 ⚠️ SIMULATED INTERVIEW — AI-generated persona. Not real customer data.
 ```
 
-**Output:** Save as `{output_folder}/{venture_name}/find-pain/synthetic-interviews.md`
+**Output:** Save as `{output_folder}/{venture_name}/03-find-pain/synthetic-interviews.md`
 
 Update progress tracker: `[✓] Phase 2 — Customer Pain Discovery`
 
@@ -170,7 +170,7 @@ Update progress tracker: `[✓] Phase 2 — Customer Pain Discovery`
 - Select primary pain: highest FIP AND most aligned with domain opportunity
 - Define initial ICP: the persona profile that showed strongest, most consistent pain
 
-**Output:** Save as `{output_folder}/{venture_name}/find-pain/pain-atomization.md`
+**Output:** Save as `{output_folder}/{venture_name}/03-find-pain/pain-atomization.md`
 
 ---
 
@@ -192,7 +192,7 @@ Apply thresholds from `{project-root}/ventureOS/scoring/pain-scoring.yaml`:
 
 **If WEAK:** Revise the ICP hypothesis (try adjacent segment or reframe pain), re-run Steps 5–6 once. If still < 2.5 after second run → KILL.
 
-**If KILL:** Generate `{output_folder}/{venture_name}/find-pain/kill-decision.md` with:
+**If KILL:** Generate `{output_folder}/{venture_name}/03-find-pain/kill-decision.md` with:
 - Pain scores across all tested segments
 - Reason for kill: pain insufficient
 - What was learned
@@ -220,7 +220,7 @@ Run autonomously. Do not pause for checkpoints.
 - Outline prototype concept (what the earliest testable version looks like)
 - Map wedge → big vision scaling path
 
-**Output:** Save as `{output_folder}/{venture_name}/define-solution/solution-design.md`
+**Output:** Save as `{output_folder}/{venture_name}/04-define-solution/solution-design.md`
 
 Header:
 ```
@@ -253,7 +253,7 @@ Run autonomously.
 - Calculate unit economics: estimated CAC, LTV, LTV:CAC ratio
 - Identify key financial assumptions that need validation
 
-**Output:** Save as `{output_folder}/{venture_name}/business-case/business-case.md`
+**Output:** Save as `{output_folder}/{venture_name}/05-business-case/business-case.md`
 
 Header:
 ```
@@ -295,7 +295,7 @@ Each board member scores independently, then Eva calculates weighted average.
 | 2.5–3.49 | **PIVOT** — identify pivot type, revise |
 | < 2.5 | **KILL** — insufficient evidence |
 
-**Output:** Save as `{output_folder}/{venture_name}/business-case/gate-evaluation.md`
+**Output:** Save as `{output_folder}/{venture_name}/05-business-case/gate-evaluation.md`
 
 All output labeled:
 ```
@@ -319,7 +319,7 @@ All output labeled:
 - If second gate also results in PIVOT → downgrade to KILL and document
 
 **If KILL:**
-Generate `{output_folder}/{venture_name}/business-case/kill-decision.md` with full rationale.
+Generate `{output_folder}/{venture_name}/05-business-case/kill-decision.md` with full rationale.
 Display summary and return to main menu.
 
 Update progress tracker: `[✓] Gate 2 — Check-in`
@@ -340,7 +340,7 @@ Run autonomously.
 - Define success metrics for each experiment (what GO looks like)
 - Draft pilot customer outreach strategy: who to target, what to say
 
-**Output:** Save as `{output_folder}/{venture_name}/design-business/gtm-plan.md`
+**Output:** Save as `{output_folder}/{venture_name}/06-design-business/gtm-plan.md`
 
 Header:
 ```
@@ -392,7 +392,7 @@ Build a complete investor pitch deck. Use the narrative-first format for every s
 
 **Narrative arc rule:** Slides 1–3 build the villain (the problem). Slides 4–5 introduce the hero (the solution and timing). Slides 6–8 prove the business. Slides 9–10 close the deal.
 
-**Output:** Save as `{output_folder}/{venture_name}/design-business/pitch/pitch-deck.md`
+**Output:** Save as `{output_folder}/{venture_name}/06-design-business/pitch/pitch-deck.md`
 
 Header:
 ```
@@ -431,15 +431,15 @@ Display this summary to the user:
 >
 > | Output | File |
 > |---|---|
-> | Domain scan | `domain-research/domain-scan.md` |
-> | Market mapping | `understand-market/market-map.md` |
-> | Synthetic interviews | `find-pain/synthetic-interviews.md` |
-> | Pain atomization | `find-pain/pain-atomization.md` |
-> | Solution design | `define-solution/solution-design.md` |
-> | Business case | `business-case/business-case.md` |
-> | Check-in evaluation | `business-case/gate-evaluation.md` |
-> | GTM plan | `design-business/gtm-plan.md` |
-> | Pitch deck | `design-business/pitch/pitch-deck.md` |
+> | Domain scan | `00-domain-research/domain-scan.md` |
+> | Market mapping | `02-understand-market/market-map.md` |
+> | Synthetic interviews | `03-find-pain/synthetic-interviews.md` |
+> | Pain atomization | `03-find-pain/pain-atomization.md` |
+> | Solution design | `04-define-solution/solution-design.md` |
+> | Business case | `05-business-case/business-case.md` |
+> | Check-in evaluation | `05-business-case/gate-evaluation.md` |
+> | GTM plan | `06-design-business/gtm-plan.md` |
+> | Pitch deck | `06-design-business/pitch/pitch-deck.md` |
 > | **Venture Scan Report** | **`venture-scan-report.md`** ← start here |
 >
 > **Gate results:**