Compare architecture by runtime boundaries, not shared business logic

A service can reuse production flow definitions and tool handlers without sharing the production architecture. Compare runtime boundaries separately: ingress, media transport, process topology, state ownership, scaling and failure isolation, persistence, and human-transfer behavior. If a demo replaces telephony and a runner fleet with browser audio and one stateful web process, describe it as business-logic reuse, not end-to-end architectural equivalence. Stable provider interfaces may allow implementations to differ without changing the architecture; the distinction matters when the boundaries and operational semantics themselves move.

Applies when: assessing whether a prototype, demo, or migration target matches a production voice-agent system. Keywords: architecture comparison demo production browser WebRTC telephony process topology