TALK APP LAYER: what Nick sees, hears and taps when he talks to Skippy and Neeko — the app team's lane

Updated just now.

TRUE NOW (2026-09-15). Both updated Talk screens are live. All sixteen conversation checks have passed independent review across the family app and business workspace: answers grow as they arrive, progress is replaced, returned results do not repeat, and the phone menus work. Their approved appearance is preserved. Testing uses verified paid OpenAI speech. A spoken interruption exposed a real fault: the answer pauses, then resumes while the speaker is still talking; its repair passes focused checks and awaits independent review before release, while keeping Nick’s chosen 0.7-second pause setting. Correctly matching thread replies to messages still needs proof. Speech streaming and continuous conversation with a named agent remain unfinished, so none of the five complete outcomes is closed.

LEFT. Five outcomes for the app team: the answer showing and speaking while it is still arriving, with an honest "still looking" while he checks; the voice playing from its first bytes instead of after the whole clip is made; Skippy answering a finished question almost at once but waiting when Nick is obviously mid-thought; talking to one named running agent turn after turn on the Status tab; and a frozen agreement between the two teams so an update from either side never breaks a screen already open. Nothing new is drawn; the look stays as approved.

0% overall0 of 5 steps finished
  1. Freeze the doors and the fence; prove old and new callers survive0%
    How we know

    Definition of done: the frozen contract list is signed in both plans, and old caller, new caller, wrong identity, wrong turn, duplicate event and unsupported version each get the fixture's response on the served proxies

    Proof: the relevant item

  2. Both Talk screens and the Status-tab thread behave0%
    How we know

    Definition of done: on the served family app and business workspace a turn shows and speaks its answer as it streams, shows interim progress replaced by the final answer, draws a returned result once and speaks it only live, stops sound on interruption, never repeats on reconnect, keeps the tap card and the menu; the Status-tab thread dictates, sends, shows delivery and speaks the reply

    Proof: the relevant item

  3. Play streamed speech as bytes arrive0%
    How we know

    Definition of done: on the served app speech begins before the provider finishes the clip, first sound within 0.5 s of the speech request on the pinned samples, no missing or repeated audio, sound stopped on interruption, an honest incomplete-answer line on a mid-stream failure

    Proof: the relevant item

  4. Finished his thought, or thinking0%
    How we know

    Definition of done: on the served app twenty completed-thought samples per surface start useful speech within two seconds while the pinned thinking-pause and correction samples produce zero premature answers and zero stale takeovers

    Proof: the relevant item

  5. Talk to a named running agent, continuously0%
    How we know

    Definition of done: on the served app ten consecutive spoken turns reach the selected running agent and return its associated answers, with correct switch, idle and ended behaviour

    Proof: the relevant item