Preserve business nodes when upgrading conversational context

When upgrading a Pipecat voice workflow for stronger models and continuous history, retain established business nodes, handlers and speech catalogs unless changing their behavior is intended. Change context strategy and model settings at the existing integration boundary. Replacing the workflow with one broad prompt can omit prerequisites, required disclosures, repeat/receipt steps and real scheduling effects; model capability cannot recover instructions that are absent. If consolidation is necessary, first enumerate reachable branches and prove equivalent tools, side effects and required speech. Retaining source preserves those definitions, but still requires native transition tests because new context and interruption handling can alter which branch runs.

Applies when: Improving conversational flexibility while preserving an established workflow's business behavior. Keywords: Pipecat model upgrade continuous context workflow parity nodes handlers prompts