@mindrian_os/install 1.13.0-beta.11

package/references/meeting/section-mapping.md

@@ -0,0 +1,192 @@
+# Section Mapping Matrix -- Speaker Role x Segment Type x Room Section
+
+*Used by `file-meeting` to route classified segments to the correct room section.*
+
+---
+
+## The 12 Speaker Roles
+
+| Role | Description | Typical Context |
+|------|-------------|-----------------|
+| mentor | Teaching advisor, framework guide | Academic, accelerator |
+| researcher | Subject matter researcher, analyst | Research team, consultants |
+| team-member | Core team, employees | Internal meetings |
+| investor | VC, angel, LP, fund manager | Pitch, board, due diligence |
+| advisor | Strategic or technical advisor | Advisory board |
+| customer | Current or potential customer | Discovery, feedback |
+| founder | Company founder, CEO | All meetings |
+| partner | Business partner, channel partner | Partnership discussions |
+| domain-expert | Industry expert, specialist | Expert interviews |
+| government | Regulator, government official | Compliance, grants |
+| competitor | Known competitor representative | Conferences, panels |
+| unknown | Unidentified speaker | Raw paste, unlabeled |
+
+---
+
+## The 8 Room Sections
+
+| Section | Primary Content |
+|---------|----------------|
+| problem-definition | Problem framing, assumptions, scope, unknowns |
+| market-analysis | Market size, trends, timing, customer needs |
+| solution-design | Architecture, features, technical approach |
+| business-model | Revenue, pricing, unit economics, channels |
+| competitive-analysis | Competitors, positioning, differentiation |
+| team-execution | Team, hiring, capabilities, leadership |
+| legal-ip | IP, patents, regulation, compliance |
+| financial-model | Funding, valuation, projections, burn rate |
+
+---
+
+## Routing Matrix
+
+The matrix below maps `(speaker_role, segment_type)` to the primary room section and priority modifier.
+
+**Reading the matrix:** Each cell contains `section (+priority_modifier)`. Empty cells mean "Larry decides based on content" -- the combination is too context-dependent for a fixed rule.
+
+### decision
+
+| Speaker Role | Primary Section | Priority Modifier | Notes |
+|-------------|----------------|-------------------|-------|
+| founder | *content-dependent* | +1 | Founders decide across all sections |
+| investor | financial-model | +2 | Unless explicitly about another section |
+| mentor | problem-definition | +1 | Mentors guide problem framing decisions |
+| advisor | *content-dependent* | +1 | Advisors span multiple domains |
+| team-member | team-execution | 0 | Unless clearly about another section |
+| customer | solution-design | +1 | Customer decisions inform product |
+| researcher | market-analysis | 0 | Research findings drive decisions |
+| partner | business-model | +1 | Partnership decisions affect model |
+| domain-expert | *content-dependent* | +1 | Expert domain determines section |
+| government | legal-ip | +2 | Regulatory decisions are highest priority |
+| competitor | competitive-analysis | 0 | Competitor decisions are intel |
+| unknown | *content-dependent* | -1 | Lower confidence without role context |
+
+### action-item
+
+| Speaker Role | Primary Section | Priority Modifier | Notes |
+|-------------|----------------|-------------------|-------|
+| founder | *content-dependent* | +1 | Founder-assigned actions are high priority |
+| investor | financial-model | +2 | Investor requests are critical |
+| mentor | *content-dependent* | +1 | Mentor-assigned homework |
+| advisor | *content-dependent* | +1 | Advisor follow-ups |
+| team-member | team-execution | 0 | Standard task tracking |
+| customer | solution-design | +1 | Customer-requested features |
+| researcher | market-analysis | 0 | Research tasks |
+| partner | business-model | 0 | Partnership deliverables |
+| domain-expert | *content-dependent* | 0 | Expert recommendations to pursue |
+| government | legal-ip | +1 | Compliance requirements |
+| competitor | competitive-analysis | -1 | Rare -- flagged for review |
+| unknown | *content-dependent* | -1 | Low confidence assignment |
+
+### insight
+
+| Speaker Role | Primary Section | Priority Modifier | Notes |
+|-------------|----------------|-------------------|-------|
+| founder | *content-dependent* | 0 | Founder insights span all sections |
+| investor | financial-model | +1 | Investor insights signal deal criteria |
+| mentor | problem-definition | +1 | Mentor insights reframe the problem |
+| advisor | *content-dependent* | +1 | Advisor insights from experience |
+| team-member | *content-dependent* | 0 | Context-dependent |
+| customer | market-analysis | +2 | Customer insights are primary market data |
+| researcher | market-analysis | +1 | Research findings |
+| partner | business-model | +1 | Partnership ecosystem data |
+| domain-expert | *content-dependent* | +1 | Expert knowledge is high value |
+| government | legal-ip | +1 | Regulatory landscape intelligence |
+| competitor | competitive-analysis | +2 | Competitor admissions are gold |
+| unknown | *content-dependent* | -1 | Needs attribution for proper routing |
+
+### advice
+
+| Speaker Role | Primary Section | Priority Modifier | Notes |
+|-------------|----------------|-------------------|-------|
+| founder | team-execution | 0 | Founder advice usually about execution |
+| investor | financial-model | +2 | Investor advice signals expectations |
+| mentor | problem-definition | +1 | Mentor guidance on framing |
+| advisor | *content-dependent* | +2 | Advisors' PRIMARY output is advice |
+| team-member | *content-dependent* | 0 | Peer suggestions |
+| customer | solution-design | +1 | Customer suggestions = feature requests |
+| researcher | *content-dependent* | 0 | Research recommendations |
+| partner | business-model | +1 | Partnership strategy guidance |
+| domain-expert | *content-dependent* | +2 | Expert recommendations are high value |
+| government | legal-ip | +1 | Compliance guidance |
+| competitor | competitive-analysis | -2 | Competitor "advice" is suspect -- flag |
+| unknown | *content-dependent* | -1 | Unattributed advice has less weight |
+
+### question
+
+| Speaker Role | Primary Section | Priority Modifier | Notes |
+|-------------|----------------|-------------------|-------|
+| founder | *content-dependent* | 0 | Founder questions reveal their blind spots |
+| investor | financial-model | +2 | Investor questions signal due diligence gaps |
+| mentor | problem-definition | +1 | Mentor questions are diagnostic |
+| advisor | *content-dependent* | +1 | Advisor questions reveal risks |
+| team-member | *content-dependent* | 0 | Operational questions |
+| customer | market-analysis | +2 | Customer questions reveal unmet needs |
+| researcher | *content-dependent* | 0 | Research questions |
+| partner | business-model | +1 | Partnership feasibility concerns |
+| domain-expert | *content-dependent* | +1 | Expert questions expose technical gaps |
+| government | legal-ip | +2 | Regulatory questions are compliance flags |
+| competitor | competitive-analysis | +1 | Competitor questions reveal their strategy |
+| unknown | *content-dependent* | -1 | Low priority without role context |
+
+### noise
+
+Noise segments are SKIPPED unless flagged by the Flag Potential Noise Rule (see `segment-classification.md`). No routing matrix needed. Flagged noise goes to user review.
+
+---
+
+## Content-Dependent Routing
+
+When the matrix shows `*content-dependent*`, Larry uses keyword analysis to determine the section:
+
+1. Run the segment text through `scripts/classify-insight` keyword patterns
+2. If `classify-insight` returns `SUGGEST:{section}:MEDIUM`, use that section
+3. If `UNCERTAIN`, analyze context:
+   - What section was the conversation discussing before this segment?
+   - What keywords appear in the segment? (see keyword lists below)
+   - What is the speaker's domain of expertise?
+4. If still uncertain, ask the user: "Where should I file this {type} from {speaker}?"
+
+**Section keyword hints:**
+
+| Section | Keywords |
+|---------|----------|
+| problem-definition | problem, challenge, issue, scope, definition, assumption, unknown, question, gap, need |
+| market-analysis | market, customer, trend, TAM, SAM, growth, segment, user, demand, adoption, timing |
+| solution-design | product, feature, architecture, design, technology, platform, integration, UX, build |
+| business-model | revenue, pricing, model, channel, cost, unit economics, margin, subscription, sales |
+| competitive-analysis | competitor, alternative, moat, differentiation, advantage, threat, positioning, benchmark |
+| team-execution | team, hire, role, culture, leadership, process, execution, sprint, velocity, roadmap |
+| legal-ip | legal, patent, IP, regulation, compliance, license, terms, privacy, GDPR |
+| financial-model | funding, valuation, runway, burn, projection, revenue, cap table, dilution, round |
+
+---
+
+## Priority Scoring
+
+Final filing priority = base_segment_priority + role_modifier + content_relevance
+
+| Base Priority | Score |
+|---------------|-------|
+| decision | 10 |
+| action-item | 8 |
+| insight | 6 |
+| advice | 6 |
+| question | 4 |
+| noise | 0 |
+
+**Role modifier:** From the routing matrix above (-2 to +2).
+
+**Content relevance:** +1 if the segment directly references the target section's domain. +0 otherwise.
+
+**Filing order:** Segments are filed highest-priority first. This ensures decisions and actions are captured before the user fatigues during the confirm-then-file loop.
+
+---
+
+## Cross-Reference Vocabulary
+
+The section names and classification vocabulary in this file are shared with:
+- `scripts/classify-insight` -- uses the same 8 section names and keyword patterns
+- `references/meeting/segment-classification.md` -- defines the 6 segment types referenced here
+- `references/meeting/artifact-template.md` -- `room_section` and `segment_type` fields use these exact values
+- `skills/room-passive/SKILL.md` -- provenance metadata uses the same section vocabulary

