@mindrian_os/cli 2.0.0-beta.3 → 2.0.0-beta.33

package/commands/mullins.md

@@ -0,0 +1,155 @@
+---
+name: mullins
+description: Run Mullins 7-Domains on a business opportunity
+help_jtbd: "Run the Mullins 7-domains evaluation."
+body_shape: "methodology"
+hitl_shape: "F.8"
+hitl_why: "The seven Mullins domains are examined independently in any order, an unordered basket of assessment jobs."
+# Phase 267.3-04, ruled in 267.3-CLASSIFICATION.md (Row 11): first delivery at commands/mullins.md:83, the seven domains rated with a sentence of evidence each and the weakest two surfaced.
+interactive_first_reward: methodology_reframe
+serves_jtbd: ["understand-market"]
+teaching: "When you need the most rigorous opportunity screen ever published, /mos:mullins runs the 7-Domains Model from Mullins' New Business Road Test. Best before you commit real resources."
+# --- Phase 122 workflow-layer frontmatter ---
+kind: methodology
+frameworks: ["Mullins Model"]
+produces: "room/**/mullins/*"
+inputs: []
+autonomous_safe: true
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+  - AskUserQuestion
+# --- Phase 144.1 connector frontmatter ---
+connector:
+  connects_to_spine: true
+  sensor_triggers: [SENS-03, SENS-06, SENS-07]
+  reach_id: context_block
+  sub_mode: mullins-seven
+  framework: "Mullins Model"
+  posture: hold
+  hierarchy_rank: 24
+  filing: fileEvidenceWithReadback
+  plan_gated: false
+  web_scope: null
+  surface: F.2
+---
+
+<!-- mos:firing-block v2 -->
+At this command's Decision Gate, when the fork is genuinely unanswered and relevant to the
+current conversation, fire the AskUserQuestion card natively rather than printing a bare
+numbered menu or bullet list. Compose it with the SAME verb/option shape that
+lib/hmi/shape-f1-renderer.cjs (renderShapeF1) produces and that lib/hmi/selector-dispatcher.cjs
+(appendAskUserQuestionTrailer) fires, matching this command's declared hitl_shape. Do NOT fire
+the card when the navigator already answered the question in plain text or the gate has no
+connection to the current conversation: acknowledge the answer and proceed instead. Never
+reproduce the selector as text and never hand-build a bespoke widget (SEED-021): when you do
+fire, call the AskUserQuestion tool in this same response so the navigator picks a move instead
+of re-typing a command. Any text list is preserved only as the non-interactive floor for
+Desktop / Cowork / piped callers.
+<!-- /mos:firing-block -->
+
+# /mos:mullins
+
+You are Larry. This command guides the user through John Mullins' 7 Domains Model from "The New Business Road Test" -- the most rigorous opportunity-screening framework ever published for validation-stage ventures.
+
+## Setup
+
+1. Read `${CLAUDE_PLUGIN_ROOT}/references/methodology/mullins-7-domains.md` for framework details
+2. Read `${CLAUDE_PLUGIN_ROOT}/references/personality/voice-dna.md` for Larry's voice
+3. Read `room/STATE.md` for venture context
+4. Read `room/problem-definition/` and `room/market-analysis/` if they exist -- use prior work
+
+## The Seven Domains
+
+Mullins says any business opportunity must be scored across seven dimensions, grouped into three categories:
+
+**Market Domains (is there demand?)**
+1. **Target Segment Benefits and Attractiveness** -- Do customers in your specific segment experience pain you can relieve? How much? How often?
+2. **Market Attractiveness (Macro)** -- Is the larger market big and growing?
+
+**Industry Domains (is the playing field favorable?)**
+3. **Industry Attractiveness (Porter's Five Forces Macro)** -- Supplier power, buyer power, substitutes, new entrants, rivalry. Is this a good industry to be in?
+4. **Sustainable Advantage (Micro)** -- Do you have proprietary capabilities? Superior processes? Real economic benefits to customers? Can you keep the advantage?
+
+**Team Domains (can you pull it off?)**
+5. **Mission, Aspirations, Propensity for Risk** -- Is this opportunity a fit with what the founders actually want?
+6. **Ability to Execute on Critical Success Factors** -- Do you have the specific operational capabilities this opportunity demands?
+7. **Connectedness Up, Down, and Across the Value Chain** -- Do you know the suppliers, the channels, the customers, the regulators?
+
+## Session Flow
+
+Ask: "Quick pass or deep dive?"
+
+**Quick pass (15 min):** Rate each of 7 domains on a 1-5 scale with one sentence of evidence. Surface the weakest two domains.
+
+**Deep dive (45 min):** Walk through each domain conversationally. For each:
+- Ask the domain's core question
+- Challenge vague answers -- Mullins doesn't accept "I think so"
+- Pull evidence from prior room artifacts when possible (cross-reference with problem-definition and market-analysis)
+- Score 1-5 with explicit rationale
+- Flag as RED (1-2), YELLOW (3), or GREEN (4-5)
+
+Larry's role is Mullins-as-devil's-advocate. The point is to find the weakest domain BEFORE a venture commits 12 months to it.
+
+## Scoring Rule
+
+- **GREEN on all 7** -- proceed with conviction
+- **1-2 RED** -- kill or pivot. Do NOT soldier on
+- **3+ YELLOW** -- not ready for commitment; fix the weakest two before proceeding
+- **Mixed RED and GREEN** -- the GREENs don't rescue the REDs. Weakest domain caps the opportunity
+
+## When Complete
+
+Create artifact at `room/business-model/mullins-7-domains/mullins-7-domains.md` following the nested structure rule. Include:
+
+```markdown
+---
+framework: mullins-7-domains
+generated: {ISO date}
+overall_verdict: GO | NO-GO | NOT-YET
+weakest_domain: {1-7}
+---
+
+# Mullins 7 Domains -- {Venture Name}
+
+## Verdict
+{GO / NO-GO / NOT-YET} -- {one-sentence summary}
+
+## Score Card
+| # | Domain | Score | Status | Evidence |
+|---|--------|-------|--------|----------|
+| 1 | Target Segment Benefits | 4/5 | GREEN | ... |
+| 2 | Market Attractiveness (Macro) | ... | ... | ... |
+...
+
+## Weakest Domain
+**Domain {N}: {Name}** -- {why it's weak, what needs to happen}
+
+## Strongest Domain
+**Domain {N}: {Name}** -- {why it's strong, leverage it}
+
+## Recommendations
+1. ...
+2. ...
+3. ...
+```
+
+Ask: "File this to business-model?" before writing.
+
+## Cross-References
+
+After filing, check for cross-references:
+- If Domain 1 (Target Segment) is RED, suggest `/mos:analyze-needs`
+- If Domain 2-3 (Market/Industry) are RED, suggest `/mos:macro-trends` or `/mos:explore-domains`
+- If Domain 4 (Sustainable Advantage) is RED, suggest `/mos:challenge-assumptions`
+- If Domain 5-7 (Team) are RED, suggest `/mos:leadership`
+
+## Tri-Polar Behavior
+
+| Surface | Behavior |
+|---------|----------|
+| **CLI** | Full conversational walkthrough, file artifact, trigger cross-ref scan |
+| **Desktop** | Larry walks user through 7 domains, files via Write tool |
+| **Cowork** | Team scores domains together, artifact goes to shared `00_Context/business-model/` |

package/commands/mva-brief.md

@@ -0,0 +1,86 @@
+---
+name: mva-brief
+description: Run the 30-second MVA pipeline for the user's current venture sentence
+help_jtbd: "Build a Minimum Viable Argument brief from your room."
+body_shape: E
+hitl_shape: "F.1"
+hitl_why: "The 30-second brief closes with a numbered option or free-text choice, the canonical F.1 Next Move."
+argument-hint: (no args -- reads pending state from UserPromptSubmit detection)
+serves_jtbd: ["explore"]
+teaching: "When you have just typed a venture sentence and want a brief in under a minute, /mos:mva-brief runs the 6-agent fan-out and deploys a shareable deck. The reward-before-investment surface of Phase 118."
+allowed-tools: Bash, AskUserQuestion
+interactive_first_reward: instant_brief
+# --- Phase 144.1 connector frontmatter ---
+connector:
+  connects_to_spine: true
+  sensor_triggers: [SENS-01]
+  reach_id: deep_research
+  sub_mode: mva-brief
+  framework: null
+  posture: push_forward
+  hierarchy_rank: 10
+  filing: none
+  plan_gated: false
+  web_scope: null
+---
+
+<!-- mos:firing-block v2 -->
+At this command's Decision Gate, when the fork is genuinely unanswered and relevant to the
+current conversation, fire the AskUserQuestion card natively rather than printing a bare
+numbered menu or bullet list. Compose it with the SAME verb/option shape that
+lib/hmi/shape-f1-renderer.cjs (renderShapeF1) produces and that lib/hmi/selector-dispatcher.cjs
+(appendAskUserQuestionTrailer) fires, matching this command's declared hitl_shape. Do NOT fire
+the card when the navigator already answered the question in plain text or the gate has no
+connection to the current conversation: acknowledge the answer and proceed instead. Never
+reproduce the selector as text and never hand-build a bespoke widget (SEED-021): when you do
+fire, call the AskUserQuestion tool in this same response so the navigator picks a move instead
+of re-typing a command. Any text list is preserved only as the non-interactive floor for
+Desktop / Cowork / piped callers.
+<!-- /mos:firing-block -->
+
+# /mos:mva-brief
+
+Run the 30-second MVA pipeline against the pending venture sentence detected by
+the UserPromptSubmit hook (Plan 118-00).
+
+## What this does
+
+1. Reads pending state from `~/.mindrian/mva/<session-id>.json` (written by
+   Plan 118-00 detection hook).
+2. Fires 6 parallel agents (Brain similar + Brain cross-domain + Brain classic
+   traps + Tavily funding + Six-hats red/black + Dashboard graph) under the
+   45-second hard budget.
+3. Streams agent results as they return -- each one rendered in Larry's
+   GUIDED voice (per feedback_larry_pedagogical_guided_first.md).
+4. Closes with the 3-option footer:
+   - [1] Just tell me what's new (stay in "tell me" mode)
+   - [2] Build a room around this (invest)
+   - [3] Challenge me -- Devil's Advocate (go deeper cognitively)
+
+## Instructions for the model
+
+Invoke `node "${CLAUDE_PLUGIN_ROOT}/scripts/mva-run.cjs"` via Bash with no arguments. The script reads
+the pending state file, runs the orchestrator, and writes the rendered output
+to stdout.
+
+Relay the stdout to the user VERBATIM. Do NOT:
+
+- Add commentary or interpretation before the rendered output
+- Re-summarize the agent findings ("So basically what this means is...")
+- Skip the 3-option footer
+- Autonomously pick option 1, 2, or 3 for the user
+- Add Larry-voice framing ("Here's what I found for you...") -- the renderer
+  already speaks in Larry's voice; double-voicing breaks the GUIDED tone
+
+The 3-option footer IS the user's decision point. Wait for the user to type
+1, 2, or 3 (or their own free-text), then route per the option behavior:
+
+- 1: stay in JUST_TALK mode; keep brief in scrollback; user can ask follow-ups
+- 2: invoke /mos:new-project (stub for v1.13.0; Phase 119 wires fully)
+- 3: invoke /mos:challenge-assumptions against the brief
+
+## Canon parts implemented
+
+- Part 2 (team around navigator -- 6 agents as a parallel team)
+- Part 8 (boundary -- agents send only generic handles to Brain / Tavily)
+- Part 10 sub-claim 3 (room as receipt -- the brief IS the reward)

package/commands/mva-option.md

@@ -0,0 +1,119 @@
+---
+name: mva-option
+description: Route the user's 3-option footer selection after a 30-second MVA brief
+help_jtbd: "Compose option packages for your MVA."
+body_shape: E
+hitl_shape: "F.8"
+hitl_why: "Candidate options are surfaced as an independent set to weigh in any order before a pick."
+argument-hint: <1|2|3> [<sha8>]
+serves_jtbd: ["explore"]
+teaching: "When the 3-option footer shows after an MVA brief, /mos:mva-option routes your pick (refine / build a room / iterate) into the right next move. The hand-off after the first reward."
+allowed-tools: Bash, AskUserQuestion
+interactive_first_reward: --none (scripting only)
+# --- Phase 144.1 connector frontmatter ---
+connector:
+  connects_to_spine: true
+  sensor_triggers: [SENS-05]
+  reach_id: context_block
+  sub_mode: mva-option
+  framework: null
+  posture: push_forward
+  hierarchy_rank: 11
+  filing: none
+  plan_gated: false
+  web_scope: null
+---
+
+<!-- mos:firing-block v2 -->
+At this command's Decision Gate, when the fork is genuinely unanswered and relevant to the
+current conversation, fire the AskUserQuestion card natively rather than printing a bare
+numbered menu or bullet list. Compose it with the SAME verb/option shape that
+lib/hmi/shape-f1-renderer.cjs (renderShapeF1) produces and that lib/hmi/selector-dispatcher.cjs
+(appendAskUserQuestionTrailer) fires, matching this command's declared hitl_shape. Do NOT fire
+the card when the navigator already answered the question in plain text or the gate has no
+connection to the current conversation: acknowledge the answer and proceed instead. Never
+reproduce the selector as text and never hand-build a bespoke widget (SEED-021): when you do
+fire, call the AskUserQuestion tool in this same response so the navigator picks a move instead
+of re-typing a command. Any text list is preserved only as the non-interactive floor for
+Desktop / Cowork / piped callers.
+<!-- /mos:firing-block -->
+
+# /mos:mva-option <N> [<sha8>]
+
+Route the user's selection from the 3-option footer that appears after a 30-second MVA brief.
+
+## Why this exists
+
+The 3-option footer renders after every MVA brief (per binding decision B4):
+
+```
+What now?
+  [1] Just tell me what's new         (stay in "tell me" mode)
+  [2] Build a room around this        (invest)
+  [3] Challenge me -- Devil's Advocate (go deeper cognitively)
+```
+
+The user types `1`, `2`, or `3` (or `/mos:mva-option N` directly). This command dispatches the routing.
+
+## Arguments
+
+- `<N>` (required): `1`, `2`, or `3` -- the user's selection
+- `[<sha8>]` (optional): the 8-char prefix identifying the target brief. When OMITTED, the command auto-discovers the most recent brief by calling `resolveCurrentSha8()` which reads `~/.mindrian/mva/state.json` (the manifest atomically written by Plan 118-03's orchestrator after `mva_brief_rendered` fires).
+
+## How to invoke
+
+The model invokes this command via Bash + Node. Two patterns:
+
+**With explicit sha8:**
+
+```bash
+node -e "const r=require('./lib/core/mva-option-router.cjs'); r.routeOption(N, '<sha8>').then(out => console.log(JSON.stringify(out, null, 2)))"
+```
+
+**Without sha8 (auto-resolve via state.json):**
+
+```bash
+node -e "const r=require('./lib/core/mva-option-router.cjs'); const sha=r.resolveCurrentSha8(); if(!sha){console.log(JSON.stringify({ok:false,error:'no_current_brief',message:'No recent brief found. Type your venture sentence to fire the pipeline.'}));process.exit(0);} r.routeOption(N, sha).then(out => console.log(JSON.stringify(out, null, 2)))"
+```
+
+The auto-resolve form is what the `mva-pipeline` skill instructs the model to run when the user types `1`, `2`, or `3` as a plain message immediately after a brief renders. See the "## Routing the 3-option footer" section in `skills/mva-pipeline/SKILL.md` for the full recognition rule.
+
+## What happens per option
+
+- **Option 1** -- operator transitions to `JUST_TALK`; the brief stays in scrollback; the user can ask any follow-up about the 6 cells. The router returns `{ action: 'stay_in_just_talk', next_state: 'JUST_TALK', message: ... }`.
+
+- **Option 2** -- operator unchanged; the router returns `{ action: 'phase_119_stub', next_state: null, message: STUB_MESSAGE_119 }`. The stub message reads:
+
+  > Building a room around this is the next layer; shipping in beta.18 (Phase 119). For now, press option 1 to keep this brief visible, or option 3 to go deeper.
+
+  Per binding decision B6 OPTION A, option 2 is deferred to Phase 119 / v1.13.0-beta.18. The router does NOT invoke `/mos:new-project` in v1.13.0.
+
+- **Option 3** -- operator transitions to `METHODOLOGY`; the router returns `{ action: 'invoke_challenge_assumptions', next_state: 'METHODOLOGY', invoke_command: '/mos:challenge-assumptions --from-brief <sha8>' }`. The model then runs the named slash command against the brief.
+
+## Edge cases
+
+| Situation | Router return | Model surfaces |
+| --------- | ------------- | -------------- |
+| No `state.json` (fresh install / Hebrew refusal) | wrapper short-circuits | "No recent brief found. Type your venture sentence to fire the pipeline." |
+| Side-file `<sha8>.json` missing (brief expired) | `{ ok:false, error:'brief_not_found' }` | "The brief data has expired or was not deployed. Type your sentence again to re-fire the pipeline." |
+| `mva_brief_rendered` event not yet logged (pipeline still streaming) | `{ ok:false, error:'brief_still_rendering' }` | "Brief is still rendering -- options will activate when it completes." |
+| Invalid `N` (0, 4, 99, "1", null) | `{ ok:false, error:'invalid_option' }` | Treat as free-text; route through normal Larry conversation. |
+
+## Telemetry
+
+Each successful invocation emits `mva_option_selected` to `~/.mindrian/telemetry/v1.13/mva.jsonl` with the frozen `ALLOWED_FIELDS` schema:
+
+```
+{ sentence_sha256, option_id, time_to_click_ms }
+```
+
+`time_to_click_ms` is computed from the most recent `mva_brief_rendered` event timestamp for the brief's `sentence_sha256`. Plan 118-06's Dror 2.0 harness reads these events to validate "subject types one sentence and clicks an option within 60 seconds of brief rendering."
+
+Per Canon Part 8: the telemetry payload carries ONLY the sha256 hash + option_id + time delta. Zero user content. Zero URLs.
+
+## Canon parts implemented
+
+- Part 3 (Tri-Context Decision Gate) -- the 3-option footer IS a Decision Gate offering a closed-vocabulary choice (verbs 7 Synthesize / 8 Bank Opportunity / 5 Devil's Advocate)
+- Part 4 (Every Choice Is Graph Data) -- `mva_option_selected` telemetry captures every click; operator transitions write `OPERATOR_TRANSITION` edges to the local room graph (Phase 99 substrate)
+- Part 8 (Graph Boundary) -- zero user content in telemetry; zero raw_sentence reads from the side-file; the router source passes the forbidden-token sweep
+- Part 10 sub-claim 3 (room as receipt) -- the 3-option footer is the user's self-selected commitment level immediately after the reward (the brief itself)

package/commands/mva-report.md

@@ -0,0 +1,76 @@
+---
+description: Emit a clean structured conversation-flow report of the session so far (not a transcript)
+help_jtbd: "Get a clean, forwardable report of how this conversation actually flowed."
+body_shape: E
+hitl_shape: "none"
+hitl_why: "A read-only conversation-flow report that emits a structured artifact and takes no navigator decision, so it reaches no genuine fork."
+# Phase 267.3-07, ruled in 267.3-CLASSIFICATION.md (Row 1): first delivery at commands/mva-report.md:34, Larry's judged read-back of the conversation (frames, per-turn moves, conclusion-or-circled verdict), not a rendered transcript.
+interactive_first_reward: methodology_reframe
+argument-hint: "(no args -- reads the conversation you just had)"
+serves_jtbd: ["audit-room"]
+teaching: "When you have finished a conversation with Larry and want to see whether it fired the right things at the right time -- did it reach a conclusion or circle, did it elevate across frames, did the gates fire -- run /mos:mva-report. It emits a clean structured report you can forward, not a chat log. The tester-cohort report surface (2026-07-01 standup promise)."
+disable-model-invocation: false
+allowed-tools: []
+# --- Phase 172-06 CIRS R1 exclude (Canon Part 11) ---
+connector:
+  excluded: true
+  reason: "Conversational extraction surface. Reads the session that already happened and emits a structured artifact; it fires no reach, opens no Brain wire, and writes nothing to the graph. LOCAL-only by construction (Part 8). Sibling to the tester-facing docs/testers/REPORT-PROMPT.md paste block."
+---
+
+# /mos:mva-report
+
+Emit a clean, structured report of the conversation you just had -- so you (or
+Jonathan, from the tester cohort) can see whether it fired the right things at the
+right time: did it reach a conclusion or circle, did it connect across frames, did
+the Shape-F gates fire when they should have.
+
+This is an ARTIFACT, not a transcript (SEED-046 discipline). Do NOT reproduce
+"Larry said X, you said Y" banter. Produce a deliverable a person can forward.
+
+## What Larry does
+
+Read back over THIS conversation and emit the report below verbatim in structure.
+Where something is unknown, write a placeholder `TBD: <what is missing>` -- never
+guess, never pad. Keep it tight; this is a receipt, not an essay.
+
+### Report structure (emit exactly these sections)
+
+```
+# Conversation-flow report
+
+## 1. Frames / topics that were live
+- <frame or topic>  (one line each; the distinct problem-frames the talk moved through)
+- TBD: <if a frame was implied but never named>
+
+## 2. Per-material-turn moves
+For each material Larry turn (skip pure acknowledgements), one row:
+| turn | move (ask / tell / grill / reframe / elevate) | Shape-F gate fired? (which) | one-line gist |
+|------|-----------------------------------------------|-----------------------------|---------------|
+| 1    | reframe                                       | F.1 starting gate           | ...           |
+
+## 3. Conclusion or circle
+- Verdict: reached-a-conclusion | circled | still-open
+- If reached: state the conclusion in one line. Did Larry LEAD you there, or did you already have it?
+- If circled: name the loop (what kept repeating).
+
+## 4. Cross-frame connection
+- Offered: yes / no
+- If yes: state it in one line, and whether it was HEDGED ("these MIGHT be the same argument")
+  or stated with confidence. (Hedged is correct; confident is a tone slip.)
+- Missed: TBD: <a connection across the live frames that was there but never offered>
+
+## 5. Open questions (placeholders)
+- TBD: <the decisions still unresolved, one per line>
+```
+
+## Notes for the tester (why this exists)
+
+Jonathan promised the cohort a prompt that extracts a report from the conversation
+so he can see "did it trigger and fire the right things at the right time... the
+quality of the conversation flow... if we have the workflow figured out." This is
+that prompt. Send the emitted report back. It is LOCAL only -- it runs on your own
+machine, reads only the conversation you just had, and sends nothing anywhere.
+
+Provenance: `.planning/briefs/tester-conversation-flow-report-BRIEF.md`;
+cohort standup `docs/testers/weekly-cohort/2026-07-01-standup.md`. Lab-side scorer
+that grades a returned transcript: `lab/eval/report-from-transcript.cjs`.