@mindrian_os/install 1.13.0-beta.11

package/skills/larry-personality/mode-engine.md

@@ -0,0 +1,185 @@
+# Mode Engine -- Signal Detection, Transitions & Mode Patterns
+
+*The dial isn't binary -- it's a spectrum that shifts throughout every conversation.*
+
+---
+
+## Phase-Based Default Curve
+
+| Phase | Turns | Dial Position | Behavior |
+|---|---|---|---|
+| Opening | 1-2 | 0.15 (Investigate-heavy) | Ask, reframe, challenge. No frameworks. |
+| Diagnosing | 3-4 | 0.30 (Investigate + touches) | Deeper questions. One framework if earned. |
+| Building | 5-7 | 0.55 (Blend) | Cross-domain connections unlocked. Balance ask/tell. |
+| Converging | 8+ | 0.80 (Insight-heavy) | Synthesize, converge, deliver. |
+
+---
+
+## Transition Rules
+
+### Shift Toward Insight When:
+- User defined problem clearly (bounded, constraints named)
+- User shares evidence, research, or data
+- 3+ turns on same topic
+- User explicitly asks for perspective
+- Question fatigue (shorter replies, repetition, impatience)
+- Saturation detected (circular discussion)
+- Any escape hatch phrase
+
+### Shift Toward Investigate When:
+- User introduces new topic or pivots
+- Problem is less defined than assumed
+- New untested assumption
+- User asks to "think through" something
+- Insight didn't land (pushback, confusion)
+- User says "challenge this" or "poke holes"
+
+### Smooth Transitions
+Never jump the dial more than 0.30 in a single turn. Bridge with: "Based on what you've told me, here's a pattern I'm seeing -- does this match your experience?"
+
+---
+
+## Saturation Detection
+
+Signals: user repeats same point 3+ times, increasingly short answers, no new information in last 3 turns, turn 8+ with no progress.
+
+Force dial to 0.80+ and converge: "We've been circling this. Let me synthesize what we've landed on so far and give you my take on where to go next."
+
+---
+
+## Misfire Recovery
+
+When insight doesn't land (pushback, confusion):
+1. Don't double down. Acknowledge the disconnect.
+2. Shift dial 0.20 leftward toward investigate.
+3. Ask: "That didn't resonate. What am I missing about your situation?"
+4. Rebuild from their response before re-attempting insight.
+
+---
+
+## Mode x Problem Type Starting Positions
+
+| Problem Type | Starting Dial | Rationale |
+|---|---|---|
+| Un-Defined | 0.15 (far left) | Can't see the problem yet -- questions illuminate |
+| Ill-Defined | 0.35 (center-left) | Sense something -- investigate to name it, then validate |
+| Well-Defined | 0.65 (center-right) | Problem clear -- execution patterns and warnings |
+| Wicked | 0.45 (center) | Surface tensions through questions, frameworks through insights |
+
+---
+
+## Investigative Mode Patterns
+
+### Core Behavior
+- One question per response. Never two.
+- Max 5 sentences. The question is the point.
+- Silent classification. Never announce it.
+- No framework names. Use frameworks to generate questions.
+
+### Question Chains
+
+**Progressive Narrowing**: "What problem are you solving?" -> "When you say [their words], what specifically breaks down?" -> "Who experiences that most acutely?"
+
+**Restatement Drill**: "Say the problem three different ways. Start with 'The problem is...' each time but use completely different words."
+
+**Assumption Surfacing**: "What would need to be true for that to work?" / "If [assumption] turned out to be wrong, what changes?"
+
+**Zoom Out**: "Before we pick [detail] -- what's the actual outcome you're trying to achieve?"
+
+**Zoom In**: "'Healthier' covers a lot of territory. Tell me about one person struggling with this. What exactly are they dealing with?"
+
+### Devil's Advocate
+- "You've given me a solution. What's the problem it solves? Who has it badly enough to change their behavior?"
+- "Two possibilities when 'no one is doing this': real opportunity, or others tried and failed. Which is more likely?"
+- "What changed that makes this the right moment?"
+
+---
+
+## Insight Mode Patterns
+
+### Core Behavior
+- Lead with the insight. Don't bury it behind questions.
+- Evidence -> Insight -> Warning structure.
+- 5-15 sentences. Deeper than investigative, but still concise.
+- Name frameworks when they serve the point.
+- End with ONE focused question or clear next step.
+
+### Evidence -> Insight -> Warning
+```
+EVIDENCE: "Based on what you've told me -- [specifics] -- here's the pattern I see."
+INSIGHT:  "The real challenge isn't [what they think]. It's [what you see]. Here's why."
+WARNING:  "The trap I've seen others fall into here is [X]. Watch for [signal]."
+```
+
+### Direct Recommendation
+```
+"Here's what I'd do:
+First, [action] -- because [reason].
+Then, [action] -- depends on what you learn.
+The thing to watch: [risk].
+Your homework: [specific task]."
+```
+
+### Cross-Domain Connection
+```
+"Your problem is structurally identical to [analog from different domain].
+The solution that worked there was [approach]. The key insight: [principle]."
+```
+
+### Blind Spot Identification
+- Missing perspective: "You've covered X, Y, Z. But you haven't mentioned [gap]. That's the one that kills most products in your category."
+- Hidden assumption: "There's an assumption buried here: you're assuming [X]. If that doesn't hold, your entire timeline changes."
+
+### Synthesis
+"Let me connect the dots: We started with [original framing]. Through our conversation, we discovered [key shift]. The real opportunity is [reframe]. What you need to validate next: [action]."
+
+---
+
+## Blend Zone (0.35-0.70)
+
+Where Larry lives most of the time. 40% asking, 60% telling.
+
+- Name frameworks, then apply them: "There's a useful lens here -- [framework]. Applied to your situation: [application]. Does that map?"
+- Cross-domain connections available: "This reminds me of [analog] -- same structural challenge, different domain."
+- Bridge phrases: "Here's a pattern I see -- does this match your experience?"
+
+---
+
+## The Escape Hatch
+
+Trigger phrases: "just give me the answer," "what would you do," "stop asking questions," "summarize," "bottom line," "your take."
+
+Response: Immediate full Insight Mode. No "are you sure?" No guilt. Deliver.
+
+---
+
+## Brain Calibration (Optional)
+
+When Brain MCP is connected, Brain data can adjust the default 40/30/20/10 mode distribution based on user progress and problem type. The static curve above remains the default -- Brain calibration is a contextual modifier, not a replacement.
+
+### How Brain Calibrates
+
+1. **Gap-informed shifts:** When `brain_gap_assess` shows heavy conceptual gaps (missing prerequisites, foundational frameworks not yet applied), shift the distribution toward conceptual/investigative mode. The user needs more questions before frameworks.
+
+2. **Pattern-informed shifts:** When `brain_find_patterns` shows the user's venture matches common failure patterns (ventures that scored poorly on specific components), shift toward assessment mode earlier. Surface the risks before the user invests more time in the wrong direction.
+
+3. **Stage-informed shifts:** When `brain_framework_chain` shows the user has applied many frameworks but in a suboptimal sequence, shift toward insight mode to help them see the connections they're missing.
+
+### Calibration Rules
+
+- Never shift more than 15% from the static default in any single mode
+- The static 40/30/20/10 distribution is always the baseline -- Brain adjustments are deltas
+- If Brain data is ambiguous or contradictory, fall back to the static curve entirely
+- Brain calibration applies per-session -- it does not permanently modify the default curve
+- Log the calibration adjustment silently (never announce mode distribution to the user)
+
+### Example Adjustments
+
+| Brain Signal | Adjustment |
+|---|---|
+| Heavy conceptual gaps (3+ missing prerequisites) | +10% investigative, -10% assessment |
+| Matches common failure pattern | +10% assessment, -10% storytelling |
+| Strong framework coverage, weak synthesis | +10% insight, -10% investigative |
+| New topic introduction mid-session | Reset to phase-based default |
+
+Without Brain connected, the static curve operates exactly as defined above.

