Presence across places
In plain words: 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.
- 1Each projection binds one target epoch with its own consent, capabilities and result.
- 2Mirrored means one act shown in several places; parallel means separate tasks with the same persona.
- 3Coordinated stop, wait or recovery across places needs an App Bundle (Suite), not Avatar.
Designed Contract only.
Words on this page, decoded click one for its card
The greeting reaches a VR room and a Blockworld inhabitant. Each place must report what happened there. If the headset runtime disappears, a continuing Blockworld mission does not prove the missing VR experience continued too.
Admit each projection
avatar.project_presence@2 begins with an immutable AvatarProfile@2, participant and target references, exact capability snapshots, synchronization policy, consent/privacy, budgets, and stop conditions. An optional MorpheBinding@2 selects an eligible form for the target.
ProjectionBinding@2 admits one target epoch with profile/Morphe, target capability receipt, participants, consent, disclosure, fallback, stops, and attributed terminal result. It records membership in Avatar's presence, without owning the target world, device, InvocationJob Request, provider session, or effects. Changed form, capability set, target epoch, participants, consent, or disclosure closes or replaces the affected binding according to its declared policy.
AvatarPresence@2 brings these Avatar-owned bindings together for one purpose. It identifies required/optional members, presentation-synchronization intent, local ceilings, and the policy for evaluating attributed target results. This gives Avatar an account of the presentation. A Suite must own any promised live coordination: Avatar itself cannot initiate, admit, await, cancel, retry, recover, or correlate the lifecycle of target-owned InvocationsJob Requests.
One Lich, many projections
Two closed modes keep shared presentation distinct from shared execution:
- mirrored declares one attributed semantic act for presentation in separately admitted targets; each target performs its own work and returns its own delivery/effect receipt;
- parallel permits distinct bounded target InvocationsJob Requests with the same Persona revision but separate ContextBriefing Pack, authority, chronology, observations, and outcomes.
Neither proves a universal session or indivisible field of attention. A projection can join, downgrade, refuse, disconnect, or finish without inventing another's state. Avatar judges only results made available to its bindings:
| Result | Meaning |
|---|---|
| completed | Every required binding returned an eligible attributed terminal result. |
| partial | Policy permits the exact settled subset and names absent, refused, interrupted, or still-running members. |
| refused | Presence or a required binding failed admission before beginning. |
| unresolved | A required outcome is unknown or cannot be reconciled without guessing. |
Follow the interrupted greeting
Compose the exact profile and target-scoped Morphe. Spectre and Blockworld independently admit a VR Habitat and mission; Avatar declares required projections and mirrored/parallel policy, then creates separate binding epochs.
A participant meets the LichAssistant in a Spectre Encounter. The greeting may also appear in Blockworld, but its separate receipt proves only the world-local result. When XR is lost, Spectre records interruption or offers explicit recovery. Avatar settles the VR binding only from Spectre's attributed result. Blockworld keeps its own mission and authority.
If Spectre re-admits recovery, Avatar can close or link the old VR epoch and open a fresh binding under recovered facts. Otherwise it remains interrupted. Avatar does not wait for or stop the world mission; it evaluates available results. A ProductPackaged Offer promising coordinated stop, wait, or recovery must pin aan SuiteApp Bundle.
Target truth stays local
Each target keeps the authority needed to judge what happened there:
| Target owner | Retained truth and authority |
|---|---|
| Reach | Social events, audience, platform delivery, and replies. |
| Blockworld | World epoch, inhabitant, mission, inventory, lease, and effects. |
| Spectre | Habitat, Encounter, comfort, interruption, and exit. |
| Homestead, for a room display | Place policy, bystanders, indicators, purpose, and controls. |
| Vehicle controller | Occupants, safety, motion, and local override. |
| Familiar | Body, capabilities, geofence, emergency stop, mission, observations, and effects. |
| Companion | Mobile session, privacy, disclosure, configuration, reconnect, and separate stop-speaking/cancel-session controls over an admitted Familiar phone body. |
For VR, Avatar binds to an exact VRHabitat@1 and may select eligible head, hands, body, voice, motion, captions, disclosure, and fallback. The target retains authority over the XR session/reference space, locomotion, haptics, tracking capture, entry, and exit.
Tracking tells Avatar which presentations are eligible. Head/hand/gaze/face/body signals prove no identity, intent, attention, emotion, consent, co-location, or remembered experience. Keep raw high-rate inputs with the engine/runtime; Avatar retains only minimum capability facts and semantic results.
Proving independent settlement
A network-disabled synthetic profile appears in mock text/voice, Blockworld, Spectre, and Familiar adapters. Prove mirrored/parallel modes, one-target refusal, downgrade, Morphe change, disconnect/restart, consent revocation, partial settlement, export, and deletion. Public platforms, real performer clones, headsets, drones, vehicles, and robots are outside the fixture.
A later Avatar Studio ProductPackaged Offer may package customization/preview. Packaging and SuitesApp Bundles do not move target authority into Avatar. Return to Avatar.