NOVA-3 CONFIGURATION STATE WORKSHEET
Free planning resource | Checked October 26, 2026
Original application design and synthetic fixtures. No provider request was run.
Production recognition and telephone usage can cost money.
Companion: https://burki.dev/blog/deepgram-nova-3-configure-acknowledgments

1. DEFINE ONE CONNECTION
Owner / reviewer:
Review date and timezone:
Application connection instance ID:
Provider stream ID (redacted when shared):
Model and endpoint region:
Installed SDK version and source checked:
Initial vocabulary evidence:
Credentials: NEVER record them in this worksheet.

2. EXPLAIN THE INTENDED CHANGE
Fictional example: Northline Parts, general reception to specialist seals.
Business reason: caller asks about the CalderaFlow line.
Proposed terms: CalderaFlow | PXR42 | seal cartridge
Who reviews compatibility and stock: qualified staff, not the recognizer.
Actual task:
Desired terms:
Caller clarification needed:

3. SEPARATE APPLICATION RECORDS
These labels and generation numbers are application-owned, not provider fields.
Active generation:
Active list / digest:
Evidence supporting active state:
Proposed generation:
Proposed list / digest:
Local send observation time:
Outcome evidence and observation time:
Disposition: pending / accepted / rejected / unknown
Next action owner:

Protocol reminder: keyterms replaces the list; [] clears it. Keep one update
pending. Success or failure is evidence; socket-write completion alone is not.
Reference: https://developers.deepgram.com/docs/configure

4. ORIGINAL SYNTHETIC FIXTURES
No row below is a provider execution or measured latency.

A. Acceptance
Start: connection A, active generation6.
Action: propose generation7, save exact intended list, observe local send.
Inject: success outcome for the pending operation on connection A.
Expected application assertion: generation7 becomes active; receipt retained.
Observed result:
Pass / fail / unknown:

B. Rejection
Start: connection A, active generation6, proposal7 pending.
Inject: rejection for the pending operation.
Expected: generation6 remains active; proposal7 retained as rejected attempt.
Staff note must not say a service order was completed.
Observed result:
Pass / fail / unknown:

C. Missing outcome
Start: proposal7 sent, no reply yet observed.
Inject: application timeout, then connection closes.
Expected: attempt unknown; no invented failure or acceptance.
New connection B must not be treated as continuation of A's configuration state.
Observed result:
Pass / fail / unknown:

D. Two department decisions
Start: proposal7 pending; desired department changes again.
Inject: a second business decision before first outcome is reconciled.
Expected: latest desired list may be stored locally without being labeled sent.
Record the rule for what to do after the first operation is resolved:
Observed result:
Pass / fail / unknown:

E. Late or duplicate evidence
Inject: duplicate old outcome, then event from retired connection A after B opens.
Expected: neither silently overwrites a newer reconciled state.
Record event association / duplicate handling rule:
Observed result:
Pass / fail / unknown:

F. Caller corrects a code
Original transcript reference: PXR24.
Later caller clarification: PXR42.
Expected: keep both records and attribute correction to caller clarification.
Do not rewrite the original transcript because vocabulary changed.
Observed result:
Pass / fail / unknown:

5. OPERATING DECISION
Offline fixtures passed:
Audio test authorized separately:
Measured recognition result, if later obtained:
Caller-heard test, if later obtained:
Costs and limits checked as of:
Unresolved outcomes / retained evidence:
Reviewer decision and next owner:

Do not use a vocabulary hint as a compatibility, inventory or fulfilment result.
Burki's initial editor vocabulary is a separate workflow. This worksheet does
not establish native mid-call configuration or a performed recognition test.