Give AI a visible
place to arrive.
Create digital-human and agent experiences that can guide, teach, support and host—with clear state, bounded tools and human fallback.
The opportunity
Move AI beyond the chat window.
Many valuable AI experiences are social and spatial. A guest looks for guidance. A learner needs an explanation. A customer wants to compare a physical product. A team wants an agent to participate around shared work.
A Reality Relay Space gives that intelligence a consistent physical position, expressive form and shared point of attention. The Platform connects the visible presence to approved knowledge, tools, states and operator controls.
Design principles
Make the intelligence legible.
- 01
Define the role
Specify what the agent can do, what it must not do and when it should hand off to a person.
- 02
Show its state
Listening, thinking, speaking, waiting and recovery must be visible to the audience and operator.
- 03
Ground the body
Scale, eye line, feet or support point, contact shadow and voice direction should belong to the same physical scene.
- 04
Keep human control
Use bounded tools, clear escalation and an operator path for uncertain or sensitive moments.
High-value roles
Start with a job people can understand.
Guide
Welcome visitors, orient them to a place and connect them with the right resource or person.
Explain
Teach a model, procedure, product or cultural object through voice, gesture and shared visuals.
Support
Handle a bounded service flow and escalate to a remote human when judgment or authority is needed.
Pilot scorecard
Prove understanding and trust.
Task success
Did people complete the intended task with fewer errors or less assistance?
Legibility
Could users understand the agent’s role, state and limits throughout the interaction?
Control
Could an operator observe, pause, recover and escalate the experience reliably?
Operator runbook
Build the intelligence and the service together.
- 01
Write the role contract
Define the audience, job, approved knowledge, callable tools, prohibited actions, escalation triggers and session data. If the role cannot be explained in one sentence, it is not ready for a public room.
- 02
Make identity explicit
State whether the presence is AI-generated, recorded, remotely operated or hybrid. The form, voice and behavior should never encourage users to assume a human authority that is not there.
- 03
Show the system working
Listening, processing, speaking, waiting, tool use and failure must be visible. The operator needs a separate view of session state and the ability to interrupt, recover or transfer the interaction.
- 04
Review the hard moments
Study refusals, uncertainty, repeated questions, unsafe requests and human handoffs—not only successful demonstrations. Update the role and knowledge boundary before adding more capabilities.
Decision gates
Do not confuse embodiment with authority.
The body has a job
If voice or text completes the task equally well, keep the simpler interface. Give AI a physical presence only when gaze, gesture, scale, shared attention or place improves the experience.
The limits are legible
Participants should know what the agent can access, what it cannot decide and how to reach a person. A convincing character must not hide an uncertain system.
Human recovery is real
Do not launch with a decorative handoff button. Test the complete transfer, context passage, response time and return path with the people responsible for support.
Evidence status. This is a product-design field brief, not a claim of deployed autonomous capability or a proven customer outcome. Replace the hypothesis with measured pilot evidence before presenting it as proof.