Role & boundaries
Audience, language, tone, allowed actions and escalation routes written as product decisions.
For teams exploring an agent-backed character experience alongside a physical product, campaign or customer journey. The goal is a governed product system—not an unbounded demo.
We organise the character layer around a defined role, approved content and an accountable operating path. The model is one component; the more durable work is deciding what the character should know, say, never say and how its source material is handled.
Audience, language, tone, allowed actions and escalation routes written as product decisions.
Rights, consent, style guide and operating limits defined before voice material is used.
Source selection, update owner, access rules and offboarding plan for each knowledge base.
Model, cloud, data residency and support choices evaluated against the actual markets and data flow.
Permissions, persona guide, age context, source materials and the commercial job the character must do.
Isolated knowledge, selected model path, content rules, logging approach and handoff procedure.
Physical interface, regional cloud choice, privacy notice, customer support and a responsible owner after launch.

There is no generic requirement to use a Chinese model or a local model in every market. The appropriate architecture follows the project’s data, users, channels, contracts and target geography.