ventureos 1.1.25 → 1.1.26

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "ventureos",
3
- "version": "1.1.25",
3
+ "version": "1.1.26",
4
4
  "description": "VentureOS — AI-powered venture building framework. From raw idea to validated venture — 12 weeks of structured ideation and incubation.",
5
5
  "type": "module",
6
6
  "bin": {
package/venture-master.md CHANGED
@@ -25,12 +25,18 @@ IF venture_name is empty (first run) → skip the status table and the menu enti
25
25
 
26
26
  Hi {user_name}, I'm Victor — your AI venture orchestrator.
27
27
 
28
- Would you like to **start a new venture**, or **explore a domain** first?
28
+ Where are you starting from?
29
+
30
+ **[I] I have a specific idea** — jump straight into market research and customer discovery
31
+ **[D] I have a domain to explore** — I'll map the landscape, rank opportunities, and help you pick the right one to build
32
+
29
33
  ---
30
34
 
31
35
  Then STOP and wait:
32
- - Any form of "start" / "new venture" / "idea" / "venture" → trigger NV
33
- - Any form of "explore" / "domain" / "research" → trigger EX
36
+ - Any form of "idea" / "I" / "start" / "specific" / "venture" → trigger NV, pre-select entry point = Idea
37
+ - Any form of "domain" / "D" / "explore" / "research" / "landscape" → trigger NV, pre-select entry point = Domain
38
+
39
+ Both paths go through NV first (venture setup, folder creation, venture-brief.md). Domain entry runs EX as Phase 0 then continues automatically into the full incubation journey. EX from the menu is for returning users who want to run additional domain research on an active venture.
34
40
 
35
41
  IF venture_name is set → display the venture context banner and proceed to step 5:
36
42
 
@@ -124,13 +124,15 @@
124
124
  2. Fill in: venture name/codename, challenge statement, market forces, starting hypotheses
125
125
  3. Set entry_point: "domain" in venture-state.yaml
126
126
  4. Initialize venture-state.yaml with the new venture details
127
- 5. Ask user: "Is this the opportunity you want to take into incubation? If yes, we move to Phase 1: Setup the Team."
127
+ 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.**"
128
+ 6. Wait for user confirmation or selection.
129
+ 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.
128
130
  </instructions>
129
131
  <template-output file="{output_folder}/{venture_name}/venture-canvas.md">
130
132
  Save venture canvas as starting artifact.
131
133
  </template-output>
132
134
  <state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">
133
- Update: venture_name, entry_point: "domain", current_phase: "1-setup-team", completed_artifacts with all domain research files
135
+ Update: venture_name, entry_point: "domain", current_phase: "2-understand-market", completed_artifacts with all domain research files
134
136
  </state-update>
135
137
  </step>
136
138