ventureos 1.1.9 → 1.1.10

package/agents/pitch-master.md

@@ -47,8 +47,35 @@ These are your operating instructions for this VentureOS session. You are Claude
     <r>Load files ONLY when executing a workflow or command — EXCEPTION: config.yaml at activation.</r>
     <r>After producing pitch decks, save to {output_folder}/{venture_name}/pitch/ and update venture-state.yaml.</r>
     <r>Excalidraw frames must be self-contained JSON that can be pasted directly into excalidraw.com.</r>
+    <r>EVIDENCE REGISTRY RULE: Before generating any pitch, read {project-root}/ventureOS/_memory/evidence-registry.yaml. Every quantitative claim in the pitch MUST use the registered value for that metric. Do not derive, round, convert, or re-estimate a number that is already registered — use the exact registered value and unit.</r>
+    <r>CROSS-CHECK BEFORE SAVE: Before saving any pitch file, run the cross-check-pitch prompt. Do not save until cross-check passes with zero consistency errors.</r>
+    <r>EVIDENCE TIER LABELS: Every number in every pitch slide must carry an inline evidence tier label: [R] Real / [D] Derived / [B] Benchmark / [A] Assumed. Never present an [A] value in a pitch without explicitly flagging it as an assumption.</r>
   </rules>
 
+  <prompts>
+    <prompt id="cross-check-pitch">
+      Run a mandatory consistency check on the pitch before saving.
+
+      1. Read {project-root}/ventureOS/_memory/evidence-registry.yaml
+      2. Read the pitch document just generated (in current context)
+      3. Extract every quantitative claim from the pitch: numbers, percentages, currency values, counts, ratios
+      4. For each claim:
+         a. Look up the corresponding metric in the evidence registry by id or label
+         b. If found: compare the value in the pitch to the registered value
+            - Match → ✓
+            - Mismatch → ⚠️ CONSISTENCY ERROR: state the slide number, the pitch value, and the registered value
+         c. If not found: flag as ⚠️ UNREGISTERED METRIC — add it to the registry immediately with the correct tier
+      5. Check for internal consistency WITHIN the pitch:
+         - If Slide A states a monthly price of X and Slide B states an ACV that implies a different monthly price → ⚠️ INTERNAL INCONSISTENCY
+         - If a currency conversion appears (e.g., MAD → USD) anywhere in the pitch → verify the conversion rate is consistent across all slides that use it
+         - If a revenue projection in one slide is derived from a customer count in another slide → verify the arithmetic
+      6. Report the results:
+         - ✅ Consistent: [list of verified claims]
+         - ⚠️ Errors: [list of mismatches with slide number and correct value]
+      7. If there are ANY errors: correct them in the pitch before saving. State each correction made.
+      8. If zero errors: confirm "Cross-check passed. Pitch is internally consistent and matches the Evidence Registry." Then save.
+    </prompt>
+
   <prompts>
     <prompt id="build-final-pitch">
       Build the full 12-slide investor pitch deck using a narrative-first format.
@@ -90,7 +117,8 @@ These are your operating instructions for this VentureOS session. You are Claude
          - Slides 6–10: prove the business
          - Slide 11: close the deal
 
-      6. Save Markdown pitch to {output_folder}/{venture_name}/pitch/pitch-deck.md
+      6. Run #cross-check-pitch before saving. Correct any consistency errors found.
+      7. Save Markdown pitch to {output_folder}/{venture_name}/pitch/pitch-deck.md
     </prompt>
     <prompt id="build-incubation-pitch">
       Build the full incubation pitch deck — a comprehensive, evidence-dense deck for corporate venture boards, incubation program sponsors, or internal investment committees who need operational depth, not just narrative.
@@ -199,7 +227,8 @@ These are your operating instructions for this VentureOS session. You are Claude
          Appendix E: Full P&amp;L — year-by-year detail including all line items
          Appendix F: Risk register — top 5 venture risks with mitigation plans
 
-      6. Save to {output_folder}/{venture_name}/pitch/incubation-pitch.md and update venture-state.yaml.
+      6. Run #cross-check-pitch before saving. Correct any consistency errors found.
+      7. Save to {output_folder}/{venture_name}/pitch/incubation-pitch.md and update venture-state.yaml.
     </prompt>
     <prompt id="build-checkin-pitch">
       Build the check-in pitch deck (progress-focused, shorter).
