ventureos 1.1.23 → 1.1.24

package/package.json

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

package/venture-master.md

@@ -116,14 +116,18 @@ _Type a number or a command (e.g. **NV**, **FP**, "market research", "start a ve
     - 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:
+    <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
+
+    If EITHER condition fails — too many columns OR any cell has more than 6 words — use structured sections instead:
 
     **Item Name**
-    - Attribute 1: value
+    - Attribute 1: value (can be as long as needed)
     - Attribute 2: value
     - Attribute 3: value
 
-    Apply this rule to ALL generated output.</r>
+    Competitive analysis, stakeholder profiles, risk descriptions, and pain journey stages always use structured sections because their cells are naturally long. Apply this rule to ALL generated output without exception.</r>
   </rules>
 
   <prompts>
@@ -143,8 +147,8 @@ _Type a number or a command (e.g. **NV**, **FP**, "market research", "start a ve
       2. Ask for entry point: [D] Domain (I have a domain to explore) | [I] Idea (I have a specific idea)
       3. Update {project-root}/ventureOS/config.yaml — set venture_name
       4. Create {project-root}/ventureOS/_memory/venture-state.yaml with initial state (phase: 0 or 1, status: active)
-      5. Create output folder: {output_folder}/{venture_name}/
-      6. 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."
+      5. Create output folder: {project-root}/{output_folder}/{venture_name}/ — for example, if output_folder is "_ventures" and venture_name is "HydroLink", create {project-root}/_ventures/HydroLink/
+      6. Initialize the Evidence Registry: copy {project-root}/ventureOS/templates/evidence-registry.yaml to {project-root}/{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."
       7. Routing:
          - Domain entry → route to [EX] Explore Domain
          - Idea entry → route to [UM] Understand the Market