Two voices, one auth
Leo never lives outside my auth, so the site hears VM and I hear Leo.
Leo reads an overnight report to me in the morning at 1.1x. Same stack, split by authentication: an unauthenticated user gets the public Virtual Mike voice, and when I am authed I get Leo giving status on what is in flight and where my attention needs to be.
The auth boundary is the decision. The voice is just how it sounds.
AUTH BOUNDARY
Leo talks only to me
Leo never lives outside my auth. A user on the site hears the public Virtual Mike voice. Authed, I hear Leo and interact with the stack as that. Like my JARVIS.
SPEED SETTABLE
1.1x belongs in the payload
There is one voice, VM Voice V1.0, at 1.1x speed. I want the speed settable rather than fixed. It should be in the payload anyway.
NO STITCHING
Under the cap
The voice has a character cap. Keeping the overnight report under it means no stitching. The constraint shapes the brief, not the delivery.