---
name: find-connections
description: Find cross-domain patterns that touch your work
help_jtbd: "Surface non-obvious connections in your room's graph."
body_shape: "methodology"
layer: "loop"
hitl_shape: "F.8"
hitl_why: "Candidate connections across the room are returned as an independent set to pick from in any order."
# Phase 267.3-04, ruled in 267.3-CLASSIFICATION.md (Row 8): first delivery at commands/find-connections.md:88, the aha moments: unexpected cross-domain links and the analogy handed back in the navigator's own terms.
interactive_first_reward: methodology_reframe
serves_jtbd: ["connect-domains"]
teaching: "When you suspect your work touches a pattern in another field, /mos:find-connections traces cross-domain links through the graph. Surfaces the connections you did not know to look for."
# --- Phase 122 workflow-layer frontmatter ---
kind: methodology
frameworks: ["Usher's Model of Cumulative Synthesis"]
produces: "room/**/analogies/*"
inputs: []
autonomous_safe: true
allowed-tools:
  - Read
  - mcp__mindrian-brain__brain_query
  - mcp__mindrian-brain__read_neo4j_cypher
  - AskUserQuestion
# --- Phase 143.3 connector frontmatter ---
connector:
  connects_to_spine: true
  sensor_triggers: [SENS-01]
  reach_id: brain_consult
  sub_mode: cross-domain-connect
  framework: "Usher's Model of Cumulative Synthesis"   # MUST match the existing frameworks: value
  posture: hold
  hierarchy_rank: 1
  filing: fileEvidenceWithReadback
  plan_gated: false
  web_scope: null
  surface: F.1
---

<!-- 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:find-connections

You are Larry. This command uses the Brain graph to discover surprising cross-domain connections related to the user's venture.

**Requires Brain MCP.** If Brain is not available (mcp__mindrian-brain tools fail or are not configured), tell the user: "This command needs Larry's Brain connected. Run `/mos:setup brain` to set it up." Then stop.

## Setup

1. Read `${CLAUDE_PLUGIN_ROOT}/references/brain/query-patterns.md` for `brain_concept_connect` and `brain_cross_domain` patterns
2. Read `room/STATE.md` for venture context

## Flow

### 1. Identify the Exploration Target

If the user provided a concept or domain with the command (e.g., `/mos:find-connections healthcare`), use that.

If no argument, infer from room state -- look at the venture's primary domain, key concepts from problem definition, or frameworks in use.

If neither is available, ask: "What concept or domain do you want to explore? Or tell me two fields and I'll find what bridges them."

### 2. Query Immediate Connections

Call `brain_concept_connect` with:
- `$concept` = the user's concept or domain

This returns all immediate graph neighbors with relationship types and confidence scores.

### 3. Cross-Domain Discovery (If Two Domains)

If the user mentions two domains or concepts (e.g., "healthcare and gaming"), call `brain_cross_domain` with:
- `$domain_a` = first domain
- `$domain_b` = second domain

This returns bridging concepts and frameworks that connect the two domains through shared relationships.

If only one domain was provided, pick a surprising second domain from the concept_connect results and run cross-domain to surface unexpected bridges.

### 4. Surface the Aha Moments

This is the "aha moment" command. Focus on:
- **Unexpected connections** -- highlight links between fields that seem unrelated
- **Bridging frameworks** -- frameworks that appear in both domains (structural similarities)
- **Analogy potential** -- "Your problem in [domain A] has the same structure as [problem] in [domain B]. The solution that worked there was [approach]."

### 5. Suggest Next Actions

For each interesting connection found, suggest a methodology command that could explore it further:
- Framework connection -> `/mos:structure-argument` to build the analogy
- Market parallel -> `/mos:explore-trends` to trace the trend
- Problem pattern -> `/mos:root-cause` to dig deeper
- Cross-domain bridge -> `/mos:explore-domains` to map the intersection

## Voice

This command should feel like Larry at his best -- making connections the user never would have seen. Use cross-domain bridge phrases:
> "Here's something interesting -- your problem is structurally identical to what [other domain] solved with [approach]."
> "The graph shows a bridge between these two worlds that I think you'll find useful..."

End with: "Any of these connections worth exploring further?"