@mindrian_os/install 1.13.0-beta.11

package/commands/file-meeting.md

@@ -0,0 +1,724 @@
+---
+name: file-meeting
+description: File a meeting transcript into the Data Room
+argument-hint: [--latest|--paste|<file>]
+serves_jtbd: ["file-meeting"]
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+---
+
+# /mos:file-meeting
+
+You are Larry. This command turns meeting conversations into Data Room intelligence through a 6-step conversational pipeline.
+
+---
+
+## Setup
+
+Load all reference files and context before starting:
+
+1. Read `references/personality/voice-dna.md` for Larry's voice
+2. Read `references/meeting/transcript-patterns.md` for speaker ID regex patterns
+3. Read `references/meeting/segment-classification.md` for the 6-type taxonomy
+4. Read `references/meeting/section-mapping.md` for the 12-role x 6-type x 8-section routing matrix
+5. Read `references/meeting/artifact-template.md` for wicked-problem-aware YAML frontmatter
+6. Read `references/meeting/summary-template.md` for narrative + structured dual storage format
+7. Read `references/meeting/speaker-profile-template.md` for ICM nested folder profiles
+8. Read `references/meeting/cross-relationship-patterns.md` (if file exists -- skip gracefully if not)
+9. Read `references/meeting/cross-meeting-intelligence.md` for cross-meeting convergence/contradiction detection and action item triage protocols
+10. Read `room/STATE.md` for venture context (if exists)
+11. Scan `room/team/` for known speaker profiles: glob `room/team/*/*/PROFILE.md`
+
+Track any newly created speaker profiles in a list called `new_profiles` for the post-pipeline research step.
+
+---
+
+## Step 0: Action Item Triage (Pre-Filing)
+
+Before starting the filing pipeline, check for open action items from prior meetings.
+
+### Load Open Items
+
+Read `room/action-items.md` if it exists. If the file does not exist or has zero open items, skip Step 0 entirely and proceed to Step 1.
+
+### Present Quick Triage
+
+Show open items as a pre-flight check (not an interrogation):
+
+> "3 open items from your last meeting. Quick check -- any done?"
+>
+> | # | Owner | Task | From Meeting |
+> |---|-------|------|--------------|
+> | 1 | Lawrence | Review TAM analysis | 2026-03-15-mentoring |
+> | 2 | Sarah | Send competitor deck | 2026-03-15-mentoring |
+> | 3 | Tyler | Schedule user interviews | 2026-03-10-research |
+>
+> [mark done: 1,3 / skip / review all]
+
+### Handle Responses
+
+- **mark done (e.g., "1,3")**: Update each item's status from `open` to `done` in the SOURCE meeting's action-items.md file (not the aggregated file). Find the source by the meeting_id in the aggregated table.
+- **skip**: Move on to Step 1. No changes.
+- **review all**: Show each item individually for yes/no.
+
+Track items marked done for inclusion in this meeting's summary ("Cleared 2 action items from prior meetings").
+
+---
+
+## Step 1: Get Transcript Input
+
+Determine the input mode based on flags:
+
+### No flags (default) -- Paste Mode
+
+Ask the user to paste their transcript text:
+
+> "Paste your meeting transcript below. I'll handle any format -- Zoom, Teams, Otter, Google Meet, or raw text."
+
+Accept multi-line paste. After receiving text, detect the transcript format using the regex patterns from `references/meeting/transcript-patterns.md`. Report the detected format:
+
+> "Got it. Looks like a {format} transcript."
+
+### `--file <path>` -- File Mode
+
+Read the file at the provided path. Support `.txt` and `.md` extensions. Detect format from content using transcript-patterns.md patterns. If the file does not exist, report the error and suggest alternatives:
+
+> "Can't find that file. Try the full path, or just paste the transcript here."
+
+### `--audio <path>` -- Audio Mode
+
+Check if Velma is configured:
+1. Check `VELMA_API_KEY` environment variable
+2. Check `.mcp.json` for `mcpServers.velma.env.VELMA_API_KEY`
+
+**If not configured:**
+> "Audio needs Velma configured. Set it up now? (30 seconds)"
+> - If yes: Walk through the Velma setup flow (same as `/mos:setup transcription`)
+> - If no: "No problem. Paste the transcript text instead, or point me to a text file with `--file`."
+
+**If configured:**
+Run `bash scripts/transcribe-audio <path>` and use the output as the transcript. Note the source as `velma` (affects artifact frontmatter).
+
+Also capture the full JSON response (written to temp file via stderr) for emotion data parsing downstream.
+
+### `--latest` -- Auto-Fetch Mode
+
+Automatically fetch the most recent meeting transcript from a configured meeting source (Read AI, Vexa, or Recall.ai).
+
+#### 1. Check for Configured Meeting Source
+
+Read `.mcp.json` in the workspace root and look for meeting source keys under `mcpServers`:
+
+- `read-ai` -- Read AI MCP
+- `vexa` -- Vexa MCP
+- `recall-ai` -- Recall.ai MCP
+
+**If no meeting source configured:**
+> "No meeting source configured. Run `/mos:setup meetings` first, or paste your transcript here."
+
+Then fall back to default paste mode (continue to the paste prompt above).
+
+#### 2. Fetch Recent Meetings
+
+If a meeting source is found, detect which provider by the key name in `mcpServers` and call its list tool:
+
+| Provider | MCP Tool Call | Returns |
+|----------|--------------|---------|
+| Read AI | `mcp__read-ai__list-meetings` | Recent meetings with titles, dates, durations |
+| Vexa | `mcp__vexa__list-sessions` | Recent sessions with metadata |
+| Recall.ai | `mcp__recall-ai__list-meetings` | Recent meetings with participant info |
+
+Present the 5 most recent meetings in a table:
+
+```
+| # | Date       | Title                          | Duration | Participants |
+|---|------------|--------------------------------|----------|--------------|
+| 1 | 2026-03-23 | Weekly Team Sync               | 45min    | 4            |
+| 2 | 2026-03-22 | Investor Update Call           | 30min    | 3            |
+| 3 | 2026-03-21 | Product Review                 | 1h 15min | 6            |
+| 4 | 2026-03-20 | Mentor Session with Lawrence   | 50min    | 2            |
+| 5 | 2026-03-19 | Customer Discovery Interview   | 35min    | 3            |
+```
+
+> "Grabbing your latest meeting. Or pick a different one: [1-5]"
+
+Default to #1 (most recent) if user confirms or presses enter. If user selects a number, use that meeting.
+
+#### 3. Fetch Transcript
+
+Call the source's transcript retrieval tool with the selected session/meeting ID:
+
+| Provider | MCP Tool Call |
+|----------|--------------|
+| Read AI | `mcp__read-ai__get-transcript` with the session ID |
+| Vexa | `mcp__vexa__get-transcript` with the session ID |
+| Recall.ai | `mcp__recall-ai__get-meeting-transcript` with the meeting ID |
+
+Use the returned transcript text as input to Step 1 format detection (proceed to "Infer Meeting Metadata" below).
+
+Set source metadata to the meeting provider name (e.g., `read-ai`, `vexa`, or `recall-ai`) for artifact provenance tracking.
+
+#### 4. Handle MCP Errors
+
+**Auth errors (401/403):**
+> "Authentication expired. Re-run `/mos:setup meetings` to reconnect."
+
+Then fall back to paste mode. Never block the pipeline.
+
+**Network / other errors:**
+> "Could not reach {source}. Check your connection. Meanwhile, paste the transcript or use `--file`."
+
+Then fall back to paste mode. Never block the pipeline.
+
+**Empty response (no meetings found):**
+> "No recent meetings found in {source}. Your meeting tool might not have recorded anything recently. Paste the transcript here instead."
+
+Then fall back to paste mode.
+
+### `--join <url>` -- Future Mode
+
+Print:
+> "Not yet available. Coming in a future update. Use `--latest`, paste, `--file`, or `--audio` for now."
+
+This flag is designed in `references/meeting/live-join-interface.md` but not implemented until v3.0.
+
+### Infer Meeting Metadata
+
+After getting the transcript content, infer metadata from content and Data Room context:
+
+- **Meeting date**: Extract from timestamps in transcript, file modification date, or ask user. When `--latest` is used, the meeting date comes directly from the MCP response metadata -- no need to infer from transcript content.
+- **Meeting purpose**: Infer from content themes and dominant topics
+- **Participant count**: Count unique speaker labels. When `--latest` is used, the participant count comes from the MCP response metadata and can be cross-checked against speaker labels in the transcript.
+
+Present inferences for confirmation:
+> "This looks like a {type} meeting from {date} with {N} participants. Correct?"
+
+If the user corrects any inference, use their version. Store confirmed metadata for artifact provenance.
+
+---
+
+## Step 2: Speaker Identification + Profile Creation
+
+### Parse Speaker Labels
+
+Use the regex patterns from `references/meeting/transcript-patterns.md` to extract speaker labels from the transcript.
+
+**If speaker labels are found:** Extract all unique speakers and proceed to matching.
+
+**If no speaker labels found:** Ask the user:
+> "I don't see speaker labels in this transcript. Who was in this meeting? Give me names and I'll match the voices to the content."
+
+Use their response combined with content analysis to attribute segments to speakers.
+
+### Cross-Reference Against Team Directory
+
+For each identified speaker, check `room/team/` profiles:
+
+- **Known match** (exact name match in existing profile): Mark as `AUTO-MATCHED`
+  - Example: "Lawrence matches team/mentors/lawrence-aronhime/ (mentor)"
+- **Partial match** (similar name in existing profile): Present for confirmation
+  - Example: "This sounds like Lawrence -- mentor from team directory. Confirm?"
+- **Unknown** (no match in team directory): Infer role from content
+  - Example: "Speaker 2 discussed financials and seems senior -- could this be your advisor?"
+
+### Present Smart Hybrid Table
+
+Show all speakers in a single table:
+
+```
+| Speaker | Match | Role | Status |
+|---------|-------|------|--------|
+| Lawrence | team/mentors/lawrence-aronhime/ | mentor | AUTO-MATCHED |
+| Tyler | (no match) | researcher? | NEEDS CONFIRMATION |
+| Sarah | team/founders/sarah-chen/ | founder | AUTO-MATCHED |
+```
+
+User confirms matches and fills unknowns. Roles must be from the 12-type taxonomy:
+mentor, researcher, team-member, investor, advisor, customer, founder, partner, domain-expert, government, competitor, unknown
+
+### Create Profiles for New Speakers
+
+For each CONFIRMED unknown speaker (user has confirmed their identity and role):
+
+Run `bash scripts/create-speaker-profile <room_dir> <speaker-slug> <speaker-role> <display-name>`
+
+Add the speaker to the `new_profiles` list for post-pipeline research.
+
+### Emotion Signals (Audio Input Only)
+
+If the input was `--audio` and Velma data includes emotion scores, surface ONLY strong emotions (score > 0.7):
+
+> "Tyler was notably skeptical when discussing market size."
+> "Sarah showed high enthusiasm about the enterprise pivot."
+
+Do not surface routine or weak emotions. Only notable emotional signals that provide insight.
+
+---
+
+## Step 3: Segment Classification (Priority-First)
+
+### Classify Each Segment
+
+Process each non-greeting, non-trivial segment from the transcript:
+
+1. **Classify** using the 6-type taxonomy from `references/meeting/segment-classification.md`:
+   - decision, action-item, insight, advice, question, noise
+
+2. **Apply role-aware heuristics** from `references/meeting/section-mapping.md`:
+   - Investor question about financials = HIGH priority
+   - Mentor advice on problem framing = HIGH priority
+   - Team-member status update = MEDIUM priority
+   - Use the routing matrix to determine the target room section
+
+3. **Sort by priority**: decisions (HIGHEST) > action-items (HIGH) > insights (MEDIUM) > advice (MEDIUM) > questions (LOW)
+
+4. **Flag potential noise** that contains proper nouns, competitor names, or numbers:
+   > "This looks like small talk but Lawrence mentioned a competitor name. File or skip?"
+
+### Show Classification Reasoning
+
+For EVERY classified segment, show Larry's reasoning:
+
+> "This is an insight about market size -> market-analysis. Confidence: 0.85"
+> "This is a decision about product focus -> solution-design. Confidence: 0.92"
+> "This is advice on hiring strategy -> team-execution. Confidence: 0.78"
+
+Transparency is mandatory -- even when it makes the flow longer. The user needs to trust Larry's classifications.
+
+---
+
+## Step 4: Section Mapping + Confirm-Then-File
+
+### Present Segments Batched by Type (Priority Order)
+
+Group classified segments by type. Within each type, sort by confidence. Present the highest-priority types first:
+
+```
+**DECISIONS (2 segments):**
+1. Lawrence (mentor): "Focus on B2B first, consumer can wait."
+   -> team-execution | decision | HIGH confidence
+   Reasoning: Direct strategic direction from mentor
+
+2. Sarah (founder): "We're pausing the mobile app."
+   -> solution-design | decision | HIGH confidence
+   Reasoning: Product roadmap change from founder
+
+File both decisions? [all / review individually / skip]
+```
+
+### Filing Options Per Batch
+
+- **all**: File every segment in this batch
+- **review individually**: Present each one for yes/no/redirect
+- **skip**: Skip the entire batch (captures structured rejection)
+
+### Handle Rejections
+
+When the user rejects a filing, offer structured rejection reasons:
+
+> "Why skip? [not relevant] [already known] [wrong section] [other]"
+
+Capture the rejection reason. This becomes graph data per the wicked problem architecture (rejection IS data).
+
+### Cross-Reference Against Open Action Items
+
+During filing, if any open action items remain (not cleared in Step 0), compare each segment being filed against them. If a segment appears to address or complete an open action item:
+
+> "This looks like progress on Lawrence's 'Review TAM analysis'. Mark as done?"
+
+Use Larry's judgment -- not exact text matching. Only surface when confidence is high. If user confirms, update the source meeting's action-items.md.
+
+### Create Filed Artifacts
+
+For each filed segment, create a markdown file in the target room section using the frontmatter from `references/meeting/artifact-template.md`:
+
+**File path pattern:** `room/{section}/YYYY-MM-DD-{slug}.md`
+
+Include ALL provenance fields:
+- methodology: file-meeting
+- created: {today}
+- source: transcript (or velma)
+- attribution:
+  - speaker: {name}
+  - role: {role}
+  - profile_path: team/{role-plural}/{speaker-slug}
+  - meeting_date: {meeting date}
+  - meeting_id: {YYYY-MM-DD-meeting-slug}
+- segment_type: {type}
+- confidence: {confidence score}
+- meeting_date: {meeting date}
+- meeting_name: {meeting identifier}
+- room_section: {target section}
+- assumptions: {extracted assumptions with status and impacts}
+- perspective: {speaker_role}
+- cascade_sections: {sections this may affect beyond target}
+
+When writing the artifact content, auto-insert [[concept-name]] links for key concepts that connect this segment to other parts of the Data Room. Use [[section-name]] for cross-section references (existing pattern) and [[concept-name]] for domain concepts, frameworks, or recurring themes. Examples: [[wicked-problems]], [[assumption-tracking]], [[market-sizing]], [[competitive-moat]]. These wikilinks feed the knowledge graph -- build-graph parses them into concept nodes and REFERENCES edges. Users can also manually add [[wikilinks]] to any room artifact at any time.
+
+**Native wikilink injection (NATIVE-01/02):** Immediately after writing each filed artifact, run:
+```bash
+node scripts/wikilink-file.cjs "$ROOM_DIR" "$ARTIFACT_PATH"
+```
+This uses `lib/vault/wikilink-builder.cjs` to inject team-name wikilinks at write time so the artifact arrives pre-linked. Errors are logged but non-fatal -- filing never aborts because of a wikilink pass.
+
+Speaker contributions are tracked via computed backlinks in PROFILE.md (run by compute-team), not by filing copies to speaker subfolders.
+
+Track: total segments filed, total rejected, sections touched.
+
+---
+
+## Step 5: Create Meeting Summary + Archive
+
+### Infer Meeting Name + Confirm
+
+Before creating the archive, confirm the meeting name with the user:
+
+1. **Larry proposes** a meeting name from the dominant topic/purpose of classified segments:
+   > "This looks like a mentoring session focused on market validation. I'd call it 'Market Validation Mentoring'. Sound right?"
+
+2. **User confirms or changes** the name. Use their version if they provide one.
+
+3. The confirmed meeting name becomes the **meeting_id** used in all attribution blocks and archive paths:
+   - meeting_id: `YYYY-MM-DD-{confirmed-slug}` (e.g., `2026-03-15-market-validation-mentoring`)
+   - Slugify: lowercase, hyphens, no special characters, max 50 characters
+
+### Meeting Archive Package
+
+The complete meeting archive directory structure:
+
+```
+room/meetings/YYYY-MM-DD-{meeting-name}/
+  transcript.md
+  summary.md
+  speakers.md
+  decisions.md
+  action-items.md
+  metadata.yaml
+  {audio-filename}       # only if --audio input
+  filed-to/
+```
+
+Each meeting is a self-contained knowledge artifact. The entire folder can be browsed, shared, or referenced as a unit.
+
+### Create Meeting Archive Directory
+
+```bash
+mkdir -p room/meetings/YYYY-MM-DD-{meeting-name}/filed-to/
+```
+
+### Store Processed Transcript
+
+Write the processed transcript (with speaker labels and format metadata) to:
+`room/meetings/YYYY-MM-DD-{meeting-name}/transcript.md`
+
+### Create Speakers Roster
+
+Create `room/meetings/YYYY-MM-DD-{meeting-name}/speakers.md`:
+
+```markdown
+---
+meeting_id: {YYYY-MM-DD-meeting-slug}
+meeting_date: {YYYY-MM-DD}
+---
+# Speakers: {meeting_name}
+
+| Speaker | Role | Segments | Profile |
+|---------|------|----------|---------|
+| {name} | {role} | {count} | [[team/{role-plural}/{slug}/PROFILE.md]] |
+```
+
+One row per confirmed speaker from Step 2. Profile links use the slug from create-speaker-profile (canonical slug source).
+
+### Create Full Summary
+
+Following `references/meeting/summary-template.md`, create the full meeting summary at:
+`room/meetings/YYYY-MM-DD-{meeting-name}/summary.md`
+
+Structure:
+
+1. **Narrative lead paragraph** in Larry's voice:
+   > "Lawrence pushed hard on market validation today. Three things you can't ignore..."
+
+2. **## Key Decisions** -- with who decided and the reasoning
+
+3. **## Insights Filed** -- {count} insights filed to {sections list}
+
+4. **## Contradictions Detected** -- if any contradictions found between this meeting's content and existing room content. Skip section entirely if none.
+
+5. **## Gaps Identified** -- room sections that SHOULD have received input from this meeting but didn't. Based on the speaker roles present and what they discussed.
+
+6. **## Action Items** -- with owners assigned from speaker context. Deadlines ONLY when explicitly mentioned in transcript. Never invent deadlines.
+
+7. **## Rejections** -- segments rejected with structured reasons. This IS data -- do not hide or minimize rejections.
+
+8. **## Speakers** -- {count} speakers with roles and contribution summary
+
+9. **## Convergence Signals** -- topics appearing in 3+ meetings across the meeting history. Only include if convergence was detected. Skip section entirely if none.
+
+10. **## Cross-Meeting Contradictions** -- contradictions detected against prior meetings (beyond within-meeting contradictions in section 4). Only include if cross-meeting contradictions were found.
+
+### Create Decisions Log
+
+Create `room/meetings/YYYY-MM-DD-{meeting-name}/decisions.md`:
+
+```markdown
+---
+meeting_id: {YYYY-MM-DD-meeting-slug}
+---
+# Decisions: {meeting_name}
+
+1. **{Decision summary}** -- {speaker} ({role})
+   Filed to: [[{section}/{artifact-filename}.md]]
+   Impact: {cascade_sections from the decision artifact}
+```
+
+Extract from the segments classified as `decision` in Step 3. If no decisions were made, write: "No explicit decisions were recorded in this meeting."
+
+### Create Action Items Log
+
+Create `room/meetings/YYYY-MM-DD-{meeting-name}/action-items.md`:
+
+```markdown
+---
+meeting_id: {YYYY-MM-DD-meeting-slug}
+---
+# Action Items: {meeting_name}
+
+| Owner | Task | Deadline | Status |
+|-------|------|----------|--------|
+| {name} | {task} | {date or "not specified"} | open |
+```
+
+Extract from segments classified as `action-item` in Step 3. Deadlines ONLY if explicitly stated in transcript -- never invent deadlines. All items start as `status: open`. If no action items, write: "No action items were identified in this meeting."
+
+### Create Structured Metadata
+
+Create `room/meetings/YYYY-MM-DD-{meeting-name}/metadata.yaml` as the LAST file in the archive (after all other data is known):
+
+```yaml
+meeting_id: {YYYY-MM-DD-meeting-slug}
+meeting_name: {human-readable meeting name}
+meeting_date: {YYYY-MM-DD}
+source: {transcript | velma}
+speakers:
+  - name: {full name}
+    role: {role}
+    slug: {speaker-slug matching profile directory}
+  - name: {full name}
+    role: {role}
+    slug: {speaker-slug}
+topics:
+  - {dominant topic 1}
+  - {dominant topic 2}
+decisions_count: {N}
+insights_count: {N}
+action_items_count: {N}
+sections_touched:
+  - {section-name}
+  - {section-name}
+has_audio: {true | false}
+```
+
+Topics are inferred from the dominant themes of filed segments. Speaker slugs MUST match the directory names created by create-speaker-profile (canonical slug source).
+
+### Copy Audio File (if --audio)
+
+If input was `--audio <path>`, copy the audio file into the meeting archive:
+
+```bash
+cp {audio-path} room/meetings/{YYYY-MM-DD-meeting-slug}/{original-filename}
+```
+
+Set `has_audio: true` in metadata.yaml. If no audio input, set `has_audio: false`.
+
+Register the audio file in the room's ASSET_MANIFEST.md for dashboard/wiki discovery:
+
+```bash
+# Register audio in ASSET_MANIFEST.md
+bash scripts/file-asset "$room_path" "$audio_path" "meetings" --meeting "$meeting_id"
+```
+
+This creates a markdown wrapper alongside the audio file in the meeting archive with a link to the transcript:
+```yaml
+---
+type: audio
+asset_path: meetings/{meeting_id}/{audio_filename}
+meeting_id: {meeting_id}
+transcript: meetings/{meeting_id}/transcript.md
+---
+```
+
+The wrapper content includes: `Transcript: [[meetings/{meeting_id}/transcript.md]]`
+
+### Create Filed-To Reference Directory
+
+In `room/meetings/YYYY-MM-DD-{meeting-name}/filed-to/`, create a small markdown file for each filed artifact pointing to its location:
+
+```markdown
+# {artifact-slug}
+Filed to: room/{section}/YYYY-MM-DD-{slug}.md
+Speaker: {name} ({role})
+Type: {segment_type}
+```
+
+**Native wikilink injection (NATIVE-01/02):** After writing each filed-to stub AND the meeting summary.md, run the wikilink wrapper to inject team links and filed-to footer lines at write time:
+```bash
+# For each filed-to stub
+node scripts/wikilink-file.cjs "$ROOM_DIR" "$STUB_PATH" \
+  --filed-to-target="{section}/YYYY-MM-DD-{slug}.md" \
+  --meeting-slug="YYYY-MM-DD-{meeting-name}"
+
+# For the meeting summary
+node scripts/wikilink-file.cjs "$ROOM_DIR" "$SUMMARY_PATH" \
+  --meeting-slug="YYYY-MM-DD-{meeting-name}"
+```
+See `lib/vault/wikilink-builder.cjs` for the canonical builders. The wrapper fails soft -- if the room has zero team profiles or scan errors, filing still completes cleanly.
+
+### Create Compact Root Reference
+
+Create a compact one-paragraph reference at the room root:
+`room/meeting-YYYY-MM-DD-{meeting-name}.md`
+
+```markdown
+---
+type: meeting-reference
+meeting_date: YYYY-MM-DD
+meeting_name: {name}
+speakers: {count}
+artifacts_filed: {count}
+sections_touched: [{sections}]
+---
+
+{One paragraph summary of the meeting and its impact on the Data Room.}
+
+Full summary: [[meetings/YYYY-MM-DD-{meeting-name}/summary.md]]
+Transcript: [[meetings/YYYY-MM-DD-{meeting-name}/transcript.md]]
+Filed {N} artifacts across {M} sections.
+```
+
+### Past Meeting Lookup
+
+When Larry needs to reference past meetings (e.g., "Lawrence mentioned this 3 meetings ago"), grep metadata.yaml files across `room/meetings/`:
+
+- **By speaker:** `grep -rl '{speaker-slug}' room/meetings/*/metadata.yaml`
+- **By topic:** `grep -rl '{topic}' room/meetings/*/metadata.yaml`
+- **By date range:** Scan `meeting_date` fields in metadata.yaml files
+- **By decision count:** `grep -l 'decisions_count: [1-9]' room/meetings/*/metadata.yaml`
+
+This provides fast targeted lookups without indexing. metadata.yaml is designed as a grep-friendly structured search surface.
+
+---
+
+## Step 6: Cross-Relationship Batch Scan
+
+After ALL filing is complete, scan filed artifacts against existing Data Room content.
+
+### Load Detection Heuristics
+
+Use `references/meeting/cross-relationship-patterns.md` (already loaded in Setup if available) for the 5 edge types:
+
+- **INFORMS**: new artifact references or provides evidence for another section
+- **CONTRADICTS**: new artifact conflicts with existing claim
+- **CONVERGES**: theme from this meeting appears in 3+ sections
+- **INVALIDATES**: new artifact makes an existing assumption stale
+- **ENABLES**: new artifact unblocks something in another section
+
+### Scan Protocol
+
+1. For each filed artifact, read its content and assumptions
+2. Glob existing room content in related sections (especially cascade_sections)
+3. Apply Tier 0 keyword matching heuristics from cross-relationship-patterns.md
+4. Detect significant cross-relationships only -- not every minor keyword overlap
+
+**Tier 0 implementation:** Larry's conversational reasoning against room content. No LSA/MiniLM in Phase 6 -- computational similarity comes in Phase 8.
+
+### Present Findings
+
+**If significant cross-relationships found:**
+
+Present in priority order (INVALIDATES > CONTRADICTS > CONVERGES > ENABLES > INFORMS):
+
+> "This meeting changed something in your Data Room:"
+>
+> **CONTRADICTS:** Tyler's market size estimate ($50M) conflicts with the $190M TAM in your financial-model/revenue-projection.md. Which is current?
+>
+> **CONVERGES:** Enterprise focus was mentioned by 3 speakers and now appears in problem-definition, market-analysis, and solution-design. This is becoming a clear strategic direction.
+>
+> **INFORMS:** Sarah's competitive analysis point adds evidence to your competitive-analysis section.
+
+**If no significant cross-relationships found:**
+
+> "No significant cross-relationships detected from this meeting's content against your existing Data Room. As your room grows, cross-meeting intelligence will get richer."
+
+### Cross-Meeting Intelligence Scan
+
+After the within-meeting cross-relationship scan, perform cross-meeting pattern detection using the protocols from `references/meeting/cross-meeting-intelligence.md`:
+
+#### Convergence Detection
+1. Extract key topics from the current meeting's metadata (topics inferred from filed segments)
+2. Grep `topics:` across all `room/meetings/*/metadata.yaml` files
+3. Any topic in 3+ meetings (including this one) = convergence signal
+4. Surface each: "Market validation has been raised in 4 of your last 6 meetings. This is becoming a central theme."
+
+#### Contradiction Detection
+1. Pre-filter prior meetings that share topics/speakers with current meeting (via metadata.yaml grep)
+2. Load summaries from up to 10 matching prior meetings
+3. Use Larry's reasoning to detect position changes or disagreements across meetings
+4. HIGH-impact contradictions (financials, strategy, key decisions): surface immediately with specific references
+5. LOW-impact contradictions (opinions, preferences): note in meeting summary
+
+#### Record Findings
+- Add convergence signals and cross-meeting contradictions to the meeting summary (new sections in Step 5)
+- Present the combined cross-relationship + cross-meeting findings to the user in priority order
+
+---
+
+## Post-Pipeline: Proactive Speaker Research
+
+After the entire 6-step pipeline is complete, check if any new speaker profiles were created in Step 2.
+
+**If `new_profiles` is empty:** Skip this section.
+
+**If `new_profiles` has entries:**
+
+> "I created profiles for {names}. Let me research them online to fill in context..."
+
+For each new speaker profile:
+
+1. Extract venture context from `room/STATE.md` (venture name, domain, stage) or use confirmed meeting context
+2. Run: `bash scripts/research-speaker <room_dir> <speaker-slug> <display-name> "<project-context>"`
+3. Present the research findings to the user:
+   > "Here's what I found about {name}. Want me to update their profile?"
+4. **User confirms** before any research content is written to PROFILE.md
+5. If confirmed, run: `bash scripts/research-speaker <room_dir> <speaker-slug> <display-name> "<project-context>" --apply`
+6. If declined: Leave profile with `research_status: pending` -- user can research later
+
+**Important:** Research runs AFTER the filing pipeline. Never block filing on external API calls. This follows Pitfall 7 from research: proactive research is valuable but must not interrupt the core workflow.
+
+---
+
+## Closing
+
+After all steps complete (including optional research):
+
+> "Meeting filed. {N} artifacts across {M} sections. {P} speakers identified. {R} new profiles created. Anything else from this conversation?"
+
+If cross-relationships were found, add:
+> "I flagged {X} cross-relationships worth reviewing."
+
+If cross-meeting intelligence was detected, add:
+> "{Y} convergence signals and {Z} cross-meeting contradictions detected."
+
+---
+
+## Voice Rules
+
+- Larry's conversational voice throughout. Short sentences. Direct.
+- Frame gaps as opportunities: "Your competitive-analysis is light -- this meeting could change that."
+- Show reasoning for every classification. Transparency builds trust.
+- Never file silently. Always confirm-then-file.
+- Rejection reasons are valuable -- treat them with respect, not as failures.
+- Challenge gently when a user skips something important: "That decision from Lawrence seems significant. Sure you want to skip it?"