Digital Twin / how a reply is shown

Watch a question become a reply

The app answers questions about my work in text, with optional voice and a moving character. This example uses no microphone or AI service.

Card = question · Card stop = my work profile
Puppet = optional voice/3D · Front tray = readable reply

DIGITAL TWIN / REPLY EXAMPLEVoice and 3D are optional

Select a part to see what it doesQuestion enters

Your question: the card represents what you type or say.

Move through the example

The readable reply

Reply appears after the context step.

Choose a part to see how it connects to Digital Twin.

The theatre represents the software. Open the original demo to use the real character and assistant.

Input: typed questions work without microphone permission.

Context: the server uses a maintained professional profile; replies can still be wrong.

Reply: readable chat text is the foundation.

Voice: audio energy and transcript timing drive approximate, not phoneme-perfect mouth cues.

Avatar: authored gesture states blend; the optional 3D view is represented by the curtains.

Fallback: readable text remains when microphone or model loading is unavailable.

The cue enters the context stop, the puppet represents optional speech/gesture output, and the front tray is the text fallback. All explanations remain readable; animation controls require JavaScript.