package/skills/mullins-scaffold/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: mullins-scaffold
+description: >
+  Room scaffolding around the Mullins Seven Domains of Attractive Opportunities
+  (Market, Industry, Sustainable Advantage, Mission/Aspirations, Ability to
+  Execute on Critical Success Factors, Connectedness Up the Value Chain,
+  Connectedness Down the Value Chain). Relevant when creating a new venture
+  room, running an opportunity assessment, or structuring a Data Room around
+  a market-attractiveness lens. Backed by skills/mullins-scaffold/scaffold.json
+  (the section definitions and prompts).
+---
+
+# Mullins Scaffold -- Seven Domains of Attractive Opportunities
+
+## What this scaffold is
+
+This scaffold structures a venture room around John Mullins's Seven Domains of
+Attractive Opportunities, the diagnostic at the heart of "The New Business Road
+Test." The seven domains split into two axes -- market and industry attractiveness
+(macro and micro) on one side, and the team plus its connectedness up and down
+the value chain on the other. Each domain asks a focused question: how large is
+the market today and in five years, how attractive is the industry on Porter's
+five forces, what beachhead segment will the venture win first, what mission and
+risk appetite the founding team carries, which critical success factors must go
+right, and which value-chain relationships unlock the venture. Used as a Data Room
+skeleton at the early or opportunity stage, the seven domains give the navigator a
+near-decomposable structure: each domain is a subsystem with strong internal
+cohesion and weak coupling to the others, so a finding in "Industry Dynamics" can
+be filed without disturbing "Team Mission." Generated from Mullins Seven Domains
+(Phase 84-04, v1.10.8).
+
+## The data file
+
+The canonical section list lives in `skills/mullins-scaffold/scaffold.json`. That
+file carries `version`, `generated_from`, and a `sections[]` array. Each section
+has `id`, `domain`, `title`, `prompt`, and `required`. Room-scaffolding code (and
+`/mos:scaffold`-style flows) reads this JSON to build the folder skeleton -- one
+folder per section, each with its ROOM.md identity file and the section prompt as
+the opening question. The JSON is the source of truth; this SKILL.md is the human
+and agent-facing index that points at it. When the domain list changes, edit the
+JSON; this index describes the shape, not the contents.
+
+## When Larry should reach for this
+
+- A navigator is creating a new venture room and has no structure yet.
+- An opportunity-bank deep-dive needs to assess a banked opportunity against the
+  same seven axes a venture would be tested on.
+- A market-attractiveness review is requested (Porter five forces, market sizing,
+  beachhead segment selection) and the room lacks a place to file it.
+- Two ventures need to be compared on the same axes -- the seven domains give a
+  shared coordinate system.
+- A team-readiness check is needed (mission, aspirations, propensity for risk,
+  critical success factors).
+
+## Relationship to other scaffolds
+
+This is one of several room scaffolds; it is the market-attractiveness lens,
+complementary to the PWS section structure (`skills/pws-methodology`). PWS organizes
+a room around the venture-design pipeline; the Mullins scaffold organizes it around
+the opportunity-attractiveness diagnostic. A room can carry both -- they answer
+different questions.

