OpenTranscribe — Post-Transcription Enrichment

OpenTranscribe — Post-Transcription Enrichment A workflow diagram generated by Archify. 01 / Core 02 / Speaker Identity 03 / Search 04 / LLM Enrichment Dispatched on finalize Speaker identity chain Finalize · transcript saved · Core Finalize transcript saved Provenance · what ran, where · Core › Dispatched on finalize · per step Provenance what ran, where per step Voiceprint · always this server · Speaker Identity › Dispatched on finalize · inline or cpu stage Voiceprint always this server inline or cpu stage Gender/Age · speaker attribute detection · Speaker Identity › Speaker identity chain Gender/Age speaker attribute detection Speaker ID · LLM suggestion · Speaker Identity › Speaker identity chain · never auto-applied Speaker ID LLM suggestion never auto-applied Reclustering · selective, on request · Speaker Identity › Speaker identity chain Reclustering selective, on request Indexing · OpenSearch whole-doc + chunks · Search › Dispatched on finalize Indexing OpenSearch whole-doc + chunks Summarization · LLM summary · LLM Enrichment › Dispatched on finalize Summarization LLM summary Topics · LLM topic extraction · LLM Enrichment › Speaker identity chain Topics LLM topic extraction Analytics · talk-time, stats · LLM Enrichment › Speaker identity chain Analytics talk-time, stats record_stage context for LLM on request Legend Agent logic Context / trace External system

Voiceprints and provenance

  • • Local engine: vectors come back inline from the transcription task (inline_native); any other detector: services/voiceprint_extractor.py on the cpu queue
  • • Every step writes its own entry through services/file_provenance.record_stage: transcription, diarization, voiceprints, summary, topics, speaker_names

LLM speaker ID is a suggestion, never a write

  • • Gender/age detection runs first so the LLM has that context
  • • Confidence-scored suggestions surface for manual approval only — repo-wide rule

Independent fan-out

  • • Indexing, summarization, and analytics all dispatch right after finalize
  • • None of them block the speaker-identity chain or each other