Avatar

In plain words: App: Avatar (appearance across places)

Designed 1 min read 1 glossary terms 22 connected pages
The short version written for the Snayu team

An app that keeps the Assistant's chosen appearance (look, voice, motion) consistent and attributable across places like VR and Minecraft, recording what each place reported.

Why read it: Read this before working on how the Assistant is presented visually or by voice in games, VR or devices.
  1. 1A profile defines the allowed presentation; a Morphe selects one form within it.
  2. 2Each place gets its own projection record and reports its own result.
  3. 3Avatar grants no identity change, device ownership or authority to act in a world.

Designed Contract only; no implementation path enabled.

Words on this page, decoded click one for its card

In this section 2 pages

Profile and Morphe Avatar: Profile and form selection How an avatar profile bundles visual, voice, motion, locale and disclosure references for one persona, and how a Morphe picks a style within it without changing who the persona is. open → Presence across places Avatar: Presence across places How Avatar admits a separate projection for each place (VR room, game world), supports mirrored or parallel presence, and handles one place dropping out without inventing its state. open →
The original text Underlined words open their plain-English card.

One LichAssistant can appear in a VR room while a Blockworld inhabitant continues elsewhere. Avatar keeps the presentation attributable across those places: which Persona and eligible form appeared, which projection was admitted, and what each target reported when it ended.

An eligible profile supplies the presentation envelope; a Morphe selects a form inside it. Separate target bindings carry the appearance through interruption and partial settlement. The LichAssistant, its Persona, memory, and each target's effects remain with their owners.

Contract

The work progresses through composing an eligible profile, binding a form, and projecting its presence. avatar.presence revision 2 publishes avatar.compose_profile@2, avatar.bind_morphe@2, and avatar.project_presence@2 for those purposes. Results are immutable AvatarProfile@2, MorpheBinding@2, AvatarPresence@2, and per-target ProjectionBinding@2 records/receipts, or exact partial/non-completion.

Those records grant no identity change, unbounded ambient presence, target-world/device ownership, unobserved delivery/motion claim, or physical/virtual effect authority.

Follow the appearance

You want to understand… Continue with…
what is selected, and what is bound to a target the profile and projection epochs
how a new form remains the same Persona selecting a Morphe
how separate places can share a presentation mirrored and parallel presence
what happens when one place disappears the interrupted greeting
what a projection may claim about a world or body each target's boundary
how this design could first be proved independent settlement and revision continuity

Identity · Composition Portfolio