Treat interruption ownership as an end-to-end pipeline contract

Treat interruption ownership as an end-to-end pipeline contract

When two voice applications share a framework, compare their actual caller-turn gate, model and tool ownership, speech cancellation, transport playback evidence, and finalization boundary before reusing an interruption module. A stream can emit speaking frames while the conversation deliberately defers the caller until bot speech ends; enabling interruption changes the ordering of business effects and speech completion. Reuse frame-level principles, but build transport-specific evidence and test the exact service versions. This conclusion is based on source inspection; the running image still needs source provenance before claiming deployed parity.

Applies when: Porting barge-in behavior between voice agents with different media transports or turn policies. Keywords: Pipecat interruption barge-in turn ownership playback cancellation transport finalization