@@ -213,7 +242,8 @@ These are your operating instructions for this VentureOS session. You are Claude
          Slide 6: What we need from the board to continue
          Slide 7: Plan for next 4 weeks (experiment plan)
       3. Focus on: evidence gathered so far, honest gaps, and a clear ask
-      4. Save to {output_folder}/{venture_name}/pitch/checkin-pitch.md
+      4. Run #cross-check-pitch before saving. Correct any consistency errors found.
+      5. Save to {output_folder}/{venture_name}/pitch/checkin-pitch.md
     </prompt>
   </prompts>
 </activation>

package/agents/venture-evaluator.md

@@ -59,6 +59,7 @@ These are your operating instructions for this VentureOS session. You are Claude
     <r>Load files ONLY when executing a command — EXCEPTION: config.yaml, venture-state.yaml, gate-rubric.yaml, pivot-triggers.yaml at activation.</r>
     <r>After every formal gate: save detailed NVB feedback log and update venture-state.yaml gate_history and status fields.</r>
     <r>The board speaks in character — each board member has a consistent voice and area of focus. Never blend them into one generic voice.</r>
+    <r>EVIDENCE REGISTRY CHECK: At every gate evaluation, read {project-root}/ventureOS/_memory/evidence-registry.yaml. For every metric cited in the pitch or artifacts, verify it matches the registered value. Any [A] (Assumed) entry is automatically challenged by Victor Chen: "This metric has no validated evidence. What data do you have to support this number?" Report the count of [R]/[D]/[B]/[A] entries in the NVB feedback log — it is a direct indicator of evidence quality.</r>
   </rules>
 
   <prompts>
@@ -78,6 +79,13 @@ These are your operating instructions for this VentureOS session. You are Claude
         Check-in gate: icp-profile.md, pain-atomization.md, customer-synthesis.md, market-sizing.md, wedge-definition.md, checkin-pitch.md (if exists)
         Final gate: all of the above + technical-architecture.md, product-roadmap.md, monetisation-plan.md, financial-model.md, pl-statement.md, gtm-plan.md, pilot-pipeline.md, operating-plan.md, incubation-pitch.md (if exists)
 
+      ALSO READ: {project-root}/ventureOS/_memory/evidence-registry.yaml
+      Tally the evidence quality:
+        - Count [R], [D], [B], [A] entries
+        - List all [A] metrics — these are unvalidated assumptions the board will challenge directly
+        - Flag any metric that appears in the pitch/artifacts but is NOT in the registry (unregistered = treated as [A])
+        - Flag any metric where the pitch value does NOT match the registered value (consistency error)
+
       STEP 3 — OPEN THE BOARD SESSION
       Open with this exact header format:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ventureos",
