## ADDED Requirements

### Requirement: Meeting Assistant creates a note before transcription
Meeting Assistant SHALL create an Obsidian markdown note for a meeting session before transcription starts.

The note SHALL be the durable anchor for meeting metadata, user notes, assistant-discovered context, transcript references, summaries, decisions, and next steps.

#### Scenario: Session starts
- **WHEN** the user starts a new meeting session
- **THEN** Meeting Assistant creates a markdown note in the configured meetings folder before starting transcription

#### Scenario: User adds context before transcription
- **WHEN** the note exists before transcription starts
- **THEN** the user can add attendees, project context, meeting purpose, and other notes to that file

### Requirement: Meeting notes preserve user-authored content
Meeting Assistant SHALL preserve user-authored meeting notes and include them as input when generating summaries, decisions, and next steps.

#### Scenario: User writes notes during the meeting
- **WHEN** the user updates the meeting note while the meeting is active
- **THEN** Meeting Assistant keeps that content and incorporates it into generated meeting outputs

### Requirement: Meeting sessions are platform independent
Meeting Assistant SHALL support meeting sessions that do not originate from Teams, Zoom, or any other meeting software API.

Meeting software integrations MAY augment the meeting experience, but they SHALL NOT be required for the primary meeting capture, transcription, or summary flow.

#### Scenario: In-person meeting is captured
- **WHEN** the user starts transcription for an in-person meeting
- **THEN** Meeting Assistant captures and processes the meeting without requiring a meeting platform integration