@mindrian_os/cli 1.13.0-beta.10 → 1.13.0-beta.44

package/references/meeting/cross-meeting-intelligence.md

@@ -1,216 +0,0 @@
----
-title: Cross-Meeting Intelligence Detection
-description: Protocols for convergence detection, contradiction tracking, and action item lifecycle across meetings
-tier: 0
-used_by:
-  - commands/file-meeting.md (Step 0, Step 4, Step 6)
----
-
-# Cross-Meeting Intelligence Detection
-
-Protocols for detecting patterns ACROSS the full meeting history. While `cross-relationship-patterns.md` handles within-meeting cross-subsystem scans, this reference handles cross-MEETING intelligence: convergence signals, contradiction tracking, and action item lifecycle.
-
----
-
-## 1. Action Item Triage Protocol (Step 0)
-
-Before starting the filing pipeline, Larry checks for unfinished business from prior meetings.
-
-### Load Open Items
-
-Read `room/action-items.md` if it exists. This aggregated file is produced by `compute-meetings-intelligence` and contains all open/done action items across meetings.
-
-**If the file does not exist or has zero open items:** Skip Step 0 entirely. Proceed to Step 1 silently -- do not mention action items.
-
-### 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]
-
-Keep it lightweight. The user is here to file a new meeting, not review old business. Quick in, quick out.
-
-### 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 (e.g., `room/meetings/2026-03-15-mentoring/action-items.md`). Find the source meeting by the `Source Meeting` column in the aggregated table. Do NOT edit the aggregated `room/action-items.md` directly -- it gets rebuilt by `compute-state`.
-- **skip**: Move on to Step 1. No changes made.
-- **review all**: Show each item individually for yes/no confirmation.
-
-Track items marked done for inclusion in this meeting's summary: "Cleared 2 action items from prior meetings."
-
-### Lifecycle Rule
-
-Action items follow a simple open/done lifecycle. No intermediate states. No auto-expiry. The user decides when something is done.
-
----
-
-## 2. Cross-Reference During Filing Protocol (Step 4 Enhancement)
-
-During segment filing (Step 4), if open action items remain (not all cleared in Step 0), compare each segment being filed against them.
-
-### Detection Method
-
-Use Larry's judgment -- not exact text matching. An action item about "Review TAM analysis" could be addressed by a segment discussing "Updated market size projections." Look for semantic overlap between the segment content and the action item task description.
-
-### Confidence Threshold
-
-Only surface when Larry is at least 70% confident that a segment addresses an open action item. False positives here interrupt the filing flow and erode trust.
-
-### Surfacing
-
-When a match is found:
-
-> "This looks like progress on Lawrence's 'Review TAM analysis'. Mark as done?"
-
-If user confirms: update the source meeting's `action-items.md` (same as Step 0 handling). If user declines: continue filing without changes.
-
-### Rate Limiting
-
-Surface at most 3 action item matches per filing session. If more are found, batch the remaining ones and present them at the end of Step 4: "I also noticed possible progress on 2 more items. Quick review?"
-
----
-
-## 3. Cross-Meeting Convergence Detection Protocol (Step 6 Enhancement)
-
-After the within-meeting cross-relationship scan (existing Step 6 behavior), perform a cross-meeting scan for convergence signals.
-
-### Scan Protocol
-
-1. **Extract key topics** from the current meeting's filed segments. These become the search terms.
-2. **Grep `topics:` fields** in ALL `room/meetings/*/metadata.yaml` files. This is a pre-filter -- fast and cheap.
-3. **Count topic frequency** across meetings. For each topic appearing in 3+ meetings (including the current one), generate a convergence signal.
-4. **Surface each signal** in Larry's voice:
-
-> "Market validation has been raised in 4 of your last 6 meetings. This is becoming a central theme."
-
-> "Regulatory risk keeps coming up -- 3 meetings in a row now. Might be worth a dedicated session."
-
-### Convergence Signal Format
-
-Each convergence signal includes:
-- The topic/theme that is converging
-- How many meetings it appears in (and which ones)
-- A brief interpretation of what the convergence means
-
-### Recording
-
-Convergence signals are written to:
-1. The current meeting's `summary.md` in the new `## Convergence Signals` section
-2. Tracked in room-level state for compute-state to aggregate
-
----
-
-## 4. Cross-Meeting Contradiction Detection Protocol (Step 6 Enhancement)
-
-After convergence detection, scan for contradictions across the meeting history.
-
-### Pre-Filter Step
-
-Load metadata.yaml from recent meetings and identify those that share topics OR speakers with the current meeting. This avoids loading irrelevant meeting summaries.
-
-### Scan Window
-
-Load summaries from up to 10 matching prior meetings. If fewer than 10 share topics/speakers, load all matching ones. Never load more than 10 -- context window management per research pitfall #1.
-
-### Detection Method
-
-Use Larry's LLM reasoning to compare current meeting claims against prior meeting claims. Look for:
-- **Position changes**: Same speaker said X before, now says Y
-- **Speaker disagreements**: Speaker A said X in a prior meeting, Speaker B says not-X now
-- **Numerical conflicts**: Different figures for the same metric across meetings
-- **Strategy reversals**: Direction decided in one meeting contradicted in another
-
-### Severity-Based Flagging
-
-**HIGH-impact** (financials, strategy, key decisions):
-Flag immediately during filing with specific references:
-
-> "Lawrence said TAM was $190M in the March 15 meeting, but now says $120M. Which is current?"
-
-The user resolves high-impact contradictions on the spot. Record the resolution.
-
-**LOW-impact** (opinions, preferences, minor details):
-Collect and include in the meeting summary's `## Cross-Meeting Contradictions` section only. Do not interrupt filing for low-impact contradictions.
-
-### Resolution Tracking
-
-When a high-impact contradiction is surfaced and the user resolves it (confirms which claim is current):
-- Note the resolution in the current meeting's summary
-- The resolved claim becomes the authoritative version
-- The prior claim is marked as superseded (noted in the contradiction record)
-
----
-
-## 5. Enhanced Meeting Summary Sections
-
-The meeting summary (`summary.md`) gains two new sections, added AFTER the existing sections (Key Decisions, Insights Filed, Contradictions Detected, Gaps, Action Items, Rejections, Speakers):
-
-### Convergence Signals Section
-
-```markdown
-## Convergence Signals
-
-{Topics appearing in 3+ meetings across the meeting history. Only include this
-section if convergence was detected. Skip entirely if none.}
-
-- **{topic}**: Appeared in {count} meetings ({meeting-id-1}, {meeting-id-2}, {meeting-id-3})
-  Interpretation: {what this convergence suggests}
-```
-
-### Cross-Meeting Contradictions Section
-
-```markdown
-## Cross-Meeting Contradictions
-
-{Contradictions detected against prior meetings. Beyond the within-meeting
-contradictions in the "Contradictions Detected" section above. Only include
-this section if cross-meeting contradictions were found. Skip entirely if none.}
-
-- **{Claim in current meeting}** vs **{Claim in prior meeting}**
-  Prior meeting: {meeting-id}
-  Speaker(s): {current speaker} vs {prior speaker}
-  Severity: {HIGH | LOW}
-  Resolution: {user's resolution, if provided, or "Unresolved"}
-```
-
----
-
-## 6. Context Window Management
-
-Cross-meeting scanning can consume significant context. Follow these rules:
-
-### Meeting Limit
-
-Scan at most 10 prior meetings. For rooms with extensive meeting history, use the 10 most recent.
-
-### Pre-Filter Before Loading
-
-Use metadata.yaml grep to PRE-FILTER relevant meetings by topic and speaker BEFORE loading full summaries. Only load `summary.md` for meetings that share at least one topic or speaker with the current meeting.
-
-### Efficient Scanning Pattern
-
-1. Grep all `metadata.yaml` files for topic matches (fast, small files)
-2. From matches, identify the most relevant 10 meetings
-3. Load only those summaries for detailed comparison
-4. Never load all meeting transcripts -- summaries contain sufficient signal
-
-### Graceful Degradation
-
-If the room has fewer than 3 prior meetings, skip convergence detection (threshold cannot be met). Contradiction detection still runs against any available prior meetings.
-
----
-
-## Cross-Reference
-
-- Within-meeting cross-relationships: `references/meeting/cross-relationship-patterns.md`
-- Meeting summary template: `references/meeting/summary-template.md`
-- Action item format: per-meeting `action-items.md` in meeting archive
-- Aggregated action items: `room/action-items.md` (produced by `compute-meetings-intelligence`)