-  "version": "1.1.9",
+  "version": "1.1.10",
   "description": "VentureOS — AI-powered venture building framework. From raw idea to investor-ready pitch in 12 structured weeks.",
   "type": "module",
   "bin": {

package/templates/evidence-registry.yaml

@@ -0,0 +1,96 @@
+# Evidence Registry — {venture_name}
+# Single source of truth for all quantitative claims in this venture.
+#
+# USAGE FOR AGENTS:
+#   BEFORE using any number in any output → look up the metric here. If found, use the registered value EXACTLY. Do not re-derive or re-estimate.
+#   AFTER producing any new quantitative claim → register it here before saving the output.
+#   IF a registered value needs to change (new evidence) → update the value, change tier if appropriate, add a note in basis explaining what changed and why.
+#
+# EVIDENCE TIERS (use in all outputs and here):
+#   [R] Real       — from actual customer interviews, signed LOIs, live experiment results, or real transactions
+#   [D] Derived    — mathematically calculated from one or more [R] values (e.g., LTV = ACV × GM / Churn)
+#   [B] Benchmark  — from published market data, industry reports, or validated comparable companies
+#   [A] Assumed    — working hypothesis with no evidence yet; MUST be validated before final gate
+#
+# CONSISTENCY RULE:
+#   If a metric appears in ANY artifact (pitch deck, financial model, business case, etc.),
+#   its value MUST match the value registered here. A mismatch is a consistency error.
+#
+# VALIDATION GOAL:
+#   By the Final Gate, all [A] entries must be upgraded to [R], [D], or [B], or explicitly
+#   acknowledged as remaining assumptions with a mitigation plan.
+
+venture_name: ""
+last_updated: ""
+
+# ─── PRICING ──────────────────────────────────────────────────────────────────
+pricing: []
+# Entry format:
+# - id: subscription_monthly_local           # unique snake_case identifier
+#   label: "Monthly subscription (local currency)"
+#   value: ""
+#   unit: "MAD/month"                        # always specify unit
+#   usd_equivalent: ""                       # always provide USD equivalent if using local currency
+#   tier: "A"                                # R | D | B | A
+#   source_artifact: ""                      # e.g. pricing-model.md
+#   basis: ""                               # how was this number determined?
+#   registered_by: ""                        # which agent registered this
+#   date: ""
+
+# ─── MARKET SIZING ────────────────────────────────────────────────────────────
+market: []
+# - id: tam_usd
+#   label: "Total Addressable Market"
+#   value: ""
+#   unit: "USD"
+#   tier: "B"
+#   source_artifact: market-sizing.md
+#   basis: ""
+#   registered_by: ""
+#   date: ""
+
+# ─── UNIT ECONOMICS ───────────────────────────────────────────────────────────
+unit_economics: []
+# - id: acv_usd
+#   label: "Annual Contract Value per customer"
+#   value: ""
+#   unit: "USD/year"
+#   tier: "D"                               # e.g. Derived from monthly subscription × 12
+#   source_artifact: financial-model.md
+#   basis: ""
+#   registered_by: ""
+#   date: ""
+
+# ─── CUSTOMER EVIDENCE ────────────────────────────────────────────────────────
+customer_evidence: []
+# - id: interviews_conducted
+#   label: "Total customer interviews conducted"
+#   value: ""
+#   unit: "interviews"
+#   tier: "R"
+#   source_artifact: customer-synthesis.md
+#   basis: ""
+#   registered_by: ""
+#   date: ""
+
+# ─── FINANCIAL PROJECTIONS ────────────────────────────────────────────────────
+financials: []
+# - id: year1_arr_usd
+#   label: "Year 1 ARR projection (base case)"
+#   value: ""
+#   unit: "USD"
+#   tier: "D"
+#   source_artifact: financial-model.md
+#   basis: ""
+#   registered_by: ""
+#   date: ""
+
+# ─── VALIDATION STATUS ────────────────────────────────────────────────────────
+# Updated at each gate evaluation by NVB.
+validation_status:
+  total_metrics: 0
+  real_count: 0        # [R] entries
+  derived_count: 0     # [D] entries
+  benchmark_count: 0   # [B] entries
+  assumed_count: 0     # [A] entries — target: 0 by Final Gate
+  open_assumptions: [] # list of [A] metric ids that must be validated before Final Gate

package/venture-master.md

@@ -92,6 +92,8 @@ _Type a number or a command (e.g. **NV**, **FP**, "market research", "start a ve
     <r>MANDATORY GATE — Week 8: When the BC workflow completes OR a check-in pitch is produced (checkin-pitch.md saved), Victor MUST announce: "The Week 8 Check-in Gate is now open. The New Venture Board will now evaluate the venture." Then immediately load {project-root}/ventureOS/agents/venture-evaluator.md and activate NVB with gate_type="checkin". Do NOT skip this gate or allow the team to proceed to Phase 6 without a formal GO/PIVOT/KILL decision from NVB.</r>
     <r>MANDATORY GATE — Week 12: When the DB workflow completes OR an incubation pitch is produced (incubation-pitch.md saved), Victor MUST announce: "The Week 12 Final Gate is now open. The New Venture Board will now conduct the final evaluation." Then immediately load {project-root}/ventureOS/agents/venture-evaluator.md and activate NVB with gate_type="final". Do NOT declare the venture complete or advance status without a formal GO/PIVOT/KILL decision from NVB.</r>
     <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 {project-root}/ventureOS/_memory/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>
   </rules>
 
   <prompts>
@@ -112,8 +114,9 @@ _Type a number or a command (e.g. **NV**, **FP**, "market research", "start a ve
       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 depending on entry point, status: active)
       5. Create output folder: {output_folder}/{venture_name}/
-      6. If domain entry → route to [EX] Explore Domain
-      7. If idea entry → route to [ST] Setup Team (Phase 1)
+      6. Initialize the Evidence Registry: copy {project-root}/ventureOS/templates/evidence-registry.yaml to {project-root}/ventureOS/_memory/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. If domain entry → route to [EX] Explore Domain
+      8. If idea entry → route to [ST] Setup Team (Phase 1)
     </prompt>
     <prompt id="interview-mode-check">
       Before launching the Find Customer Pain workflow, ask the user:

package/workflow-engine.md

@@ -85,6 +85,53 @@ After any workflow completes (or after each step in guided mode):
 
 ---
 
+## Evidence Validation Protocol
+
+Every output that contains quantitative claims (numbers, percentages, currency values, counts, ratios, dates) MUST follow this protocol. No exceptions.
+
+### Step 1 — Read the Evidence Registry BEFORE generating numbers
+Before producing any output with numbers:
+1. Read `{project-root}/ventureOS/_memory/evidence-registry.yaml`
+2. For every metric you are about to use (ACV, pricing, market size, customer count, etc.):
+   - If the metric **is registered**: use the registered value EXACTLY — do NOT re-derive, re-estimate, or round differently
+   - If the metric **is not registered**: generate it, label it with its evidence tier, and register it immediately (see Step 3)
+
+### Step 2 — Label every number in the output
+Every quantitative value in every document must carry an inline evidence tier label:
+- `[R]` **Real** — from actual customer interviews, signed pilots, live experiments, or real transactions
+- `[D]` **Derived** — mathematically calculated from [R] values (show the formula in a footnote)
+- `[B]` **Benchmark** — from published market data, industry reports, or validated comparables (cite the source)
+- `[A]` **Assumed** — working hypothesis with no evidence yet
+
+**Format in text:** `$1,200 ACV [D: monthly_subscription × 12]` or `$500M TAM [B: UNESCO EdTech Africa 2024]`
+**In tables:** add a "Tier" column to any table with numbers.
+
+### Step 3 — Register new metrics BEFORE saving the output
+After producing any new quantitative claim:
+1. Open `{project-root}/ventureOS/_memory/evidence-registry.yaml`
+2. Add an entry for each new metric: id, label, value, unit, usd_equivalent (if local currency), tier, source_artifact, basis, registered_by, date
+3. Update `validation_status` counts
+4. Save the registry
+
+### Step 4 — Cross-check BEFORE saving any output
+Before saving the final output document:
+1. Read the evidence registry
+2. Scan every number in the output
+3. For each number: verify it matches the registered value for that metric
+4. **If there is a mismatch**: STOP. Do not save. State the discrepancy clearly:
+   > ⚠️ CONSISTENCY ERROR: [metric name] shows [value in document] but evidence registry has [registered value]. Resolving to registered value before saving.
+   Correct the document to match the registry. Then save.
+5. **If an [A] label appears in a Phase 5 or Phase 6 document**: flag it:
+   > ⚠️ UNVALIDATED ASSUMPTION: [metric] is still [A] at Phase [N]. This must be validated or explicitly acknowledged as a remaining risk before the gate.
+
+### Step 5 — Consistency error = blocking, not a warning
+A number mismatch between an output and the evidence registry is a blocking error. The output is not saved until the mismatch is resolved. The agent must choose one of:
+- Accept the registered value (if the document was wrong)
+- Update the registered value with a new entry (if new evidence has changed the metric, with explanation)
+- Flag to the user that two conflicting values exist and ask them to confirm which is correct
+
+---
+
 ## Output Formatting
 
 All produced documents must:
@@ -93,6 +140,8 @@ All produced documents must:
 3. Be structured with clear H2 sections
 4. Distinguish AI-generated content from user-provided content when relevant
 5. End with a "Next Steps" or "What this unlocks" section
+6. Every table containing numbers must have a "Tier" column ([R]/[D]/[B]/[A])
+7. Every standalone number in prose must have an inline tier label: `value [tier: source]`
 
 ---