Changelog#

Traceable development steps of the platform. Newest first.

2026-07-27 — WebWoW_Audio console section, English docs, real-design chrome#

WebWoW_Audio as a console section: script editor per touchpoint with live analysis, listen button (TTS render), voice-to-text upload, recording/transcription switches, and the widget lead inbox — rendered in the genuine console design (shared chrome module, no rebuilt tokens).
Docs in English with the console's real design chrome (rail, topbar, cards) instead of an approximated look.

WebWoW_Audio (production): script registry for eight customer-journey touchpoints (inbound greeting, hold, hangup, website visit, lead success, meeting, callback, chat), tenant overrides, deterministic quality analysis, TTS render and voice-to-text as API.
Cartesia as a first-class engine: direct path via api.cartesia.ai (Sonic-3, Ink) with automatic fallback to the verified Together path; mode visible in /health and X-Engine-Mode. TTS-STT round trip verified.
Website widget: callback, meeting, and chat leads as a one-line embed; public lead intake with honeypot and rate limit; lead management in the console.
Customer switches: recording and transcription can be turned on and off per tenant.
This docs portal: self-built without a third-party subscription, generated from Markdown, with search, light/dark themes, and section navigation.

Inbound calls run through the TENIOS call control path up to a real conversation: AI disclosure, dialog via the conversation LLM, transfer, and clean hangup.
Fallback to keypad input when no speech recognition is configured in the carrier account — noted in the transcript.
The console reads real data from /v2/numbers, /v2/assistants, and /v2/calls.

Two separate services (control plane and data plane), enforced tenant isolation, contracts for telephony and voice ports ("one wire, two ports").
Engine registry with empirical usableNow instead of marketing claims.
Voice Runtime live on staging, systemd-hardened.