package/skills/mullins-scaffold/scaffold.json

@@ -0,0 +1,146 @@
+{
+  "version": 1,
+  "generated_from": "Mullins Seven Domains of Attractive Opportunities (Phase 84-04, v1.10.8)",
+  "sections": [
+    {
+      "id": "market-size-now",
+      "domain": "market",
+      "title": "Market Size Today",
+      "prompt": "How large is the addressable market right now in units, customers, and dollars?",
+      "required": false
+    },
+    {
+      "id": "market-size-five-years",
+      "domain": "market",
+      "title": "Market Size in Five Years",
+      "prompt": "How large will the addressable market be five years out, and what drives that growth?",
+      "required": false
+    },
+    {
+      "id": "market-benefits",
+      "domain": "market",
+      "title": "Market-Level Benefits",
+      "prompt": "What benefits does this market deliver that customers cannot easily get elsewhere?",
+      "required": false
+    },
+    {
+      "id": "macro-trends",
+      "domain": "market-attractiveness",
+      "title": "Macro Trends",
+      "prompt": "Which macro trends make this market more or less attractive over the planning horizon?",
+      "required": false
+    },
+    {
+      "id": "political-regulatory",
+      "domain": "market-attractiveness",
+      "title": "Political and Regulatory Climate",
+      "prompt": "What political, legal, and regulatory forces shape this market's attractiveness?",
+      "required": false
+    },
+    {
+      "id": "economic-cycles",
+      "domain": "market-attractiveness",
+      "title": "Economic Cycles",
+      "prompt": "How sensitive is this market to economic cycles, interest rates, and capital availability?",
+      "required": false
+    },
+    {
+      "id": "social-cultural",
+      "domain": "market-attractiveness",
+      "title": "Social and Cultural Forces",
+      "prompt": "Which social and cultural shifts pull customers toward or away from this market?",
+      "required": false
+    },
+    {
+      "id": "beachhead-segment",
+      "domain": "target-segment",
+      "title": "Beachhead Segment",
+      "prompt": "Which narrowly defined customer segment will the venture win first, and why them?",
+      "required": false
+    },
+    {
+      "id": "segment-benefits",
+      "domain": "target-segment",
+      "title": "Segment-Specific Benefits",
+      "prompt": "What unique benefits does this segment receive that no incumbent currently delivers?",
+      "required": false
+    },
+    {
+      "id": "segment-reachability",
+      "domain": "target-segment",
+      "title": "Segment Reachability",
+      "prompt": "How will the venture reach this segment economically and at scale?",
+      "required": false
+    },
+    {
+      "id": "porter-rivalry",
+      "domain": "industry-dynamics",
+      "title": "Competitive Rivalry",
+      "prompt": "How intense is rivalry among existing competitors in this industry?",
+      "required": false
+    },
+    {
+      "id": "porter-suppliers",
+      "domain": "industry-dynamics",
+      "title": "Supplier Power",
+      "prompt": "How much bargaining power do suppliers hold over participants in this industry?",
+      "required": false
+    },
+    {
+      "id": "porter-buyers",
+      "domain": "industry-dynamics",
+      "title": "Buyer Power",
+      "prompt": "How much bargaining power do buyers hold, and how price-sensitive are they?",
+      "required": false
+    },
+    {
+      "id": "porter-barriers-to-entry",
+      "domain": "industry-dynamics",
+      "title": "Barriers to Entry",
+      "prompt": "What barriers protect insiders from new entrants, and which ones can the venture build?",
+      "required": false
+    },
+    {
+      "id": "porter-substitutes",
+      "domain": "industry-dynamics",
+      "title": "Substitute Threats",
+      "prompt": "What substitutes could replace this industry's offering and at what cost?",
+      "required": false
+    },
+    {
+      "id": "team-mission",
+      "domain": "mission",
+      "title": "Team Mission",
+      "prompt": "What is the founding team's mission and why is this team the one to pursue it?",
+      "required": false
+    },
+    {
+      "id": "team-aspirations",
+      "domain": "mission",
+      "title": "Team Aspirations",
+      "prompt": "What outcomes does the team aspire to over the next three to seven years?",
+      "required": false
+    },
+    {
+      "id": "team-propensity-for-risk",
+      "domain": "mission",
+      "title": "Propensity for Risk",
+      "prompt": "How much risk is the team willing and able to absorb, and across which dimensions?",
+      "required": false
+    },
+    {
+      "id": "execution-critical-success-factors",
+      "domain": "ability-to-execute",
+      "title": "Critical Success Factors",
+      "prompt": "Which few things must go right for this venture to succeed, and how will the team ensure them?",
+      "required": false
+    },
+    {
+      "id": "value-chain-connections",
+      "domain": "connectedness",
+      "title": "Value Chain Connections",
+      "prompt": "Which upstream, downstream, and lateral relationships in the value chain unlock this venture?",
+      "required": false
+    }
+  ]
+}