package/references/meeting/segment-classification.md

@@ -0,0 +1,258 @@
+# Segment Classification Taxonomy -- Meeting Intelligence
+
+*Used by `file-meeting` to classify each speaker turn into a segment type for filing.*
+
+---
+
+## The 6 Segment Types (Priority Order)
+
+| Priority | Type | Description | Filing Action |
+|----------|------|-------------|---------------|
+| HIGHEST | decision | Explicit choices made, direction set | File to target section, flag cascades |
+| HIGH | action-item | Tasks assigned, deadlines mentioned | File to target section + action tracking |
+| MEDIUM | insight | New information, discoveries, data points | File to target section |
+| MEDIUM | advice | Recommendations, suggestions, should/could | File to speaker's advice folder + section |
+| LOW | question | Open questions, uncertainties raised | File as gap/question in target section |
+| SKIP | noise | Greetings, small talk, logistics, off-topic | Skip (unless flagged -- see Flag Rule below) |
+
+---
+
+## Type Definitions and Heuristics
+
+### 1. decision (HIGHEST)
+
+**Definition:** A speaker explicitly commits to a course of action, selects between options, or sets direction for the venture.
+
+**Signal phrases:**
+- "We've decided to..."
+- "Let's go with..."
+- "The plan is to..."
+- "We're going to..."
+- "I'm committing to..."
+- "That's final"
+- "We'll move forward with..."
+- Negation decisions: "We're NOT doing X" / "We're killing that feature"
+
+**Role-aware heuristics:**
+| Speaker Role | Priority Modifier | Rationale |
+|-------------|-------------------|-----------|
+| founder | +1 | Founders make binding decisions |
+| investor | +1 (conditional) | Only if decision involves funding/terms |
+| mentor | 0 | Mentors advise, rarely decide |
+| team-member | 0 | Context-dependent -- may decide within scope |
+
+**Confidence indicators:**
+- HIGH: Definitive language ("we will", "decided", "final")
+- MEDIUM: Conditional ("if X then we'll do Y", "probably going with")
+- LOW: Hypothetical ("we might want to", "it could make sense to")
+
+**Classification rule:** If a statement both makes a decision AND assigns an action, classify as `decision` (higher priority). The action item is captured as a sub-element.
+
+---
+
+### 2. action-item (HIGH)
+
+**Definition:** A task is explicitly assigned to someone, or a deadline is mentioned for deliverable work.
+
+**Signal phrases:**
+- "{Name} will..."
+- "Can you {task} by {date}?"
+- "Action item: ..."
+- "Let's have {deliverable} ready by..."
+- "I'll send that over"
+- "Follow up on..."
+- "TODO: ..."
+- "Next step: ..."
+
+**Extracted fields:**
+- `owner`: Who is responsible (name or role)
+- `task`: What needs to be done
+- `deadline`: When (if mentioned -- NEVER invent a deadline)
+- `context`: Why this action matters
+
+**Role-aware heuristics:**
+| Speaker Role | Priority Modifier | Rationale |
+|-------------|-------------------|-----------|
+| founder | 0 | Normal -- founders assign work |
+| mentor | +1 | Mentor-assigned actions carry weight |
+| investor | +1 | Investor requests are high-priority |
+| team-member | 0 | Normal task assignment |
+
+**Confidence indicators:**
+- HIGH: Named owner + specific task ("Sarah will prepare the deck")
+- MEDIUM: Implicit owner ("someone should look into that")
+- LOW: Vague future ("we need to think about this at some point")
+
+---
+
+### 3. insight (MEDIUM)
+
+**Definition:** New information, a discovery, a data point, or an observation that adds to the venture's knowledge base.
+
+**Signal phrases:**
+- "I found out that..."
+- "The data shows..."
+- "Interesting -- I didn't know that..."
+- "According to {source}..."
+- "The market is {specific observation}"
+- Numbers, statistics, percentages
+- Comparisons: "X is bigger/smaller/faster than Y"
+- "What we learned is..."
+
+**Role-aware heuristics:**
+| Speaker Role | Priority Modifier | Rationale |
+|-------------|-------------------|-----------|
+| researcher | +1 | Researchers produce high-quality insights |
+| domain-expert | +1 | Domain expertise makes insights more valuable |
+| customer | +1 | Customer insights are primary market data |
+| investor | 0 | Investor observations are insight or advice depending on framing |
+
+**Confidence indicators:**
+- HIGH: Specific data ("revenue grew 23% last quarter")
+- MEDIUM: Observation with reasoning ("the enterprise segment seems stronger because...")
+- LOW: Impression without evidence ("I feel like the market is shifting")
+
+**Assumption extraction:** Every insight implies an assumption. Extract it:
+- Insight: "The TAM is $190M" -> Assumption: `claim: "TAM is $190M", status: unvalidated`
+- Insight: "Enterprise customers have 18-month sales cycles" -> Assumption: `claim: "Enterprise sales cycles are 18 months", status: unvalidated`
+
+---
+
+### 4. advice (MEDIUM)
+
+**Definition:** A recommendation, suggestion, or guidance offered by a speaker. Framed as "you should" rather than "we will."
+
+**Signal phrases:**
+- "You should..."
+- "I'd recommend..."
+- "Have you considered..."
+- "My suggestion would be..."
+- "In my experience..."
+- "What worked for us was..."
+- "I'd be careful about..."
+- "Watch out for..."
+- "One thing to think about..."
+
+**Role-aware heuristics:**
+| Speaker Role | Priority Modifier | Rationale |
+|-------------|-------------------|-----------|
+| mentor | +1 | Mentors' primary output is advice |
+| advisor | +1 | Advisors' primary output is advice |
+| investor | +1 | Investor advice often signals deal criteria |
+| domain-expert | +1 | Domain expertise makes advice actionable |
+| competitor | -1 | Competitor "advice" is suspect |
+
+**Dual filing:** Advice is filed to BOTH:
+1. The relevant room section (based on content)
+2. The speaker's `advice/` subfolder in their profile
+
+**Confidence indicators:**
+- HIGH: Specific actionable recommendation ("hire a VP Sales before Series A")
+- MEDIUM: General direction ("you should think about enterprise")
+- LOW: Vague encouragement ("keep doing what you're doing")
+
+---
+
+### 5. question (LOW)
+
+**Definition:** An open question or uncertainty raised during the meeting. Represents a gap in knowledge.
+
+**Signal phrases:**
+- "What about...?"
+- "How do we...?"
+- "Do we know...?"
+- "Has anyone looked into...?"
+- "I'm not sure about..."
+- "What if...?"
+- "Why is...?"
+
+**Role-aware heuristics:**
+| Speaker Role | Priority Modifier | Rationale |
+|-------------|-------------------|-----------|
+| investor | +2 | Investor questions often signal deal-breaking concerns |
+| mentor | +1 | Mentor questions reveal blind spots |
+| customer | +1 | Customer questions reveal product gaps |
+| team-member | 0 | Normal operational questions |
+
+**Important:** Investor questions about financials, market size, or competition are ALWAYS priority-boosted. An investor asking "What's your churn rate?" is not a LOW-priority question -- it signals a critical data gap.
+
+**Filing:** Questions become gap entries in the relevant section. They represent "what we don't know yet."
+
+**Confidence indicators:**
+- HIGH: Direct question with clear topic ("What's our customer acquisition cost?")
+- MEDIUM: Rhetorical or exploratory ("I wonder if the timing is right...")
+- LOW: Conversational ("Does that make sense?")
+
+---
+
+### 6. noise (SKIP)
+
+**Definition:** Content with no substantive value for the venture's knowledge base. Greetings, logistics, small talk, off-topic tangents.
+
+**Examples:**
+- "Hey everyone, can you hear me?"
+- "Let me share my screen"
+- "Sorry, I was on mute"
+- "Should we take a 5-minute break?"
+- "Nice weather today"
+- "How was your weekend?"
+- Laughter, filler words, repeated phrases
+
+**SKIP rule:** Noise segments are not filed. They are excluded from the meeting summary's segment count.
+
+---
+
+## The Flag Potential Noise Rule
+
+**Critical:** When a segment is classified as `noise` but contains ANY of the following, FLAG it for user review instead of skipping:
+
+1. **Proper nouns** -- company names, person names, product names
+2. **Competitor names** -- any mention of a known or potential competitor
+3. **Numbers** -- revenue figures, percentages, dates, counts
+4. **Technical terms** -- domain-specific language that might indicate hidden insight
+
+**Example:**
+```
+"Oh by the way, I ran into the CEO of Acme Corp at that conference last week."
+```
+This looks like small talk (noise) but contains a competitor name ("Acme Corp") and a potential connection. Flag it.
+
+**Flagged noise format:**
+```
+FLAGGED_NOISE: "{original text}"
+REASON: Contains competitor name "Acme Corp"
+ACTION: User review required -- may contain buried insight
+```
+
+---
+
+## Classification Confidence Scoring
+
+Each classified segment gets a confidence score (0.0 - 1.0):
+
+| Score Range | Label | Meaning |
+|-------------|-------|---------|
+| 0.9 - 1.0 | HIGH | Clear signal phrases, unambiguous type |
+| 0.7 - 0.89 | MEDIUM | Strong indicators but some ambiguity |
+| 0.5 - 0.69 | LOW | Weak signals, multiple possible types |
+| Below 0.5 | UNCERTAIN | Larry should ask user for classification |
+
+**Threshold rule:** Segments with confidence below 0.5 are presented to the user: "I'm not sure how to classify this. Is it an insight, advice, or something else?"
+
+---
+
+## Multi-Type Segments
+
+Some segments contain multiple types. Resolution rules:
+
+1. **Higher priority wins** for primary classification
+2. **Secondary types are noted** in the artifact metadata: `secondary_types: [insight, action-item]`
+3. **Decision + Action:** Classify as `decision`, extract action as sub-element
+4. **Insight + Advice:** If speaker is mentor/advisor, classify as `advice`. Otherwise, `insight`.
+5. **Question + Insight:** If the question reveals new information, classify as `insight`. If purely asking, classify as `question`.
+
+---
+
+## Cross-Reference: Section Mapping
+
+After classification, the segment type combines with the speaker role to determine the target room section. See `references/meeting/section-mapping.md` for the full routing matrix.

