meeting-assistant/openspec/changes/archive/2026-05-22-add-speaker-identity-references/specs/meeting-transcription/spec.md

MODIFIED Requirements

Requirement: Meeting Assistant learns speaker identities locally

Meeting Assistant SHALL maintain a local SQLite speaker identity database in the user's application data folder.

The speaker identity database SHALL store speaker identities, optional canonical names, aliases, candidate names, meeting file references, and a bounded set of WAV snippets per identity.

Meeting file references SHALL include the meeting note file address and the transcript file address.

Meeting Assistant SHALL calculate speaker identity participation counts from meeting file references when needed instead of persisting a denormalized transcript count.

Each speaker identity SHALL store a last-modified timestamp used by active-age filtering, and Meeting Assistant SHALL update it whenever the identity is created or modified by identification, candidate updates, snippet changes, reference changes, or merge operations.

The configured maximum snippet count per identity SHALL prevent unbounded growth.

Scenario: Unknown speaker is learned from meeting attendees

• WHEN a finished transcript contains an unmatched diarized speaker and the meeting note has attendees
• THEN Meeting Assistant stores a new unnamed speaker identity with candidate names from the attendees that were not already matched in that meeting
• AND stores a meeting file reference for that identity

Scenario: Speaker snippets are bounded

• WHEN Meeting Assistant adds a snippet for an identity that already has the configured maximum number of snippets
• THEN Meeting Assistant does not store more snippets for that identity

Scenario: Identity modification updates active-age timestamp

• WHEN Meeting Assistant creates, identifies, updates candidates for, stores snippets for, stores references for, or merges a speaker identity
• THEN Meeting Assistant updates that identity's last-modified timestamp

Requirement: Speaker candidates are eliminated across meetings

Meeting Assistant SHALL update candidate names for a matched unnamed identity using the intersection of its existing candidate names and the current meeting attendees.

Meeting Assistant SHALL treat identity aliases as acceptable names during candidate elimination and when excluding already-matched attendees from new unmatched speaker candidates.

When the candidate intersection leaves exactly one candidate, Meeting Assistant SHALL promote that candidate to the canonical speaker name.

When an identity receives a canonical name, Meeting Assistant SHALL append an audit line to each referenced transcript in the form <date> <speaker label> was identified as <name>.

When the candidate intersection is empty, Meeting Assistant SHALL replace the oldest stored snippet for that identity and reset candidates from the current meeting attendees, because the previous snippet may have been dirty.

Scenario: Candidate elimination promotes canonical name

• GIVEN an unnamed identity has candidate names John and Mike
• WHEN that identity matches a speaker in a later meeting with attendees Jane, John, and Chris
• THEN Meeting Assistant removes Mike from the identity candidates and promotes John as the canonical name
• AND appends the identity naming audit line to the identity's referenced transcripts

Scenario: Alias participates in candidate elimination

• GIVEN an unnamed identity has candidate name Michael and alias Mike
• WHEN that identity matches a speaker in a later meeting with attendee Mike
• THEN Meeting Assistant treats Mike as matching Michael
• AND promotes Michael as the canonical name

Scenario: Empty candidate intersection resets candidates

• GIVEN an unnamed identity has candidate names John and Mike
• WHEN that identity matches a speaker in a later meeting with attendees Jane and Chris
• THEN Meeting Assistant resets the identity candidates to Jane and Chris
• AND replaces the oldest stored snippet for that identity with the current speaker snippet

Requirement: Speaker identity matches relabel transcripts

Meeting Assistant SHALL attempt to match unknown diarized speaker snippets against known speaker identities ordered by calculated meeting reference count.

Speaker identity matching SHALL use a dedicated Azure Speech diarization verifier component rather than the configured speech recognition pipeline.

The matcher SHALL test at most the configured batch size of known people per diarization session and continue with later batches until a match is found or no candidates remain.

The matcher SHALL prioritize identities whose canonical name or aliases match current meeting attendees.

After attendee-matched identities, the matcher SHALL order identities by calculated meeting reference count, filter out non-attendee identities whose last update is older than the configured active age, and cap the candidate set at the configured maximum match candidate count.

When a match is confirmed in final identity processing, Meeting Assistant SHALL store a meeting file reference for that identity.

When a match is confirmed and the identity has a canonical name, Meeting Assistant SHALL rewrite finished transcript segments for that diarized speaker with the canonical name.

When a match is confirmed and the matched speaker is not already listed in meeting note attendees by display name or alias, Meeting Assistant SHALL add the speaker display name to the attendee list.

When Meeting Assistant writes attendees from calendar metadata, it SHALL match attendee display names exactly against known identity canonical names and aliases, replace matches with the identity display name, and deduplicate attendees that map to the same identity.

Scenario: Finished transcript is relabeled after a confirmed match

• GIVEN the speaker identity database contains canonical speaker Chris
• WHEN a finished transcript has diarized speaker Guest03 and the matching backend confirms it is Chris
• THEN Meeting Assistant rewrites Guest03 segments in the transcript as Chris

Scenario: Confirmed match stores meeting reference

• GIVEN the speaker identity database contains canonical speaker Chris
• WHEN a finished transcript has diarized speaker Guest03 and the matching backend confirms it is Chris
• THEN Meeting Assistant stores the meeting note and transcript file addresses as a reference for Chris

Requirement: Speaker identities can be merged diagnostically

Meeting Assistant SHALL expose a diagnostic endpoint that merges duplicate speaker identities.

The merge process SHALL compare recently-created identities, using a configurable recent age that defaults to two weeks, against all other identities in matcher batches bounded by the configured batch size.

The merge process SHALL require a match and a second validation match using a different source sample before merging two identities.

When identities are merged, Meeting Assistant SHALL retain one identity, move useful names from the merged identity into aliases, combine meeting file references, retain a bounded set of snippets from both identities, and append an audit line to each referenced transcript in the form <date> <name 1> and <name 2> were merged.

Scenario: Recently-created duplicate identity is merged

• GIVEN a recently-created identity and an older identity have matching speaker snippets
• WHEN the diagnostic merge endpoint is triggered
• THEN Meeting Assistant validates the match twice with different source snippets
• AND merges the recent identity into the older identity
• AND stores the recent identity name as an alias on the retained identity
• AND keeps meeting file references from both identities
• AND appends the merge audit line to the referenced transcripts

Scenario: Old identities are not used as merge sources

• GIVEN two identities older than the configured recent age
• WHEN the diagnostic merge endpoint is triggered
• THEN Meeting Assistant does not compare them as source identities