# ADR 0005: Meeting Domain Model

## Status

Accepted

## Context

The application manages meetings as structured collections of related artifacts rather than as individual files.

A consistent domain model is required to support future extensions such as semantic search, knowledge extraction, versioning and database storage.

## Decision

The central entity of the application is the Meeting.

A Meeting owns or references all artifacts created during its lifecycle.

The initial domain model consists of:

- Meeting
- Recording
- Transcript
- Working Transcript
- Speaker
- Participant
- AI Artifact
- Action Item
- Decision
- Knowledge Object
- Attachment

Each entity has a unique identifier.

Relationships between entities shall be maintained explicitly.

## Consequences

- New artifact types can be added without changing the overall architecture.
- Storage implementation (files, SQLite, PostgreSQL, etc.) remains independent from the domain model.
- AI outputs become first-class entities rather than generated text files.
- Future integrations can operate on domain objects instead of file names.