# Resilient Transcript Workflow

## Summary

Make live transcript persistence independent from workflow-rule success. Transcript lines should be written before optional workflow transformations run, changed lines should be rewritten in place, and workflow rule activity/errors should be logged clearly enough to diagnose broken local rules.

## Motivation

A running meeting showed Azure Speech continuing to emit live segments while the transcript markdown stopped advancing. The current append path waits for workflow transformation before writing each line, so a failing or stalled workflow rule can make transcription appear dead even when ASR is still producing output.

A separate earlier run logged a disk-full `IOException` while writing the temporary WAV, despite the expected WAV size being small. That anomaly should be tracked separately because the current evidence does not identify a safe corrective behavior beyond better diagnostics.

## Scope

- Write the formatted live transcript line before transcript-line workflow processing.
- Rewrite the just-written transcript line if workflow rules change it.
- Keep transcript writes going when transcript-line workflow rules fail.
- Log triggered workflow rules, workflow rule completion, and workflow rule errors with event context.
- Track follow-up investigation for anomalous temporary-recording disk-full failures.

## Out Of Scope

- Changing ASR providers or audio capture format.
- Restarting or interrupting an active meeting.
- Automatically deleting files or freeing disk space after a disk-full error.