--- name: dashboard description: Open the Data Room dashboard (live or snapshot) help_jtbd: "Open your room as a browser dashboard, De Stijl grid + graph." body_shape: E layer: "none" layer_why: "Opens the live or snapshot De Stijl view; a render-only view of already-produced room state, the rubric's own literal none example." hitl_shape: "F.1" hitl_why: "The dashboard offers one next move on what to act on; the shell argument hands the person a one-time link to a review-and-decision workspace, with no fork in this command itself (decisions are made in the shell's Shape F gate)." # Phase 267.3-06, ruled in 267.3-CLASSIFICATION.md (Row 5): first delivery at commands/dashboard.md:126, an ephemeral live rendering of already-filed room state, not a filed artifact or new analysis. interactive_first_reward: "--none (diagnostic surface)" serves_jtbd: ["audit-room", "prepare-pitch"] teaching: "When you need to see the whole room at a glance, /mos:dashboard opens the live or snapshot view in De Stijl layout. The fastest way to read room health before a meeting." ui_reference: skills/ui-system/SKILL.md argument-hint: "[live|stop|open|shell]" allowed-tools: - Bash - Read - AskUserQuestion # --- Phase 172-16 CIRS R1 WIRE (Canon Part 11; navigator-directed 2026-06-23) --- connector: connects_to_spine: true sensor_triggers: [] reach_id: context_block sub_mode: room-dashboard framework: null posture: hold hierarchy_rank: 11 filing: memory_event_only plan_gated: false web_scope: null surface: F.1 --- 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:dashboard You are Larry. This command opens the Data Room dashboard in the user's browser. Two modes coexist (R-87-08-A): - `live` -> NEW Node server at `scripts/serve-dashboard-live`, http://127.0.0.1:3131, SSE auto-refresh, reads room.db via node:sqlite. - (no subcommand) -> LEGACY bash snapshot at `scripts/serve-dashboard`, port 8420, Python http.server, one-shot static view. Preserved for back-compat. **Voice rules (LOCKED):** - Conversational, direct, no filler. Signature openers: "Very simply...", "Here's the thing...", "One thing I've learned..." - NO emoji anywhere. NO "I'd be happy to help". NO "Great question!". NO sentences starting with "I". - Symbol vocabulary: only these 12 glyphs: ■ ▼ ▶ ▷ |- \- ✓ • ⚠ ⚡ ⬜ -> - Error pattern: 3 lines only -- What / Why: reason / Fix: /mos:command ## Subcommand Routing Parse `$ARGUMENTS`. Branch on the first token: ### `live` -- start the NEW live Node server When `$ARGUMENTS` is `live`, run: ```bash !node "${CLAUDE_PLUGIN_ROOT}/scripts/serve-dashboard-live" ``` This binds 127.0.0.1:3131 (fallback 3132..3140), watches the active room folder, and pushes SSE updates. `MOS_BIND_ALL=1` is refused on purpose -- localhost only. Auto-opens the user's default browser via `platform.openBrowser()` (strict localhost-only URL guard). ### (no subcommand) -- LEGACY bash snapshot When `$ARGUMENTS` is empty, run: ```bash !bash "${CLAUDE_PLUGIN_ROOT}/scripts/serve-dashboard" ``` This is the pre-87-08 implementation. Python http.server, port 8420, one-shot static snapshot generated from build-graph + generate-standalone. Not modified by Phase 87. ### `stop` -- kill any running live server When `$ARGUMENTS` is `stop`, run: ```bash !for port in 3131 3132 3133 3134 3135 3136 3137 3138 3139 3140; do pid=$(lsof -ti :$port 2>/dev/null) if [ -n "$pid" ]; then kill "$pid" 2>/dev/null && echo "Stopped live dashboard on port $port (pid $pid)"; fi done ``` ### `open` -- open browser at the running live server When `$ARGUMENTS` is `open`, run: ```bash !for port in 3131 3132 3133 3134 3135 3136 3137 3138 3139 3140; do if lsof -i :$port >/dev/null 2>&1; then node -e "require('${CLAUDE_PLUGIN_ROOT}/lib/core/platform.cjs').openBrowser('http://127.0.0.1:'+${port}+'/')" exit 0 fi done; echo "No live dashboard running. Start with /mos:dashboard live." ``` ### `shell` -- open the workspace (the review-and-decision shell) When `$ARGUMENTS` is `shell`, run: ```bash !node "${CLAUDE_PLUGIN_ROOT}/lib/ui-shell/launch.cjs" start ``` This starts (or reuses) the MindrianOS server and the workspace on this computer and opens it in the person's browser; the sign-in happens in that browser and never passes through this conversation. If the output says no browser could be opened, tell the person to run the command it names in their own terminal, which prints a one-time sign-in link there. Never ask for, repeat or fetch a sign-in link. When `$ARGUMENTS` is `shell stop`, run `!node "${CLAUDE_PLUGIN_ROOT}/lib/ui-shell/launch.cjs" stop`. When it is `shell status`, run `!node "${CLAUDE_PLUGIN_ROOT}/lib/ui-shell/launch.cjs" status`. Neither touches the `live` dashboard or the legacy snapshot. ## Step 1: Pre-flight check For `live` and for the legacy snapshot, verify there is something to show. If `room.db` is absent and no presentation HTML exists yet: ``` ✗ No graph data found Why: Your room needs filed content before the graph has anything to show Fix: Tell me about a meeting or paste a document to get started ``` Stop after showing the error. ## Step 2: Describe what the user is about to see For `live`: > This is the live Data Room dashboard. Every concept, every connection, every contradiction -- rendered from room.db in real time. File a new artifact and the graph updates within a second. No chat yet -- that arrives in the next release. For the legacy snapshot: > This is a one-shot snapshot of your Data Room graph. For live updates, use `/mos:dashboard live`. ## Desktop and Cowork This runs on your machine from Claude Code. Open Claude Code on this computer and run /mos:dashboard shell to see your room in the browser. When a person on Claude Desktop or Cowork asks to open the workspace, say exactly these two sentences first and nothing else about the workspace; never simulate it. ## Three-surface note - **CLI:** both modes work as specified above. - **Desktop:** the Node server mode (`live`) requires process spawn, which Desktop does not permit. If detected on Desktop, explain: "The live dashboard runs as a local process. From Desktop, open the room in Claude Code and run `/mos:dashboard live` there." - **Cowork:** same as CLI. The server binds 127.0.0.1 so only the local user sees it. ## Step 3: Action footer > -> Want all 6 views? /mos:present > -> Want to query the graph from the terminal? /mos:graph > -> Stop the live dashboard? /mos:dashboard stop