Recording
01:08Record
writing…Under the hood
What is actually running on this page, what is a recording, and what a production deployment would still need.
What is live
The whole interface. The waveform, the intent graph, the record panel and the log stream all render in your browser from one script. Every column is a pure function of the replay clock, so pausing and replaying gives you the identical frame. The waveform is 613 fixed amplitudes per channel, written into the repo rather than generated, because a random waveform would drift between renders and make the recorded run claim false.
What is replayed
The call. 17 turns, 28 log lines, the cost split and the per turn latency all come from one recorded run and play back at the original speed. There is no audio file in this build, which is why the Audio download is dimmed. Nothing on this page fetches, polls, or calls a model. There is no Math.random and no Date anywhere in the code.
What production needs
A live telephony leg on Twilio, Deepgram for transcription, Claude for the model, ElevenLabs for the voice, and the CRM write behind a real API. The second factor goes out through a real SMS provider. The identity policy and the audit record are the two parts I would ship exactly as they are here, because refusing on one factor and writing the denial before the release is the whole point.
Two honesty notes. The narrow layout is invented. There is no responsive capture of the reference product anywhere, so the breakpoint behaviour below 1280 is my rule and not a recreation. The record panel and the identity gate are original work too, built out of the reference's card, badge and node parts, because nothing in the reference writes a customer record or refuses a caller mid call.