package/references/meeting/cross-relationship-patterns.md

@@ -1,202 +0,0 @@
----
-title: Cross-Relationship Detection Patterns
-description: >
-  Defines the 5 edge types (INFORMS, CONTRADICTS, CONVERGES, INVALIDATES, ENABLES)
-  that the file-meeting command's Step 6 batch scan uses to discover cross-subsystem
-  impacts in the Data Room. Tier 0 detection heuristics require no ML -- Larry's
-  reasoning plus keyword matching.
-tier: 0
-used_by:
-  - commands/file-meeting.md (Step 6: batch cross-relationship scan)
-  - scripts/analyze-room (convergence + contradiction detection)
-  - skills/room-passive/SKILL.md (cascade awareness)
----
-
-# Cross-Relationship Detection Patterns
-
-After all meeting segments are filed, Larry performs a **batch cross-relationship scan** to discover how new artifacts connect to existing room content. This reference defines the 5 edge types, their detection heuristics, and when to surface findings.
-
-## Why Cross-Relationships Matter
-
-Ventures are wicked problems (Rittel & Webber 1973). Changes in one subsystem cascade through others (Simon 1962). The Data Room is NOT a flat document store -- it is a nested system where insights in one section may inform, contradict, or invalidate claims in another. The cross-relationship scan finds what humans miss.
-
----
-
-## Edge Types
-
-### INFORMS (Impact: MEDIUM)
-
-**Definition:** A new artifact provides evidence, context, or supporting data for content in another room section. The information flows one direction -- source informs target without conflicting.
-
-**Wicked problem connection:** Addresses characteristic #3 ("Solutions are not true-or-false, but good-or-bad") -- new evidence shifts the quality of existing analysis.
-
-**Tier 0 detection heuristics:**
-- Shared keywords between new artifact content and existing section entries (noun phrases, proper nouns, technical terms)
-- Explicit section references in text: "this affects our financials," "relevant to our market analysis," "connects to the IP question"
-- Speaker mentions another domain by name: "from a legal perspective," "on the competitive side"
-- New artifact contains data (numbers, percentages, dates) relevant to an existing section's claims
-
-**Examples:**
-1. A researcher's insight about material costs INFORMS the financial-model section's cost projections
-2. A mentor's feedback about go-to-market strategy INFORMS the market-analysis section's channel assumptions
-3. An advisor's note about regulatory changes INFORMS the legal-ip section's compliance analysis
-
-**Surface when:** Direct relevance to a section the user has content in. Skip when the connection is trivially obvious (same section) or when the target section is empty (no existing content to inform).
-
-**Output format:** `INFORMS: {source_artifact} -> {target_section}. {brief explanation}. Impact: MEDIUM.`
-
----
-
-### CONTRADICTS (Impact: HIGH)
-
-**Definition:** A new artifact conflicts with an existing claim, assumption, or conclusion in the Data Room. The two pieces of information cannot both be true simultaneously, or they present incompatible perspectives on the same topic.
-
-**Wicked problem connection:** Addresses characteristic #9 ("The planner has no right to be wrong") -- contradictions signal that a previous decision may need revisiting. Also addresses #2 ("No stopping rule") -- contradictions re-open what seemed settled.
-
-**Tier 0 detection heuristics:**
-- Opposite sentiment about the same topic: one artifact says "market is growing" while another says "market is shrinking"
-- Numerical disagreements: different TAM figures, conflicting timelines, mismatched cost estimates
-- Contradiction signals in speech: "actually," "contrary to what we assumed," "I disagree," "that's not what we're seeing," "the data shows otherwise"
-- Assumption with `status: validated` in frontmatter that new data challenges
-- Speaker role conflict: investor says one thing, researcher data shows another
-
-**Examples:**
-1. Investor says "TAM is $50M" but market-analysis has an entry claiming "TAM is $190M"
-2. New competitive intelligence shows a direct competitor, but competitive-analysis states "no direct competitors"
-3. Mentor advises pivoting to B2C but business-model is built entirely around B2B enterprise sales
-
-**Surface: ALWAYS.** Contradictions are the most valuable signal in wicked problem management. They reveal where the venture's understanding is inconsistent. Never suppress a contradiction.
-
-**Output format:** `CONTRADICTS: {source_artifact} -> {target_section}/{target_artifact}. {what conflicts}. Impact: HIGH.`
-
----
-
-### CONVERGES (Impact: HIGH)
-
-**Definition:** A theme, concept, or concern from the current meeting appears in 3 or more room sections. This cross-cutting pattern signals a topic that is central to the venture and deserves focused attention.
-
-**Wicked problem connection:** Addresses characteristic #7 ("Every wicked problem is essentially unique") -- convergence patterns reveal the unique structure of THIS venture's problem space. Also addresses #5 ("Every solution is a 'one-shot operation'") -- convergent themes are the highest-leverage points for intervention.
-
-**Tier 0 detection heuristics:**
-- Key noun phrases from new artifacts appear in 3+ existing section entries (proper nouns, technical terms, framework names)
-- Proper nouns mentioned across sections: competitor names, technologies, market segments, regulations
-- Themes surfaced by multiple speakers in the meeting that also appear in existing room content
-- A single concept (e.g., "sustainability," "compliance," "scalability") referenced across problem-definition, solution-design, and business-model
-
-**Examples:**
-1. "Sustainability" mentioned by mentor in problem-definition, by researcher in solution-design, and now by investor in business-model -- convergent theme
-2. A specific competitor's name appears in competitive-analysis, market-analysis, solution-design, and now in a meeting discussion -- this competitor is a cross-cutting concern
-3. "Regulatory risk" surfaces in legal-ip, financial-model, market-analysis, and the current meeting -- systemic theme requiring a unified response
-
-**Surface: ALWAYS.** Convergence signals that a theme deserves its own strategic attention. It may warrant a dedicated session or cross-section synthesis.
-
-**Output format:** `CONVERGES: "{theme}" appears in {count} sections ({section_list}). Consider a focused analysis on this cross-cutting theme. Impact: HIGH.`
-
----
-
-### INVALIDATES (Impact: HIGH)
-
-**Definition:** A new artifact makes an existing assumption stale, outdated, or factually incorrect. The assumption's `status` should change from `validated` or `unvalidated` to `invalidated`.
-
-**Wicked problem connection:** Addresses #1 underserved outcome: "Minimize time to detect invalid assumptions" (Opportunity Score: 18). Also addresses characteristic #8 ("Every wicked problem can be considered a symptom of another") -- an invalidated assumption may reveal a deeper problem.
-
-**Tier 0 detection heuristics:**
-- Scan existing artifacts' `assumptions:` frontmatter fields. Compare new information against `claim:` values
-- Temporal conflicts: "That was true in Q1 but..." / "Since we last discussed..." / "The landscape has changed"
-- Numerical/factual conflicts between new data and existing assumption claims
-- Speaker explicitly references a previous assumption: "I know we assumed X, but..."
-- Market or competitive changes that alter the basis of existing claims
-
-**Examples:**
-1. New competitive intelligence invalidates the assumption "No competitors in ionic liquids space" -- a funded startup just launched
-2. Updated market research shows the regulatory environment changed, invalidating the assumption "FDA approval not required for our device class"
-3. A team member reports that the key technical partner withdrew, invalidating the assumption "Partnership with X secures our supply chain"
-
-**Surface: ALWAYS.** Stale assumptions are the #1 underserved outcome in venture intelligence. An invalidated assumption may cascade through multiple sections. Flag immediately and trace the cascade.
-
-**Output format:** `INVALIDATES: {source_artifact} invalidates assumption "{claim}" in {target_section}/{target_artifact}. {why it's stale}. Impact: HIGH.`
-
----
-
-### ENABLES (Impact: MEDIUM)
-
-**Definition:** A new artifact unblocks progress in another section. A decision was made, information was provided, or an action was completed that resolves an open question or dependency in another part of the Data Room.
-
-**Wicked problem connection:** Addresses characteristic #4 ("There is no immediate and no ultimate test of a solution") -- enablement signals that the venture can now test a hypothesis that was previously blocked. Also addresses #6 ("Wicked problems do not have an enumerable set of potential solutions") -- each enablement opens new solution paths.
-
-**Tier 0 detection heuristics:**
-- Action items completed that other sections referenced as blockers
-- Decisions that resolve open questions: "We've decided to go B2B" enables financial-model projections that were waiting on market definition
-- "Now we can..." / "This means we can..." / "This unblocks..." / "The missing piece was..." signals
-- Resource acquisition (funding, hire, partnership) that other sections depend on
-- Regulatory/legal clearance that other sections were waiting for
-
-**Examples:**
-1. Decision to go B2B enables financial-model projections that were blocked by undefined target market
-2. Securing a Letter of Intent from a pilot customer enables the business-model section's revenue projections
-3. Hiring a CTO enables the solution-design section's technical architecture work that was on hold
-
-**Surface when:** The previously blocked section exists and has content waiting. Skip when the target section is empty (nothing to unblock) or when the enablement is trivially local (same section).
-
-**Output format:** `ENABLES: {source_artifact} -> {target_section}. {what is now unblocked}. Impact: MEDIUM.`
-
----
-
-## Batch Scan Protocol
-
-After all meeting segments have been filed (Step 5 of file-meeting completes), Larry performs the batch cross-relationship scan:
-
-1. **Collect filed artifacts:** Gather all artifacts just filed from this meeting session
-2. **Load room context:** For each non-empty room section, read the existing entries (titles, headers, frontmatter including assumptions)
-3. **Compare each new artifact:** Against existing room content using Tier 0 heuristics above
-4. **Identify significant relationships:** Apply the impact and surfacing rules for each edge type
-5. **Present findings:** Show only significant discoveries -- do not overwhelm with trivial INFORMS connections
-6. **Prioritize:** CONTRADICTS and INVALIDATES first (highest user value), then CONVERGES, then ENABLES and INFORMS
-
-**Presentation order:**
-```
-HIGH impact first:
-  1. INVALIDATES (stale assumptions -- most urgent)
-  2. CONTRADICTS (conflicting claims -- action required)
-  3. CONVERGES (cross-cutting themes -- strategic awareness)
-
-MEDIUM impact second:
-  4. ENABLES (unblocked progress -- opportunity)
-  5. INFORMS (supporting evidence -- enrichment)
-```
-
-**User interaction after scan:**
-- For each HIGH finding, ask: "Want to explore this?" (opens the relevant section)
-- For MEDIUM findings, present as a summary list
-- If no significant relationships found: "No cross-subsystem impacts detected from this meeting."
-
----
-
-## Tier Progression
-
-| Tier | Phase | Method | Capability |
-|------|-------|--------|------------|
-| **Tier 0** | Phase 6 | Larry's reasoning + keyword matching | Detects obvious relationships via shared terms, explicit references, and speech signals. No dependencies required. |
-| **Tier 1** | Phase 8 | LSA + MiniLM embeddings | Semantic similarity discovers non-obvious connections. "Cash burn rate" and "runway" recognized as related even without keyword overlap. |
-| **Tier 2** | Phase 9 | Full HSI with Brain graph | Quantitative Hybrid Similarity Index. Pinecone embeddings + Neo4j relationship traversal. Reverse Salient discovery finds hidden cross-meeting connections. |
-
-**Graceful degradation:** Tier 0 always works. Higher tiers enhance accuracy but are never required. A Data Room with only Tier 0 still catches the most impactful relationships.
-
----
-
-## Output Format Reference
-
-Each discovered relationship is presented as a single line:
-
-```
-{EDGE_TYPE}: {source} -> {target}. {explanation}. Impact: {HIGH|MEDIUM}.
-```
-
-**Batch summary example:**
-```
-INVALIDATES: meeting-segment-03.md invalidates assumption "No direct competitors" in competitive-analysis/landscape.md. New entrant Acme Corp launched Q4. Impact: HIGH.
-CONTRADICTS: meeting-segment-01.md -> financial-model/projections.md. Investor estimates $50M TAM vs. existing $190M claim. Impact: HIGH.
-CONVERGES: "regulatory compliance" appears in 4 sections (legal-ip, market-analysis, solution-design, financial-model). Consider a focused regulatory strategy session. Impact: HIGH.
-ENABLES: meeting-segment-05.md -> business-model/revenue.md. B2B decision unblocks pricing model. Impact: MEDIUM.
-INFORMS: meeting-segment-02.md -> solution-design/architecture.md. CTO feedback on tech stack choice. Impact: MEDIUM.
-```

