Initialize meeting assistant

2026-05-18 23:38:47 +02:00
commit 90df1edc03
20 changed files with 967 additions and 0 deletions
@@ -0,0 +1,19 @@
+## ADDED Requirements
+
+### Requirement: Agents can use project context tools
+Meeting Assistant SHALL expose tools that allow agents to look up project information, retrieve keyword-relevant context, and inspect meeting-derived knowledge.
+
+#### Scenario: Agent looks up meeting project context
+- **WHEN** a meeting note identifies a project
+- **THEN** the agent can retrieve relevant project context through Meeting Assistant tools
+
+### Requirement: Agents can only mutate project files with explicit project binding
+Meeting Assistant SHALL only expose project file mutation tools when the target project is known and mutation is permitted by user instruction or project context.
+
+#### Scenario: Project mutation is permitted
+- **WHEN** the user or project context permits file updates for a known project
+- **THEN** the agent can use controlled tools to change files in that project
+
+#### Scenario: Project mutation is not permitted
+- **WHEN** the target project is missing or mutation permission is absent
+- **THEN** Meeting Assistant does not expose project file mutation tools for that request
@@ -0,0 +1,30 @@
+## 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
@@ -0,0 +1,12 @@
+## ADDED Requirements
+
+### Requirement: Meeting Assistant generates meeting outputs
+Meeting Assistant SHALL generate a summary, decisions, and next steps from the meeting transcript, metadata, user notes, and assistant-discovered context.
+
+#### Scenario: Meeting processing completes
+- **WHEN** transcription and context collection have completed
+- **THEN** Meeting Assistant generates a summary, decisions, and next steps for the meeting note
+
+#### Scenario: User notes conflict with transcript interpretation
+- **WHEN** user-authored notes provide context that changes the interpretation of the transcript
+- **THEN** Meeting Assistant considers those notes during summary and next-step generation
@@ -0,0 +1,14 @@
+## ADDED Requirements
+
+### Requirement: Meeting Assistant transcribes meetings with speaker attribution
+Meeting Assistant SHALL transcribe meeting audio and associate transcript segments with speakers when speaker attribution is available.
+
+The transcription contract SHALL remain independent of the meeting source so that local audio, in-person meetings, and future meeting-platform integrations can use the same downstream processing.
+
+#### Scenario: Speaker-attributed transcript is produced
+- **WHEN** meeting audio is transcribed and speaker attribution is available
+- **THEN** the transcript contains ordered speaker-attributed segments
+
+#### Scenario: Speaker attribution is unavailable
+- **WHEN** meeting audio is transcribed but speaker attribution is unavailable
+- **THEN** Meeting Assistant keeps the transcript and marks speaker identity as unknown rather than discarding the meeting
@@ -0,0 +1,14 @@
+## ADDED Requirements
+
+### Requirement: Meeting Assistant maintains project knowledge
+Meeting Assistant SHALL maintain project knowledge based on meeting content and future generic information sources.
+
+Project knowledge SHALL support retrieval by project context and relevant keywords.
+
+#### Scenario: Meeting has project context
+- **WHEN** a meeting note identifies a project
+- **THEN** Meeting Assistant can associate transcript-derived and summary-derived knowledge with that project
+
+#### Scenario: Agent retrieves project context
+- **WHEN** an agent needs context for a meeting or follow-up task
+- **THEN** Meeting Assistant can retrieve relevant project knowledge and source references