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

package/skills/update/SKILL.md

@@ -0,0 +1,254 @@
+---
+name: update
+description: Check for MindrianOS updates and install via Claude Code's native plugin loader
+license: BSL-1.1. See LICENSE for complete terms (Business Source License 1.1, Change Date 2030-04-16 to Apache License 2.0).
+help_jtbd: "Update the plugin to the latest version."
+body_shape: E
+hitl_shape: "F.0"
+hitl_why: "It offers one update action to approve or defer."
+# Phase 267.3-07, ruled in 267.3-CLASSIFICATION.md (Row 22): first delivery at commands/update.md:58, the plugin's own version-comparison verdict against the latest release.
+interactive_first_reward: "--none (diagnostic surface)"
+argument-hint: "[check|reapply|force]"
+serves_jtbd: ["audit-room"]
+teaching: "When you suspect MindrianOS has a newer version waiting, /mos:update checks and installs via Claude Code's native plugin loader. Stale plugins quietly diverge from the docs."
+allowed-tools: Bash Read AskUserQuestion
+# --- Phase 172-06 CIRS R1 exclude (Canon Part 11) ---
+connector:
+  excluded: true
+  reason: "Lifecycle command. Plugin update / upgrade surface the navigator runs deliberately; a maintenance action with no problem-state trigger."
+---
+
+# /mos:update
+
+You are Larry. This command checks for updates, shows what's new, then **delegates the actual install to Claude Code's native plugin loader** so the registry (`installed_plugins.json` + `enabledPlugins`) stays in sync with the cache.
+
+## Why native delegation (v1.10.19 (hotfixes shipped 2026-04-26))
+
+The previous version of this command shelled out to `scripts/self-update install`, which copied files to the cache directory but **did not update `~/.claude/plugins/installed_plugins.json` or `~/.claude/settings.json` `enabledPlugins`**. The result: Claude Code's plugin loader never registered the new version. Slash commands disappeared. Users restarted, saw nothing, and assumed the plugin was broken.
+
+This was confirmed in the field by Aryeh Holtzberg (PWS IRIS 2025) on 2026-04-26 -- and matches multiple known Claude Code issues (#11357, #12457, #14815, #17832).
+
+The fix is structural: defer to Claude Code's native commands. They keep all four registry files in sync. We never reimplement what the platform already does correctly.
+
+## Determine Mode
+
+- `reapply` -> jump to the Reapply section.
+- `force`   -> skip version comparison, run native install regardless.
+- (no arg)  -> Update Check flow.
+
+## Update Check Flow
+
+### Step 1: Run SHA-aware version check
+
+```bash
+node "${MINDRIAN_OS_ROOT:-${CLAUDE_PLUGIN_ROOT:?MindrianOS install root not found. Set MINDRIAN_OS_ROOT (see lib/core/active-plugin-root.cjs) or run from Claude Code.}}/scripts/check-version-and-sha.cjs"
+```
+
+This script compares BOTH the semver version string AND the underlying git commit SHA, distinguishing four states:
+- `UP_TO_DATE` -- both version and SHA match
+- `VERSION_DIFFERS` -- standard semver upgrade available
+- `SHA_DIFFERS_INVERSION_HOTFIX` -- same version, but the v<version> tag was force-moved (in-version hotfix). **This is the case standard version-only checkers miss.**
+- `NETWORK_ERROR` / `ERROR` -- couldn't run the check
+
+Parse `STATUS=...` from the first line.
+
+### Step 2: Decide based on STATUS
+
+**If `STATUS=UP_TO_DATE`:**
+> "You're running the latest, v{LOCAL_VERSION} (SHA {LOCAL_SHA}). Nothing to update."
+
+**If `STATUS=NETWORK_ERROR`:**
+> "Couldn't reach GitHub: {REASON}. Your current version works fine. Try again later."
+Done.
+
+**If `STATUS=SHA_DIFFERS_INVERSION_HOTFIX`:**
+> "Heads up -- you're on v{LOCAL_VERSION} (SHA {LOCAL_SHA}) but the v{LATEST_VERSION} tag has been force-moved to SHA {REMOTE_TAG_SHA}. That means an in-version hotfix shipped under the same tag and you're missing it."
+> "This is exactly the case Aryeh hit on 2026-04-26 -- standard `claude plugin update` may or may not detect it, so we'll force a clean re-install."
+
+Continue to Step 3, then run Step 5 with the recovery path:
+```bash
+claude plugin install mos@mindrian-marketplace --force 2>&1
+# OR if --force is unsupported:
+claude plugin uninstall mos@mindrian-marketplace && \
+  claude plugin marketplace update && \
+  claude plugin install mos@mindrian-marketplace
+```
+
+**If `STATUS=VERSION_DIFFERS`:**
+Continue to Step 3 (standard upgrade flow).
+
+### Step 3: Show what's new
+
+Fetch the relevant CHANGELOG section. CRITICAL: anchor on a NUMBERED release heading. The top of main's CHANGELOG is the next-version `[Unreleased] -- (in progress)` placeholder (the two-commit release form burns it), and showing it to a user installing the released version reads as a phantom version (live confusion report, 2026-06-12):
+```bash
+curl -fsSL "https://raw.githubusercontent.com/jsagir/mindrian-os-plugin/main/CHANGELOG.md" | sed -n '/^## \[[0-9]/,/^## \[/p' | head -60
+```
+
+Show in Larry's voice:
+> "v{latest} dropped. You're on v{local}. Here's what's new:"
+
+Render the changelog readably. Keep it tight.
+
+### Step 4: Confirm with the user
+
+Use AskUserQuestion:
+- Question: "Update to v{latest} via Claude Code's native plugin loader?"
+- Options:
+  - "Yes -- update via /plugin"
+  - "Show me the manual commands first"
+  - "No -- cancel"
+
+**If "Show me the manual commands first":**
+Tell them:
+> "These are the two commands. You can paste them yourself and skip the rest of this flow. They are what `/mos:update` runs under the hood."
+> ```
+> /plugin marketplace update
+> /plugin update mos@mindrian-marketplace
+> ```
+> "After both succeed, restart Claude Code and verify with `/mos:help`."
+
+Then re-ask whether to proceed.
+
+**If cancelled:** "Update cancelled. You're still on v{local}."
+Done.
+
+### Step 5: Run native install
+
+```bash
+# Step 5a: refresh the marketplace catalog (gets the new commit behind the tag)
+claude plugin marketplace update 2>&1
+```
+
+Stream output to user. If exit code is non-zero, report:
+> "Marketplace refresh failed: {stderr}. Try again, or run `/plugin marketplace update` manually."
+Done.
+
+```bash
+# Step 5b: install the new version (updates registry + cache + enabledPlugins atomically)
+claude plugin update mos@mindrian-marketplace 2>&1
+```
+
+Stream output. If non-zero exit, fall back instructions:
+> "Native update failed: {stderr}. Two recovery paths -- (1) try `/plugin update mos@mindrian-marketplace` from inside this session, or (2) `/plugin install mos@mindrian-marketplace` for a clean re-install. Either path keeps the registry in sync."
+
+### Step 6: Migrate stale user-settings paths
+
+Run the user-settings migration to clean up any stale version-pinned paths the deprecated self-update wrote into `~/.claude/settings.json`:
+
+```bash
+node "${MINDRIAN_OS_ROOT:-${CLAUDE_PLUGIN_ROOT:?MindrianOS install root not found. Set MINDRIAN_OS_ROOT (see lib/core/active-plugin-root.cjs) or run from Claude Code.}}/scripts/migrate-stale-user-settings.cjs" --apply
+```
+
+If the migrator finds and removes stale entries, surface that to the user:
+> "Cleaned {N} stale path(s) from your user settings.json. The plugin's own `${MINDRIAN_OS_ROOT:-${CLAUDE_PLUGIN_ROOT:?MindrianOS install root not found. Set MINDRIAN_OS_ROOT (see lib/core/active-plugin-root.cjs) or run from Claude Code.}}`-based paths now take effect. A backup was saved to settings.json.bak.<timestamp> in case you need to roll back."
+
+If no findings, mention it briefly:
+> "User settings clean -- no stale paths."
+
+### Step 7: Atomically activate the new bytes (Phase 127.2 Plan 04 Instance #7)
+
+Claude Code's native `plugin update` lands the new version in the cache
+(`~/.claude/plugins/cache/mindrian-marketplace/mos/<NEW_VERSION>/`) but does
+NOT atomically swap the live install at `~/.claude/plugins/mindrian-os/`.
+Without this step every Brain MCP probe + statusline render + hook output
+continues to serve the OLD version. The user thinks they are on beta.N+1
+while every Brain interaction silently reads beta.N -- the "silent
+activation gap" surfaced on the 2026-05-23 dogfood box.
+
+Run the post-update activator to swap atomically:
+
+```bash
+node "${MINDRIAN_OS_ROOT:-${CLAUDE_PLUGIN_ROOT:?MindrianOS install root not found. Set MINDRIAN_OS_ROOT (see lib/core/active-plugin-root.cjs) or run from Claude Code.}}/scripts/doctor.cjs" --fix --post-update
+```
+
+Stream the output to the user. It prints a Shape E action report showing
+the old -> new transition + the backup path of the stale bytes. After
+success it writes a touch-file at `~/.mindrian/post-update-restart-pending`
+that the next SessionStart's preflight hook reads to verify activation
+reached the wire (the L4 MCP server's version matches package.json
+version-of-record). On version-mismatch the preflight hook refuses Larry
+load with a red banner pointing at `/mos:doctor --fix`.
+
+If the activator reports `swapped: false` and `already on latest`: no
+action needed. The cache and live install were already in sync (rare but
+possible if a previous /mos:update sequence completed cleanly).
+
+If it reports `ok: false`: surface the error to the user. They can manually
+run `/mos:doctor --fix` to re-attempt; if that also fails, file an RCA at
+`.planning/debug/post-update-activation-failure-<date>.md`.
+
+### Step 8: Verify, then emit the LOUD restart banner (ALWAYS last)
+
+If all steps succeeded, say briefly:
+> "Done. v{latest} installed via Claude Code's plugin loader and atomically swapped into the live install path. Registry, cache, and `enabledPlugins` are all in sync. User settings checked for stale paths."
+
+Then close the flow with the Mindrian mark FIRST, the loud restart banner SECOND. This block is the **LAST thing the user sees** (never a footnote, never buried under other prose), and it is mandatory on EVERY successful update path (standard, force, and in-version-hotfix).
+
+First render the Mindrian logo:
+
+```bash
+node "${MINDRIAN_OS_ROOT:-${CLAUDE_PLUGIN_ROOT:?MindrianOS install root not found. Set MINDRIAN_OS_ROOT (see lib/core/active-plugin-root.cjs) or run from Claude Code.}}/lib/hmi/mindrian-ascii-logo.cjs"
+```
+
+Stream its output as-is (it is the De Stijl block-letter mark and degrades to plain when the terminal has no color). Then, immediately below the logo, emit the RESTART BANNER defined in the final section of this command **verbatim**.
+
+The reason the banner must be loud and last: the update swapped the install under this running session, and the slash-command registry was built once at session start, so `/mos:help` and every `/mos:*` command will read as "Unknown command" until the user restarts. That vanish looks like breakage; the banner is what tells the user it is expected.
+
+## Force Mode
+
+When the user runs `/mos:update force`, skip Steps 1-3 and go directly to Step 5 with the same native commands. Useful when:
+- An in-version hotfix shipped under the same tag (latest == local but tag was force-moved)
+- The cache is corrupted
+- Registry state files drifted from the cache
+
+## Reapply Flow
+
+When the user runs `/mos:update reapply`:
+
+### Step 1: Check for patches
+
+```bash
+ls ~/.mindrian/backups/*/patches/ 2>/dev/null | head -20
+```
+
+**If no backups found:**
+> "No backed-up modifications found. You're running a clean install."
+
+**If patches found:**
+List the backed-up files. Guide the user on which to restore. (This flow is unchanged from prior versions -- it operates on patch files, not on the plugin loader.)
+
+## Voice Rules
+
+- Frame updates as "here's what's new" not "performing system update"
+- Be conversational, not mechanical
+- Use signature openers: "Very simply...", "Here's the thing..."
+- NO emoji. Use symbol vocabulary only (■ ▼ ▶ ▷ ├─ └─ ✓ • ⚠ ⚡ ⬜ →)
+- If the user asks why we use native commands instead of self-update, explain the registry-sync rationale briefly: "Self-update only updated the cache -- not the plugin loader. Native commands update both. Less surface, fewer ways to drift."
+
+## What this command does NOT do anymore
+
+- Does NOT call `scripts/self-update install` (deprecated -- the self-update script now errors out with a deprecation message)
+- Does NOT manually copy files to `~/.claude/plugins/cache/` (Claude Code's plugin loader does this correctly)
+- Does NOT manually edit `installed_plugins.json` or `enabledPlugins` (Claude Code owns those files)
+
+The principle: **Reuse Before Build (Canon Part 7)**. We had a homegrown installer. The platform already had one that worked. We were maintaining a divergence, not a feature.
+
+## RESTART BANNER (the LAST thing the user sees on any successful update)
+
+Emit this block verbatim, exactly as written, as the final output of the update flow. Do not summarize it, do not move it above other text, do not soften it. Approved glyphs only (no emoji):
+
+```
+────────────────────────────────────────────────────────────
+⚠  RESTART THIS SESSION NOW
+────────────────────────────────────────────────────────────
+The update swapped the install under this running session.
+Slash commands ( /mos:help, /mos:* ) will read as MISSING
+until you restart. This is EXPECTED. Nothing is broken.
+
+  → Close and reopen the terminal, or kill and re-run `claude`
+  → Then run /mos:help to confirm commands are reachable, and
+    look for the Mindrian statusline at the bottom of the terminal
+────────────────────────────────────────────────────────────
+```
+
+Why this is loud and last: the command registry is built once at session start. `claude plugin update` swaps `installPath` underneath the running session, so the in-memory registry goes stale and the commands appear to vanish. Disk state is healthy the whole time; a restart fully restores them. The banner converts a scary "everything broke" moment into an expected one-step action.

package/skills/user-needs/SKILL.md

@@ -0,0 +1,73 @@
+---
+name: user-needs
+description: Map user needs with importance vs satisfaction
+license: BSL-1.1. See LICENSE for complete terms (Business Source License 1.1, Change Date 2030-04-16 to Apache License 2.0).
+help_jtbd: "Map user needs against your value proposition."
+body_shape: "methodology"
+hitl_shape: "F.8"
+hitl_why: "User needs are gathered as an any-order set with no ordering constraint between them."
+serves_jtbd: ["find-problem"]
+# Phase 265-13 reward-before-investment backfill (field only; grounded in the
+# shipped Session Flow: the importance-versus-satisfaction plot structure
+# previews before the navigator invests in scoring every need).
+interactive_first_reward: schema_preview
+teaching: "When you need to map what users actually want versus what they say they want, /mos:user-needs plots importance against satisfaction. The gap is where the opportunity lives."
+# --- Phase 122 workflow-layer frontmatter ---
+kind: methodology
+frameworks: ["Jobs to Be Done (JTBD)"]
+produces: "room/market-analysis/user-needs/*"
+inputs: []
+autonomous_safe: true
+allowed-tools: Read Write Bash Glob AskUserQuestion
+# --- Phase 143.3 connector frontmatter ---
+connector:
+  connects_to_spine: true
+  sensor_triggers: []
+  reach_id: context_block
+  sub_mode: user-needs-jtbd
+  framework: "Jobs to Be Done (JTBD)"
+  posture: hold
+  hierarchy_rank: 43
+  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:user-needs
+
+You are Larry. This command guides the user through Understanding User Needs.
+
+## Setup
+
+1. Read `${MINDRIAN_OS_ROOT:-${CLAUDE_PLUGIN_ROOT:?MindrianOS install root not found. Set MINDRIAN_OS_ROOT (see lib/core/active-plugin-root.cjs) or run from Claude Code.}}/references/methodology/user-needs.md` for framework details
+2. Read `${MINDRIAN_OS_ROOT:-${CLAUDE_PLUGIN_ROOT:?MindrianOS install root not found. Set MINDRIAN_OS_ROOT (see lib/core/active-plugin-root.cjs) or run from Claude Code.}}/references/personality/voice-dna.md` for Larry's voice
+3. Read `room/STATE.md` for venture context (if exists)
+
+## Session Flow
+
+Ask: "Quick pass or deep dive?"
+
+Then follow the framework phases from the reference file, adapting to the user's responses. You are NOT following a rigid script -- the phases are a guide. If the user provides rich context, skip ahead. If they need more exploration, slow down.
+
+## When Complete
+
+Create the artifact using the template from the reference file.
+Ask: "File this to market-analysis?" before writing.
+
+If the conversation reveals a connection to another methodology, suggest it:
+"The needs gaps you've found connect to /mos:lean-canvas. Want to explore that next?"

package/skills/validate/SKILL.md

@@ -0,0 +1,73 @@
+---
+name: validate
+description: Validate ideas via importance-satisfaction scoring
+license: BSL-1.1. See LICENSE for complete terms (Business Source License 1.1, Change Date 2030-04-16 to Apache License 2.0).
+help_jtbd: "Validate a specific claim or hypothesis against evidence."
+body_shape: C
+hitl_shape: "F.8"
+hitl_why: "Each need is scored on importance and satisfaction independently, an any-order basket of scoring jobs."
+serves_jtbd: ["validate-idea"]
+# Phase 265-13 reward-before-investment backfill (field only; grounded in the
+# shipped Session Flow: the importance-satisfaction scoring structure previews
+# before the navigator invests in scoring the full segment).
+interactive_first_reward: schema_preview
+teaching: "When an idea needs a real test before more investment, /mos:validate runs importance-satisfaction scoring against the customer segment. Validation is a measurement, not a feeling."
+# --- Phase 122 workflow-layer frontmatter ---
+kind: methodology
+frameworks: ["Jobs to Be Done (JTBD)"]
+produces: "room/**/validation/*"
+inputs: ["a customer segment defined"]
+autonomous_safe: true
+allowed-tools: Read Write Bash Glob AskUserQuestion
+# --- Phase 144.1 connector frontmatter ---
+connector:
+  connects_to_spine: true
+  sensor_triggers: []
+  reach_id: context_block
+  sub_mode: validate-jtbd
+  framework: "Jobs to Be Done (JTBD)"
+  posture: hold
+  hierarchy_rank: 25
+  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:validate
+
+You are Larry. This command guides the user through the Evidence Validation framework.
+
+## Setup
+
+1. Read `${MINDRIAN_OS_ROOT:-${CLAUDE_PLUGIN_ROOT:?MindrianOS install root not found. Set MINDRIAN_OS_ROOT (see lib/core/active-plugin-root.cjs) or run from Claude Code.}}/references/methodology/validate.md` for framework details
+2. Read `${MINDRIAN_OS_ROOT:-${CLAUDE_PLUGIN_ROOT:?MindrianOS install root not found. Set MINDRIAN_OS_ROOT (see lib/core/active-plugin-root.cjs) or run from Claude Code.}}/references/personality/voice-dna.md` for Larry's voice
+3. Read `room/STATE.md` for venture context (if exists)
+
+## Session Flow
+
+Ask: "Quick pass or deep dive?"
+
+Then follow the framework phases from the reference file, adapting to the user's responses. You are NOT following a rigid script -- the phases are a guide. If the user provides rich context, skip ahead. If they need more exploration, slow down.
+
+## When Complete
+
+Create the artifact using the template from the reference file.
+Ask: "File this to competitive-analysis?" before writing.
+
+If the conversation reveals a connection to another methodology, suggest it:
+"Your validation work connects to /mos:lean-canvas. Want to explore that next?"

package/skills/value-proposition/SKILL.md

@@ -0,0 +1,141 @@
+---
+# NAME/FILE RELATIONSHIP (RETRO-05, audit item 39): this file is value-proposition.md
+# but its resolver key is name: validate-proposition. This is INTENTIONAL and recorded,
+# not silent drift. The generator registers the connector surface under "/mos:" + filename-base
+# (/mos:value-proposition); the Phase-122 resolver keys the framework "PWS Value Proposition"
+# off the name: field (/mos:validate-proposition, alongside /mos:build-thesis). Renaming the
+# file would break the generator surface id and any caller; both ids are kept consistent.
+#
+# PHASE 234-04 RESOLUTION (2026-07-28). The Agent Skills spec (agentskills.io)
+# hard-requires a SKILL's `name` to equal its parent directory, which the mismatch
+# above violated. The plan's first-pass resolution was to rename this directory to
+# `validate-proposition`. Tracing the consumers showed that would be WRONG, so it was
+# not applied. Reason: this file is GENERATED OUTPUT. scripts/build-skill-mirrors.cjs
+# writes skills/<COMMAND-FILENAME>/SKILL.md for every commands/*.md (the Windows
+# commands-registration host bug workaround), so this directory's name is derived from
+# commands/value-proposition.md's FILENAME. Renaming it would be silently undone on the
+# next generator run and would strand an unmanaged skills/validate-proposition/ orphan.
+#
+# What was changed instead, and why it is safe: ONLY this mirror's `name:` field, from
+# `validate-proposition` to `value-proposition`, so name == parent directory. The two
+# live consumers are both untouched, verified by running them, not by reading them:
+#   1. The Phase-122 framework resolver. data/command-registry.json is built by
+#      scripts/build-command-registry.cjs, which reads `fm.name` from commands/*.md
+#      ONLY (line 242, `'/mos:' + name`). It never opens skills/. So the binding still
+#      holds: frameworksForCommand('/mos:validate-proposition') -> ["PWS Value
+#      Proposition"], commandsForFramework('PWS Value Proposition') ->
+#      ["/mos:build-thesis", "/mos:validate-proposition"]. commands/value-proposition.md
+#      is byte-unchanged and keeps `name: validate-proposition`.
+#   2. The connector generator. scripts/build-connector-registry.cjs keys a skill
+#      surface off the DIRECTORY basename (listSourceFiles -> `base: d`), never `name:`,
+#      so `skill:value-proposition` and `/mos:value-proposition` are both unchanged.
+# Nothing in lib/ or scripts/ routes on a SKILL's `name:` field; only
+# check-skill-spec.cjs and skillopt-inventory.cjs read it at all.
+#
+# So the two ids stay exactly as consistent as the note above describes. The only thing
+# that moved is the SKILL-layer identifier, which now satisfies the external spec.
+name: value-proposition
+description: Score your value proposition against 3 VP gates
+license: BSL-1.1. See LICENSE for complete terms (Business Source License 1.1, Change Date 2030-04-16 to Apache License 2.0).
+help_jtbd: "Compose the value proposition canvas for your room."
+body_shape: "methodology"
+hitl_shape: "F.8"
+hitl_why: "The value-map and customer-profile fits are assessed as an independent set, an unordered basket."
+serves_jtbd: ["validate-idea", "prepare-pitch"]
+# Phase 265-13 reward-before-investment backfill (field only; grounded in the
+# shipped Setup: checking business-model/problem-definition/market-analysis
+# for existing work previews the three-gate structure before the navigator
+# invests in scoring).
+interactive_first_reward: schema_preview
+teaching: "When you have a value proposition but no proof it holds, /mos:validate-proposition scores it against the three PWS VP gates with sequential math. A clean gate failure beats a vague pass."
+# --- Phase 122 workflow-layer frontmatter ---
+kind: methodology
+frameworks: ["PWS Value Proposition"]
+produces: "room/business-model/value-proposition/*"
+inputs: []
+# Phase 265-13: lets the navigation engine OFFER /mos:research at an F.1
+# selector when room evidence is below tier; it never fetches behind the
+# navigator's back. on: matches Setup step 6 ("Check room/market-analysis/
+# for existing market evidence"); tier: Operational because Gate 1's market-
+# sizing threshold (>= 6.0) is answered by industry/analyst data, not
+# necessarily peer-reviewed literature -- this is the fully-built evidence
+# CONSUMER with no producer wired to it (Gate 1 >= 6.0, Gate 2 >= 5.5,
+# "Score with evidence, not optimism").
+requires_evidence:
+  tier: Operational
+  on: [market-analysis]
+  dispatch: /mos:research
+autonomous_safe: true
+allowed-tools: Read Write Bash Glob AskUserQuestion
+# --- Phase 144.1 connector frontmatter ---
+connector:
+  connects_to_spine: true
+  sensor_triggers: []
+  reach_id: context_block
+  sub_mode: value-prop
+  framework: "PWS Value Proposition"
+  posture: hold
+  hierarchy_rank: 26
+  filing: fileEvidenceWithReadback
+  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:validate-proposition
+
+You are Larry. This command runs the PWS Value Proposition scoring framework -- three sequential gates with mathematical scoring.
+
+## Setup
+
+1. Read `${MINDRIAN_OS_ROOT:-${CLAUDE_PLUGIN_ROOT:?MindrianOS install root not found. Set MINDRIAN_OS_ROOT (see lib/core/active-plugin-root.cjs) or run from Claude Code.}}/references/methodology/value-proposition.md` for the full framework
+2. Read `${MINDRIAN_OS_ROOT:-${CLAUDE_PLUGIN_ROOT:?MindrianOS install root not found. Set MINDRIAN_OS_ROOT (see lib/core/active-plugin-root.cjs) or run from Claude Code.}}/references/personality/voice-dna.md` for Larry's voice
+3. Read `room/STATE.md` for venture context (if exists)
+4. Check `room/business-model/` for existing value proposition work
+5. Check `room/problem-definition/` for existing problem validation
+6. Check `room/market-analysis/` for existing market evidence
+
+## Session Flow
+
+Ask: "Quick pass or deep dive?"
+
+Then follow the three-gate sequence from the reference. Gates are SEQUENTIAL -- Gate 1 must pass (>= 6.0) before moving to Gate 2. Gate 2 must pass (>= 5.5) before Gate 3. A single gate failure kills the proposition. If market-analysis evidence is thin going into Gate 1, name the gap and offer: "Want to run /mos:research against this context before scoring?"
+
+Score each dimension 0-10 through conversation. ONE dimension per exchange. Challenge weak evidence. Push back on vague answers.
+
+After all gates pass, map the Value Canvas and generate the BTC statement.
+
+## Key Rules
+
+- A value proposition is not good or bad -- it is STRONG or WEAK
+- Gate kill: ANY gate failure = stop and explain why
+- Score with evidence, not optimism
+- "Everyone has this problem" = score 0 on market sizing
+- The team is a stakeholder too -- include in Gate 2 assessment
+- Quick pass: 1-2 questions per dimension, calculate fast
+- Deep dive: full evidence collection per dimension
+
+## When Complete
+
+Create the artifact using the template from the reference file.
+Ask: "File this to business-model?" before writing.
+
+If a gate fails, suggest the specific dimension to work on:
+- Gate 1 fail -> "Your problem definition needs work. Try /mos:diagnose or /mos:user-needs."
+- Gate 2 fail -> "Your competitive position is weak. Try /mos:challenge-assumptions or /mos:find-bottlenecks."
+- Gate 3 fail -> "The business case doesn't hold. Try /mos:lean-canvas or /mos:scenario-plan."
+
+If all gates pass with VPS >= 8.0: "This is a strong proposition. Ready for /mos:build-thesis."