A three-part system you can point at
Ask:Build a small diagram of input, memory, and output. Use three real shapes with labels, keep them still, and put a short explanation in a panel.Start with a stationary primitive:
left and right. Use stable IDs so the Entity can remove the diagram later. A shape’s label names the shape; text alone is not a substitute for a geometric object.
Put the detailed explanation in a panel:
A small physics demonstration
Ask:Spawn a periwinkle bouncy ball in front of us with a small upward toss. Explain that this is a simulation, then let me watch it.
ar_remove_object with object_id: "demo-ball" to clean up.
A focused research corner
Ask:Set a focus environment, place the useful findings in a readable panel, and show a source page only if it can be opened. Keep the spoken summary short.The action sequence is
ar_set_environment → ordinary research tools → ar_show_panel → optional ar_open_browser. The spatial panel presents results; research and factual verification still happen through the Entity’s configured tools.
An embodied explanation
Ask:Step to the left, look toward me, and explain this in three sentences. Put the longer version in a panel.Combine
ar_move_to, ar_look_at, ar_gesture, and ar_show_panel. Let the shell express the movement. The answer does not need to narrate every gesture as stage directions.
Keep the scene useful
- Use stable object and panel IDs.
- Keep content short enough to read at a comfortable distance.
- Remove temporary objects when the demonstration ends.
- Check the surface before requesting capture or generated motion.
- Confirm the rendered result instead of treating a queued action as proof of display.