Meeting Assistant is the user-facing application for turning recorded meetings into reviewed, distributable protocols. It uses Meeting Lab as its reusable local processing backend.

Current MVP Direction

The first product milestone is a desktop GUI that lets a user:

select an existing audio recording
create and edit structured meeting metadata and participants
optionally map anonymous SPEAKER_XX labels to known participants
start the Meeting Lab processing pipeline
follow stage-based progress
review and edit the generated protocol
export the reviewed result

The MVP does not include integrated recording. OBS Studio remains a recommended reference recorder, but imported audio is not tied to OBS-specific behavior.

Processing Pipeline

Audio file
    -> FFmpeg preparation (mono, 16 kHz PCM WAV)
    -> whisper.cpp transcription (large-v3-turbo)
    -> optional pyannote.audio Community-1 diarization
    -> direct full-transcript protocol generation
    -> human review and export

Meeting Assistant calls Meeting Lab's reusable Python API (MvpMeetingConfig, MvpRunResult and run_mvp_meeting(...)). It does not run the Meeting Lab CLI as a subprocess. Fixed five-minute audio chunking is not a required part of this workflow.

GPU acceleration is supported where available, but CPU execution remains a compatibility path. Diarization is optional and produces anonymous speaker labels. A label identifies a participant only when the user explicitly confirms the mapping; automatic speaker-name inference is not allowed.

Product Outputs

The product direction includes:

a detailed, contextual protocol for review and continued work
a shorter version suitable for participants and distribution

The detailed direct-protocol flow is the practical MVP direction. The shorter version may be implemented after the initial GUI. Human review remains part of the workflow for all generated protocols.

Project Boundary

Meeting Lab owns reusable audio preparation, transcription, diarization, orchestration and protocol-generation logic. Meeting Assistant owns the GUI, context and participant editing, explicit speaker mapping, progress display, protocol editing and export.

The code currently contains the initial Meeting Assistant project and domain foundation. The GUI has not yet been implemented.

See Architecture, Project Knowledge, Roadmap and ADR 0011.