package/references/meeting/live-join-interface.md

@@ -1,244 +0,0 @@
-# Live Join Interface -- External Transcript Source Design Spec
-
-*Design specification for future `--join` and `--latest` flags. NOT implemented in Phase 6.*
-
----
-
-## Status
-
-| Feature | Phase | Status |
-|---------|-------|--------|
-| `file-meeting` (paste/upload) | Phase 6 | Active development |
-| `file-meeting --latest` | Phase 8 | Design only |
-| `file-meeting --join <url>` | Phase 9+ | Design only |
-
-This document defines the interface contract so that future phases can implement external transcript sources without changing the core filing pipeline.
-
----
-
-## Interface Contract
-
-All external transcript sources MUST produce output in one of the supported formats defined in `references/meeting/transcript-patterns.md`. The filing pipeline does not change -- only the input source changes.
-
-```
-External Source -> Transcript (supported format) -> file-meeting pipeline -> Room
-```
-
-### Input Normalization
-
-Any external source adapter must output:
-1. A text file in Zoom, Teams, Otter, Meet, or Raw format, OR
-2. A JSON file in Velma format (with `speaker_id`, `text`, `start_time`, `end_time`, `emotions[]`)
-
-The `file-meeting` command does not know or care where the transcript came from. It only knows formats.
-
----
-
-## `--latest` Flag (Phase 8)
-
-**Purpose:** Pull the most recent meeting transcript from a connected service.
-
-### Usage
-
-```bash
-/mos:file-meeting --latest
-/mos:file-meeting --latest --source read-ai
-/mos:file-meeting --latest --source velma
-```
-
-### Behavior
-
-1. Query the configured transcript source for the most recent meeting
-2. Download the transcript
-3. Convert to a supported format if needed
-4. Pass to the standard `file-meeting` pipeline
-5. Include `source: {service-name}` in artifact frontmatter
-
-### Source Priority (when no `--source` specified)
-
-1. Velma (if configured) -- highest quality (emotions, diarization)
-2. Read AI MCP (if configured) -- broadest meeting platform coverage
-3. Recall.ai (if configured) -- fallback
-
-### Configuration
-
-```json
-// .mcp.json or room config
-{
-  "transcript_sources": {
-    "velma": {
-      "api_url": "ENV:VELMA_API_URL",
-      "api_key": "ENV:VELMA_API_KEY"
-    },
-    "read_ai": {
-      "mcp_server": "read-ai-mcp"
-    },
-    "recall_ai": {
-      "api_key": "ENV:RECALL_API_KEY"
-    }
-  }
-}
-```
-
----
-
-## `--join` Flag (Phase 9+)
-
-**Purpose:** Join a live meeting and transcribe in real-time, filing segments as they occur.
-
-### Usage
-
-```bash
-/mos:file-meeting --join https://zoom.us/j/123456789
-/mos:file-meeting --join https://teams.microsoft.com/l/meetup-join/...
-```
-
-### Behavior
-
-1. Connect to the meeting via an attend-mcp compatible service
-2. Stream transcript segments in real-time
-3. Classify and file segments as they arrive (with user confirmation batched)
-4. Produce the meeting summary when the meeting ends or user disconnects
-
-### Live Filing Modes
-
-| Mode | Description | User Interaction |
-|------|-------------|------------------|
-| silent | Transcribe and classify, file after meeting ends | Post-meeting confirm-then-file |
-| notify | Transcribe and classify, surface high-priority items live | User sees notifications during meeting |
-| interactive | Full confirm-then-file during the meeting | User approves each filing in real-time |
-
-Default: `silent` -- do not interrupt the meeting.
-
----
-
-## External Service Comparison
-
-### attend-mcp (github.com/xpos/attend-mcp)
-
-| Attribute | Value |
-|-----------|-------|
-| Type | MCP server |
-| Cost | Open source (free) |
-| Self-hostable | Yes |
-| Platforms | Zoom, Teams, Google Meet |
-| Diarization | Basic (speaker labels from platform) |
-| Emotions | No |
-| Real-time | Yes (streaming) |
-| Integration | MCP tool calls |
-
-**Best for:** Self-hosted deployments, privacy-conscious users, developers.
-
-### Recall.ai
-
-| Attribute | Value |
-|-----------|-------|
-| Type | API service |
-| Cost | ~$0.50/hour |
-| Self-hostable | No |
-| Platforms | Zoom, Teams, Google Meet, Webex, GoTo |
-| Diarization | Yes (high quality) |
-| Emotions | No |
-| Real-time | Yes (webhooks) |
-| Integration | REST API + webhooks |
-
-**Best for:** Production deployments, broadest platform support, reliable diarization.
-
-### Vexa
-
-| Attribute | Value |
-|-----------|-------|
-| Type | Open source platform |
-| Cost | Free (self-hosted) |
-| Self-hostable | Yes (Apache-2.0) |
-| Platforms | Zoom, Teams, Google Meet |
-| Diarization | Yes |
-| Emotions | Basic sentiment |
-| Real-time | Yes |
-| Integration | REST API |
-
-**Best for:** Self-hosted deployments, budget-conscious teams, open-source preference.
-
-### Modulate Velma (already integrated -- Phase 6, Plan 02)
-
-| Attribute | Value |
-|-----------|-------|
-| Type | API service |
-| Cost | ~$0.03/hour |
-| Self-hostable | No |
-| Platforms | Audio files (not live join) |
-| Diarization | Yes (native, high quality) |
-| Emotions | Yes (20+ categories) |
-| Real-time | No (file upload) |
-| Integration | REST API (scripts/transcribe-velma) |
-
-**Best for:** Audio file transcription, emotion-aware filing, lowest cost per hour.
-
----
-
-## Adapter Interface
-
-Future adapters must implement this contract:
-
-```bash
-# Adapter script interface
-# Input: meeting URL or "latest" command
-# Output: transcript file in supported format, written to stdout or specified path
-# Exit: 0 on success, 1 on failure
-
-scripts/adapters/{source-name} [--latest | --join <url>] [--output <path>]
-```
-
-### Required Adapter Outputs
-
-1. Transcript file (in a supported format)
-2. Meeting metadata (written to stderr as JSON):
-   ```json
-   {
-     "meeting_name": "...",
-     "meeting_date": "YYYY-MM-DD",
-     "duration_minutes": 60,
-     "platform": "zoom",
-     "speakers_detected": 4
-   }
-   ```
-
-### Error Handling
-
-| Error | Adapter Behavior |
-|-------|-----------------|
-| Auth required | Exit 1 with message: "Authentication required. Run: {auth command}" |
-| Meeting not found | Exit 1 with message: "No meeting found at {url}" |
-| Service unavailable | Exit 1 with message: "{service} is unreachable" |
-| Timeout | Exit 1 after 30 seconds with message: "Connection timed out" |
-
----
-
-## Phase Dependencies
-
-```
-Phase 6 (current):
-  - file-meeting accepts paste/upload
-  - Velma transcribes audio files
-  - No external live sources
-
-Phase 8 (--latest):
-  - Read AI MCP integration
-  - Pull most recent transcript
-  - Same pipeline, new input source
-
-Phase 9+ (--join):
-  - attend-mcp or Recall.ai integration
-  - Live meeting attendance
-  - Real-time transcript streaming
-  - Post-meeting or live filing modes
-```
-
----
-
-## Cross-Reference
-
-- Supported transcript formats: `references/meeting/transcript-patterns.md`
-- Velma integration: `scripts/transcribe-velma` (Phase 6, Plan 02)
-- Filing pipeline: `references/meeting/artifact-template.md`
-- Read AI requirements: RDAI-01, RDAI-02, RDAI-03 (Phase 8)