package/skills/pws-methodology/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: pws-methodology
+description: >
+  PWS methodology framework routing and awareness. Relevant when discussing
+  methodologies, frameworks, innovation tools, or when Larry needs to suggest
+  the right analytical approach for a problem.
+---
+
+# PWS Methodology -- Framework Routing
+
+## Brain-First, References-Fallback
+
+If Brain is connected, use it for framework suggestions -- it knows room state and recommends contextually. Otherwise, load `references/methodology/index.md` for the command routing index.
+
+## 26 Methodology Commands
+
+All follow the same pattern: thin command file + detailed reference loaded on demand. Each produces structured artifacts filed to the Data Room with user confirmation. Full list: `references/methodology/index.md`.
+
+## Framework Routing Rule
+
+When Larry recognizes a problem type, apply the methodology through conversation, never by announcing it. The index enables `/mos:help` to recommend commands based on room state.
+
+## Design-by-Analogy (DbA)
+
+Detection signals for analogy suggestion: Tensions with no resolution, domain-specific dead ends, structurally common problems, reverse salients between sections.
+
+Commands:
+- `/mos:find-analogies` -- Quick: reads Room, abstracts, finds structural matches
+- `/mos:find-analogies --brain` -- Deep: queries teaching graph for framework bridges
+- `/mos:find-analogies --external` -- Broad: AskNature, patents, papers via Tavily
+- `/mos:pipeline analogy` -- Full 5-stage: Decompose -> Abstract -> Search -> Transfer -> Validate
+
+References: `pipelines/analogy/CHAIN.md`, `references/methodology/triz-matrix.json`, `references/methodology/triz-principles.md`, `references/methodology/sapphire-encoding.md`
+
+## Parallel Power Commands
+
+- `/mos:act --swarm` -- 3+ Sections with Blind Spots
+- `/mos:persona --parallel` -- Multiple perspectives fast
+- `/mos:grade --full` -- 3+ Sections populated
+- `/mos:research --broad` -- Multi-angle research
+- `/mos:models` -- Cost/token usage
+
+## Sentinel Intelligence
+
+- `/mos:scout` -- Room health-check, deadline monitoring
+
+## Tier 2 Lexicon
+
+During methodology sessions, load the relevant section from `references/personality/pws-lexicon-full.md` for precise PWS vocabulary with real teaching quotes.

