ventureos 1.1.28 → 1.1.30

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ventureos",
-  "version": "1.1.28",
+  "version": "1.1.30",
   "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

@@ -104,8 +104,10 @@ _(Links to phase outputs — update as each workflow completes)_
 - [ ] experiment-plan.md
 - [ ] gate-evaluation.md
 - [ ] pitch/checkin-pitch.md
+- [ ] pitch/checkin-nvb-decision.md  ← Week 8 board feedback + GO/PIVOT/KILL
 
 **06-design-business/**
 - [ ] gtm-plan.md
 - [ ] market-experiment.md
 - [ ] pitch/pitch-deck.md
+- [ ] pitch/final-nvb-decision.md  ← Week 12 board feedback + final decision

package/venture-master.md

@@ -113,15 +113,16 @@ _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:
+    <r>OUTPUT FOLDER STRUCTURE — All agents MUST save outputs to these phase subfolders under {output_folder}/{venture_name}/. Use the EXACT folder names listed below — do NOT derive them from phase numbers or rename them. These are literal strings:
     - venture-brief.md (root, always current) — Victor updates this after every completed workflow
     - 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/
+    - 03-find-pain/ → pain-hypothesis.md, social-signal-scan.md, interview-outreach-plan.md, icp-profile.md, interview-synthesis.md, pain-atomization.md, pain-journey-map.md, interview-scripts/ (scripts before interviews), interviews/ (notes + synthetic + imported)
     - 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
+    NEVER create folders like 1-domain-research, 0-domain-research, domain-research, or any other variation. Only the exact names above.
     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

package/workflow-engine.md

@@ -73,6 +73,17 @@ After any workflow completes (or after each step in guided mode):
 2. Add the new artifact to `completed_artifacts` list
 3. Update any `guiding_questions` that were answered by this workflow
 4. Save the updated venture-state.yaml
+5. **Update venture-brief.md** — open `{output_folder}/{venture_name}/venture-brief.md` and update:
+   - Phase / Week / Status / Last Updated header fields
+   - The Problem section (if pain has been identified or refined)
+   - The Solution section (if a wedge has been defined)
+   - The Market section (if TAM/SAM/SOM have been sized)
+   - The Evidence section (add any new [V]/[P]/[A] findings from this workflow)
+   - The Business Model section (if revenue model or unit economics have been defined)
+   - The Gate Status section (if a gate was evaluated)
+   - The Artifacts checklist — check off the newly completed artifact(s)
+   - Next step — update to reflect the single most important next action
+   This is mandatory after every workflow. venture-brief.md must always reflect the current state of the venture.
 
 ---
 

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

@@ -136,3 +136,7 @@ Proceed to Step 5.
 | Pain atomization matrix | `pain-atomization.md` |
 | Updated pain hypothesis | `pain-hypothesis.md` |
 | Desk research notes | `interviews/desk-research-prevalence.md` |
+
+---
+
+⚠️ **MANDATORY NEXT STEP — Do not stop here.** Pain atomization is not the final step of Find Customer Pain. Proceed immediately to **Step 5: Pain Journey Map and ICP** — load `{project-root}/ventureOS/workflows/3-find-pain/customer-pain-discovery/step-5-pain-journey-map.md`. The phase is not complete without the pain journey map and ICP profile.

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

@@ -80,4 +80,13 @@
     </state-update>
   </step>
 
+  <completion>
+    ⚠️ MANDATORY NEXT STEP — Do not stop here. Business Case is not complete without the check-in pitch and board review.
+    Immediately run the Check-in Pitch workflow: load all three steps in sequence:
+    1. {project-root}/ventureOS/workflows/5-business-case/checkin-pitch/step-1-evidence-compilation.md
+    2. {project-root}/ventureOS/workflows/5-business-case/checkin-pitch/step-2-pitch-creation.md
+    3. {project-root}/ventureOS/workflows/5-business-case/checkin-pitch/step-3-nvb-review.md
+    The Week 8 gate decision (GO / PIVOT / KILL) lives in the NVB review step. The venture cannot advance to Phase 6 without this gate.
+  </completion>
+
 </workflow-instructions>