meeting-assistant/openspec/changes/dedupe-speaker-attendee-aliases/specs/meeting-transcription/spec.md

MODIFIED Requirements

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 a match is confirmed and the meeting note attendees contain both the speaker display name and one or more accepted aliases for that same speaker, Meeting Assistant SHALL remove the alias attendee entries and keep the display name entry.

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

Scenario: Confirmed match removes duplicate aliases

• GIVEN the speaker identity database contains canonical speaker Christopher with alias Chris
• AND the meeting note attendees contain both Christopher and Chris <chris@example.com>
• WHEN live or final speaker matching confirms a diarized speaker is Christopher
• THEN Meeting Assistant keeps Christopher in the meeting note attendees
• AND removes Chris <chris@example.com> from the meeting note attendees