STREAMING SPEAKER REVIEW WORKSHEET
Prepared October 11, 2026. Free resource, not free provider usage.

Purpose: rehearse a revision-safe review view before authorizing real audio.
These invented values are an offline teaching fixture, not provider output,
a complete API payload, a benchmark or evidence of Burki runtime behavior.
Native Burki AssemblyAI speaker-label options are not enabled.

1. DEFINE THE REVIEW
Owner: ____________________  Reviewer: ____________________
Fixture version: __________  Application version: __________
Purpose of transcript: ____________________________________
Required languages / accents: _____________________________
Authorized audio source and permission: ___________________
Retention period / approved viewers: ______________________
Provider / exact model / SDK version: _____________________
Requested configuration / observed configuration: _________
Session key: ____________  Turn key includes session? ______

Do not turn anonymous labels into authenticated identity. Request ownership,
identity, authorization and actual business outcomes need separate evidence.

2. ORIGINAL FICTIONAL CONVERSATION
Session: venue-enquiry-fixture-01
Turn 0, initial label A:
  We need a room for a community meeting.
Turn 1, initial label A:
  I am joining the enquiry. Please ask staff about the smaller room too.
Turn 2, initial label A:
  Keep my original callback details for the enquiry.

Planned correction: turn 1 becomes label B. No text is rewritten.
This is deliberately not a promise about how a provider labels real speakers.

Expected business state:
  A room enquiry remains open for staff clarification.
  No room is reserved. No person is authenticated through a label.
  Callback details are not changed automatically by a speaker correction.

3. YOUR STORAGE AND PROCESSING PLAN
Original events location: __________________________________
Latest review view location: _______________________________
Business request identifier: _______________________________
Stable action identifier / duplicate prevention: ___________
Revision association and validation rule: __________________
Unknown turn handling: _____________________________________
Where finalization status appears to staff: _________________
How corrected summaries are versioned: _____________________

Do not overwrite received evidence just to make the review look clean.
Do not replay external actions when attribution changes.

4. OFFLINE ACCEPTANCE CASES
A. Normal turn 1 correction
   Expect: review label changes to B; original remains available;
   text/timings remain intact; no booking, callback or request duplication.
   Observed / evidence: _____________________________________

B. Empty correction list
   Expect: existing turns retained, no deletion or duplicate action.
   Observed / evidence: _____________________________________

C. Repeat the same correction
   Expect: same review result; no extra external action.
   Observed / evidence: _____________________________________

D. Later correction to the same turn
   Expect: processing order and review version recorded; last applicable
   correction changes the view without losing earlier received evidence.
   Observed / evidence: _____________________________________

E. Correction refers to an unknown turn or unexpected words
   Expect: explicit investigation state, no silent position-based guessing.
   Observed / evidence: _____________________________________

F. Identical turn number in another session
   Expect: first session's correction does not alter the second session.
   Observed / evidence: _____________________________________

G. Connection ends unexpectedly
   Expect: last received attribution retained, finalization not observed;
   staff can see uncertainty rather than a fabricated complete state.
   Observed / evidence: _____________________________________

H. Old label confidence present
   Expect: it is not presented as confidence for a replacement label.
   Observed / evidence: _____________________________________

I. A summary was already reviewed or shared
   Expect: a correction produces a new review version and a visible reason;
   it does not quietly modify a historical business confirmation.
   Observed / evidence: _____________________________________

5. BEFORE ANY AUTHORIZED PROVIDER TEST
Check current request/model contract, SDK event handling, audio format,
credential scope, budget, permission and retention. This worksheet does not
perform or authorize a paid test. A local fixture pass is not provider acceptance.

Date / exact primary docs checked: _________________________
Normal close sequence receipt: ____________________________
Final revision observed? ______  Terminal event observed? ___
Unexpected close / errors: _________________________________
Actual model receipt: ______________________________________
Billable usage and actual cost receipt: ____________________
Language / accent / noise conditions and sample count: _____
Remaining limitations / staff fallback: ____________________

6. DECISION
[ ] Offline processing reviewed, provider use still untested
[ ] Authorized provider exercise completed with linked evidence
[ ] Incomplete evidence, keep attribution provisional
[ ] Do not deploy; resolve the listed failure first
Reason / owner / follow-up: _________________________________

Primary reference:
https://www.assemblyai.com/docs/streaming/label-speakers-and-separate-channels
https://www.assemblyai.com/docs/streaming/message-sequence
https://www.assemblyai.com/pricing
Original guide:
https://burki.dev/blog/streaming-speech-to-text-speaker-diarization