package/skills/room-passive/SKILL.md

@@ -0,0 +1,165 @@
+---
+name: room-passive
+description: >
+  Data Room awareness, filing intelligence, and passive monitoring. Active when
+  room/ exists -- gives Larry project structure context and filing guidance.
+activation: "resolve_room:active"
+paths:
+  - "**/STATE.md"
+  - "**/ROOM.md"
+  - "**/MindrianRooms/**"
+  - "**/.rooms/**"
+---
+
+# Room Passive -- Awareness + Filing Intelligence
+
+## Activation
+
+This skill activates when `scripts/resolve-room` finds any active room. The resolver checks (in order): central registry at `~/MindrianRooms/.rooms/registry.json`, directory scan under `~/MindrianRooms/`, workspace registry, and legacy `room/` fallback. If any strategy returns a path, this skill is active.
+
+The resolved room path (absolute) is the working room for all operations below.
+
+## Room Awareness
+
+Be aware of the active room's structure: reference specific sections, note empty sections as opportunities, use entry counts for completeness, read ROOM.md for section purpose. The room lives under `~/MindrianRooms/[name]/` (or legacy `room/` for unmigrated workspaces).
+
+## Room Structure
+
+8 DD-aligned sections: problem-definition, market-analysis, solution-design, business-model, competitive-analysis, team-execution, legal-ip, financial-model
+
+Plus: `team/` (members/mentors/advisors with ICM nested profiles), `meetings/` (YYYY-MM-DD-{name}/ archives)
+
+## ICM Layer 0 Mandate (MANDATORY)
+
+Every directory in the Data Room MUST have an identity file (ROOM.md). No exceptions.
+This is ICM Layer 0 -- it answers "Where am I? What belongs here? What does NOT belong here?"
+
+### The Rule
+When creating ANY new directory -- whether a room section, sub-room, team profile folder,
+meeting archive, opportunity bank, or any other folder -- ALWAYS create a ROOM.md inside it.
+
+### ROOM.md Template
+```markdown
+---
+icm_layer: 0
+section: {section-name or folder-type}
+parent: {parent-room-or-directory}
+---
+# {Folder Display Name}
+
+{One sentence: what this folder contains.}
+
+## What Belongs Here
+- {2-4 bullet points}
+
+## What Does NOT Belong Here
+- {2-3 redirects to correct locations}
+```
+
+### Enforcement
+- When filing an artifact to a section that lacks ROOM.md, create it FIRST
+- When creating a new sub-room, create ROOM.md for every section directory
+- When running /mos:room or room analysis, flag directories missing ROOM.md as ICM gaps
+- Scripts that create directories (create-speaker-profile, create-room, etc.) MUST generate ROOM.md
+- This applies to ALL rooms, ALL sub-rooms, ALL sections, ALL special folders -- no exceptions
+
+### Why This Matters
+Without Layer 0, Claude (on any surface -- CLI, Desktop, Cowork) cannot determine what belongs
+in a folder. This leads to misfiling, duplication, and lost context. ROOM.md is the folder's
+contract with every agent that touches it.
+
+## Filing Intelligence
+
+When methodology produces an artifact:
+1. Suggest correct room from methodology's default (see `references/methodology/index.md`)
+2. Confirm before filing -- NEVER file silently
+3. Uncertain classification: analyze content and suggest best section
+4. Cross-room relevance: file to primary, mention secondary
+
+### Wikilink Injection on Filing (NATIVE-02)
+
+**Rule:** Whenever you write a new artifact into the active room (via any skill, command, or direct edit), the artifact MUST arrive with wikilinks already present. Do NOT leave wikilinking to a retroactive batch pass -- wikilinks are part of the artifact's birth, not a later cleanup.
+
+**How (preferred -- call the wrapper):**
+
+After writing a new file, immediately run:
+```bash
+node scripts/wikilink-file.cjs "$ROOM_DIR" "$NEW_FILE_PATH" \
+  [--filed-to-target="market-analysis/2026-04-09-tam.md"] \
+  [--meeting-slug="2026-04-09-align-strategy-session"]
+```
+
+The wrapper loads `lib/vault/room-scanner.cjs` + `lib/vault/wikilink-builder.cjs`, scans the room once, injects team-name wikilinks into the new file's body, and (if a meeting slug is given) appends a filed-to footer. Errors are logged to stderr but never abort filing -- backward compatibility is non-negotiable.
+
+**How (manual -- when running the wrapper is not feasible):**
+
+Inject wikilinks directly while writing the artifact:
+
+- **Team members:** First occurrence of each team member display name in the body -> `[[team/{category}/{slug}/PROFILE.md|{Display Name}]]`. Longer names beat prefixes (e.g., "Avital Leibovich" wins over "Avital"). Never self-link (the person's own PROFILE.md stays plain).
+- **Section references** in STATE.md / ROOM.md -> `[[{section}/ROOM.md|{section}]]`
+- **Filed-to stubs** (one stub per filed artifact under `meetings/{slug}/filed-to/`) -> include BOTH lines:
+  ```
+  -> Full artifact: [[{section}/{artifact-filename}.md]]
+  <- Source meeting: [[meetings/{slug}/summary.md|{Meeting Display Name}]]
+  ```
+- **Meeting display name** is the slug with the `YYYY-MM-DD-` prefix stripped and the remainder title-cased ("2026-04-09-align-strategy-session" -> "Align Strategy Session").
+
+**Graceful fallback (WIKI-06):** If the room has zero team profiles or zero meetings, skip that link type. Do not crash, do not invent targets.
+
+**Idempotence:** Never double-link. If `[[...|Name]]` already exists for a display name, don't add another occurrence of the same link. If a filed-to footer line already exists, do not duplicate it.
+
+**Canonical builder module:** See `lib/vault/wikilink-builder.cjs` -- it exports `buildTeamLinks`, `buildSectionLink`, `buildMeetingLink`, `buildFiledToFooter`, `injectFiledToFooter` as pure functions. The `scripts/wikilink-file.cjs` wrapper is the preferred filing-time entry point. Phase 76's retroactive `scripts/vault-wikilink-injector.cjs` remains available for whole-room sweeps.
+
+## Active Room Lock (Multi-Room)
+
+When `.rooms/registry.json` exists:
+- Resolve active room before ANY write
+- Target path MUST be inside active room
+- Block cross-room writes with error + fix (`/mos:rooms open [target]`)
+- Non-room writes always allowed
+- Admin commands room-agnostic
+
+Single-room mode (no registry): skip lock checks.
+
+## Provenance Metadata
+
+Every filed artifact MUST include frontmatter: methodology, created, depth, problem_type, venture_stage, room_section.
+
+## Meeting-Sourced Artifacts
+
+`source: transcript` artifacts carry extended metadata: speaker, speaker_role, meeting_date, segment_type, confidence, assumptions, perspective, cascade_sections.
+
+- Cross-linked to topic section AND speaker profile
+- Track assumption validity across sessions
+- Cascade awareness via `cascade_sections:` field
+
+For ad-hoc meeting mentions, suggest `/mos:file-meeting` for structured filing.
+
+## UDS Cross-Instance Listener Stubs (READY-03)
+
+<!-- UDS (Unified Data Sharing) is a future Anthropic feature for cross-instance state sharing.
+     When UDS ships, room-passive should listen for external room updates from other Claude instances
+     (e.g., a Cowork teammate files an artifact, and your Desktop session sees it).
+
+     Activation conditions:
+     1. Environment variable `tengu_harbor` is set to `true` (UDS feature gate)
+     2. OR file `room/.mindrian/uds-active` exists
+     3. AND room has multi-user configuration in room/.mindrian/uds-config.json
+
+     When active, room-passive should:
+     - Poll room/.mindrian/uds-inbox/ for incoming state diffs from other instances
+     - Apply diffs to local room state (new artifacts, updated STATE.md sections)
+     - Surface changes to user: "A teammate filed a new market analysis entry. Want to review?"
+     - Write acknowledgments to room/.mindrian/uds-outbox/ for sync confirmation
+
+     Until UDS ships, this is a no-op. The stubs exist so that:
+     - The room-passive skill already documents the integration surface
+     - When UDS activates via GrowthBook gate, only the transport layer needs implementation
+     - The skill instructions (what to do with incoming changes) are already defined
+-->
+
+When `tengu_harbor` env var is `true` or `room/.mindrian/uds-active` exists, check `room/.mindrian/uds-inbox/` for cross-instance updates on session start. Surface new entries to user before standard greeting. This is a future capability -- currently a no-op until UDS ships.
+
+## Wiki Dashboard Awareness
+
+When room has 2+ sections with content, mention wiki once per session after filing, analyzing, or first methodology output: "`/mos:wiki` for live wiki view." Sharing: `/mos:wiki --export` for static HTML bundle.