38 lines
1.4 KiB
Markdown
38 lines
1.4 KiB
Markdown
# ADR 0001: Project Vision
|
|
|
|
## Status
|
|
|
|
Accepted, amended by [ADR 0011](0011-use-meeting-lab-mvp-backend.md)
|
|
|
|
## Context
|
|
|
|
The project aims to create a local-first meeting assistant that transforms recorded meetings into high-quality transcripts and structured organizational knowledge.
|
|
|
|
Existing commercial meeting assistants often depend on bots, cloud services, vendor-specific workflows or opaque AI pipelines. This project is intended to provide more control over audio capture, transcription, knowledge extraction and long-term data ownership.
|
|
|
|
## Decision
|
|
|
|
The project will be developed as a modular Python application with a clear pipeline:
|
|
|
|
Recording
|
|
→ Transcription
|
|
→ Speaker Diarization
|
|
→ AI Analysis
|
|
→ Knowledge Extraction
|
|
→ Export
|
|
|
|
The transcript is treated as the canonical source. AI-generated summaries and knowledge objects are derived artifacts.
|
|
|
|
## Consequences
|
|
|
|
- Audio and transcript quality have priority over UI features.
|
|
- The system must preserve original recordings and original transcripts.
|
|
- AI outputs must be reproducible where practical.
|
|
- Modules should remain replaceable.
|
|
- The project should avoid unnecessary vendor lock-in.
|
|
|
|
ADR 0011 narrows the practical MVP to a user-facing application over the
|
|
reusable Meeting Lab backend. Direct protocol generation is the validated MVP
|
|
path; a separate knowledge-extraction stage remains a possible future
|
|
extension rather than an MVP requirement.
|