package/references/meeting/speaker-profile-template.md

@@ -0,0 +1,219 @@
+# Speaker Profile Template -- ICM Nested Folder Structure
+
+*Used by `file-meeting` to create speaker profiles when a new speaker is encountered.*
+
+---
+
+## Directory Structure
+
+When `file-meeting` encounters a speaker not yet in the room, it creates the following ICM nested folder profile:
+
+```
+room/team/{role-plural}/{firstname-lastname}/
+  PROFILE.md
+  insights/
+  advice/
+  connections/
+  concerns/
+```
+
+---
+
+## Role-to-Directory Mapping
+
+| Speaker Role | Directory Plural | Example Path |
+|-------------|-----------------|--------------|
+| mentor | mentors | room/team/mentors/lawrence-aronhime/ |
+| researcher | researchers | room/team/researchers/lisa-wong/ |
+| team-member | members | room/team/members/david-park/ |
+| investor | investors | room/team/investors/michael-torres/ |
+| advisor | advisors | room/team/advisors/rachel-kim/ |
+| customer | customers | room/team/customers/james-carter/ |
+| founder | founders | room/team/founders/sarah-chen/ |
+| partner | partners | room/team/partners/alex-johnson/ |
+| domain-expert | domain-experts | room/team/domain-experts/maria-garcia/ |
+| government | government | room/team/government/robert-smith/ |
+| competitor | competitors | room/team/competitors/tom-wilson/ |
+| unknown | contacts | room/team/contacts/unknown-speaker-1/ |
+
+**Name formatting:** Lowercase, hyphenated. "Sarah Chen" becomes `sarah-chen`. Handle edge cases:
+- Middle names: include or omit based on uniqueness needs
+- Titles: strip "Dr.", "Prof.", "Mr.", "Ms." from folder name (preserve in PROFILE.md)
+- Suffixes: strip "Jr.", "III", etc. from folder name (preserve in PROFILE.md)
+
+---
+
+## PROFILE.md Template
+
+```markdown
+---
+name: {Full Name}
+roles:
+  - {speaker_role from 12-type taxonomy}
+primary_role: {speaker_role from 12-type taxonomy}
+role: {speaker_role from 12-type taxonomy}
+status: active
+last_active: {YYYY-MM-DD}
+affiliation: {organization, if known}
+first_meeting: {YYYY-MM-DD}
+meetings_attended: 1
+created_by: file-meeting
+research_status: pending
+last_updated: {YYYY-MM-DD}
+---
+
+# {Full Name}
+
+**Role:** {role} | **Affiliation:** {affiliation or "Unknown"}
+
+## Context
+
+{How this person was encountered. Auto-generated from meeting context.}
+
+First appeared in: [[meetings/YYYY-MM-DD-{meeting-name}/summary.md]]
+
+## Expertise
+
+{Inferred from their contributions. Updated across meetings.}
+
+## Contributions
+
+[Computed by compute-team -- do not edit manually]
+```
+
+---
+
+## PROFILE.md Field Definitions
+
+| Field | Type | Default | Description |
+|-------|------|---------|-------------|
+| name | string | -- | Full display name (with titles if applicable) |
+| roles | list | [{role}] | List of roles this speaker has held (Phase 7+) |
+| primary_role | string | {role} | Current primary role from 12-type taxonomy (Phase 7+) |
+| role | string | unknown | One of the 12 speaker roles (Phase 6 backward compat) |
+| status | enum | active | Lifecycle status: active, inactive, archived (Phase 7+) |
+| last_active | date | -- | Date of most recent meeting participation (Phase 7+) |
+| affiliation | string | "Unknown" | Organization, company, or institution |
+| first_meeting | date | -- | Date of the meeting where first encountered |
+| meetings_attended | integer | 1 | Incremented each time the speaker appears |
+| created_by | string | file-meeting | Always `file-meeting` for auto-created profiles |
+| research_status | enum | pending | See research status values below |
+| last_updated | date | -- | Date of most recent profile update |
+
+### Research Status Values
+
+| Status | Meaning |
+|--------|---------|
+| pending | Default -- no research has been done on this speaker |
+| in-progress | `scripts/research-speaker` is running or was interrupted |
+| complete | Web research has been performed and integrated |
+| skipped | User chose to skip research for this speaker |
+
+### Status Lifecycle Values
+
+| Status | Meaning |
+|--------|---------|
+| active | Speaker has participated in a meeting within the last 90 days |
+| inactive | No meeting participation in 90+ days (computed by compute-team) |
+| archived | Manually archived by user -- excluded from active team scans |
+
+**Important:** Proactive web research runs AFTER the filing pipeline via `scripts/research-speaker`, NOT during filing. The filing pipeline should never block on external API calls. The profile is created with `research_status: pending` and a separate background process handles enrichment.
+
+### Backward Compatibility
+
+Phase 6 profiles have `role:` (singular). Phase 7 adds `roles:` (list) and `primary_role:`. compute-team reads `roles:` first, falls back to `role:` as single-element list.
+
+When scanning profiles, use this resolution order:
+1. Read `roles:` -- if present, use as the role list
+2. If `roles:` is absent, read `role:` and wrap as a single-element list: `[{role}]`
+3. `primary_role:` is always the current active role for routing and display
+
+---
+
+## Computed Contributions Section
+
+The `## Contributions` section in PROFILE.md is **computed by compute-team**, not maintained manually or by file-meeting.
+
+compute-team rebuilds this section by scanning all room artifacts for matching `attribution.speaker` or `speaker` fields, then generating a per-meeting contribution summary:
+
+```markdown
+## Contributions
+
+### From Board Strategy Session Q1 (2026-03-15)
+- **decision** in solution-design: Focus on enterprise segment first
+- **insight** in market-analysis: Enterprise grew 34% last quarter
+
+### From Mentoring Session (2026-03-22)
+- **advice** in problem-definition: Reframe the problem before solving
+```
+
+This replaces the Phase 6 pattern of manually filing copies to speaker subfolders (insights/, advice/, etc.). The subfolders are retained for backward compatibility but file-meeting no longer writes to them.
+
+---
+
+## Subfolder Purposes (Legacy)
+
+The subdirectories (insights/, advice/, connections/, concerns/) are created for backward compatibility with Phase 6 profiles. As of Phase 7, file-meeting no longer creates copies in these subfolders. Speaker contributions are tracked via the computed Contributions section above.
+
+### insights/
+
+Filed insights attributed to this speaker. Legacy -- no new files created by file-meeting in Phase 7+.
+
+### advice/
+
+Filed advice attributed to this speaker. Legacy -- no new files created by file-meeting in Phase 7+.
+
+### connections/
+
+People, organizations, or resources this speaker has mentioned or introduced.
+
+### concerns/
+
+Questions, risks, or objections this speaker has raised.
+
+---
+
+## Profile Updates Across Meetings
+
+When a known speaker appears in a subsequent meeting:
+
+1. **Increment** `meetings_attended` in PROFILE.md frontmatter
+2. **Update** `last_updated` to today's date
+3. **Update** `last_active` to today's date
+4. **Do NOT overwrite** existing content -- profiles are append-only for contributions
+5. Contributions are computed by compute-team, not filed manually
+
+---
+
+## Role Changes
+
+A speaker's role can change across meetings (e.g., advisor becomes investor after a funding round). Handle by:
+
+1. **Keep the profile in its original directory** (don't move folders)
+2. **Update the `primary_role` field** in PROFILE.md frontmatter
+3. **Append the new role** to the `roles:` list (preserves role history)
+4. **Update the `role` field** to match `primary_role` (backward compat)
+5. **Add a note** in the Context section: "Role changed from advisor to investor as of {date}"
+6. **Future filing** uses the updated role for routing priority calculations
+
+---
+
+## Unknown Speakers
+
+When a speaker cannot be identified (raw paste format, unlabeled audio):
+
+1. Create profile at `room/team/contacts/unknown-speaker-{N}/`
+2. Set `research_status: pending`
+3. Set `role: unknown` and `roles: [unknown]`
+4. After user identifies the speaker, rename the folder and update PROFILE.md
+5. All filed artifacts maintain correct links via the `attribution.speaker` field in their frontmatter
+
+---
+
+## Cross-Reference
+
+- Role taxonomy: `references/meeting/section-mapping.md` (12 roles defined)
+- Segment types filed to subfolders: `references/meeting/segment-classification.md`
+- Artifact format in subfolders: `references/meeting/artifact-template.md`
+- Meeting summary links to profiles: `references/meeting/summary-template.md`
+- Research enrichment: `scripts/research-speaker` (future -- Phase 6, Plan 03)