Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/jsagir/mindrian-os-plugin/llms.txt

Use this file to discover all available pages before exploring further.

When you suspect your work touches a pattern in another field, /mos:find-connections traces cross-domain links through the Brain graph. It surfaces the connections you did not know to look for — not by keyword matching, but by meaning. The goal is the aha moment: “Your problem in domain A has the same structure as a solved problem in domain B, and the approach that worked there is directly applicable.”

Usage

/mos:find-connections
/mos:find-connections "<concept or domain>"
/mos:find-connections "<domain A> and <domain B>"
ArgumentDescription
(none)Infers the exploration target from your room’s primary domain and problem definition
"<concept>"Searches for cross-domain connections anchored to a specific concept or domain
"<A> and <B>"Finds bridging concepts and frameworks that connect two named domains
This command requires Brain to be connected. Without Brain, cross-domain pattern discovery is unavailable. Run /mos:setup brain to configure Brain, or visit the Brain access page to get an API key.

What Happens

1

Identify the exploration target

If you provided a concept or domain with the command, Larry uses it directly. If no argument was given, Larry infers from room state — the venture’s primary domain, key concepts from problem-definition/, or frameworks currently in use. If neither is available, Larry asks: “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 (Brain graph query)

Larry runs the brain_concept_connect Cypher pattern via brain_query against your concept, pulling all immediate graph neighbors with their relationship types and confidence scores. This traverses Brain’s Neo4j framework graph — graph-structure matching, not keyword search.
3

Cross-domain bridge discovery

If you provided two domains, Larry runs the brain_cross_domain Cypher pattern via brain_query to find bridging concepts and frameworks that connect them through shared relationships. If only one domain was provided, Larry picks a surprising second domain from the first query’s results and runs the cross-domain pattern to surface unexpected bridges.
4

Surface the aha moments

Larry focuses on three types of insight:
  • Unexpected connections — links between fields that seem unrelated on the surface
  • Bridging frameworks — methodology frameworks that appear in both domains (structural similarities)
  • Analogy potential — direct translation: “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, Larry suggests the methodology command that could develop it further — build the analogy into a structured argument, trace a trend, dig into root cause, or map the domain intersection.

What the Brain Queries

/mos:find-connections draws on Brain’s Neo4j framework graph via brain_query — Cypher traversals over 27,904 nodes and 19,987 relationships.
Graph layerWhat it contains
Concept nodes (9,131)Domain concepts and cross-domain bridges
Framework nodes (748)Innovation and methodology frameworks
FEEDS_INTO edges (163)Framework-sequencing relationships — one framework’s output becomes the next’s input
ADDRESSES_PROBLEM_TYPEWhich framework applies to which problem class
TRANSFORMS_OUTPUT_TOHow one framework’s output becomes another’s input
The Cypher traversals find not just structural neighbors, but why things connect — bridging frameworks, sequencing chains, and cross-domain paths — drawing on 30+ years of classroom-observed methodology relationships.

Good Use Cases

Stuck on a problem

When you have been working in one domain and cannot see a path forward, finding out how another field solved the structurally identical problem can unlock the next move.

Validating an analogy

When you suspect your situation resembles a known pattern in another industry, this command confirms or refines that analogy with methodology-grounded evidence.

Discovering precedents

When a solution seems novel, cross-domain search often surfaces historical precedents — times this problem was solved in a different context and what the outcomes were.

Bridging two fields

When your venture sits at the intersection of two domains, this command maps the frameworks that already operate in both, giving you a methodology vocabulary for the intersection.

Tier 0 Behavior (Without Brain)

Without Brain connected, /mos:find-connections cannot run its semantic cross-domain search. The command will tell you: “This command needs Larry’s Brain connected. Run /mos:setup brain to set it up.” The five commands that lose enrichment without Brain are listed in the troubleshooting guide. All other commands — including /mos:research, /mos:graph, /mos:opportunities, and /mos:qualify-opportunity — continue working fully without Brain.

Examples

# Infer the exploration target from your room
/mos:find-connections

# Search for cross-domain connections anchored to a specific challenge
/mos:find-connections "pricing model for two-sided marketplace"

# Find what bridges two specific domains
/mos:find-connections "healthcare and gaming"

# Explore a methodology concept
/mos:find-connections "jobs to be done in regulated industries"

/mos:graph

Query the local room graph for connections already filed across your artifacts.

/mos:research

Pull fresh web evidence on the analogy or bridge domain that find-connections surfaced.

/mos:opportunities

Scan for funding opportunities after cross-domain discovery reveals a new angle.

/mos:qualify-opportunity

Qualify a candidate opportunity that a cross-domain connection helped surface.

Build docs developers (and LLMs) love