Detect
TV-DEMO-0042 finds missing return-leg audio. Classify this as a capture gap, retain the outbound match and archive reference, and leave the failed run unchanged.
ASSURE / EXCEPTION WORKFLOW
A failed recording check needs more than an alert. It needs a path from detection to a reviewed resolution.
01 / RESPONSE MODEL
TV-DEMO-0042 finds missing return-leg audio. Classify this as a capture gap, retain the outbound match and archive reference, and leave the failed run unchanged.
Prepare the run ID, path, UTC time, severity and owner for the agreed response channel. Keep raw audio and sensitive counterparty details out of general notifications.
Open an incident with the source references, expected behavior, observed gap, affected scope and an accountable owner. Record an escalation deadline in the firm’s process.
After the capture mapping is corrected and authorized, create a new run. Keep the old result; compare both legs, markers and archive retrieval against the original scope.
Link the retest to the incident and the failed run. Review the evidence before closure; retain the change, reviewer decision and any remaining exceptions.
02 / INTERACTIVE ROUTING EXAMPLE
These are workflow destinations on the integration roadmap. This browser demo builds an example handoff only; it does not connect, send a message or create a ticket.
Example state: detected · EX-DEMO-07 open
03 / CLOSURE RULE
If the retest fails, the incident stays open. If access prevents retrieval, mark the result inconclusive and route the access issue to its owner. If the retest passes, the reviewer still checks scope and evidence before recording closure.
Keep both run IDs, the authorized change and reviewer rationale. This history lets trading technology, archive operations and compliance work from the same sequence rather than interpreting an isolated status badge.
NEXT / DEFINE THE TEST
Bring your recording architecture. Let’s define the right test.