Spectre

In plain words: App: Spectre (VR meetings)

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

The VR app: it admits a virtual place (VR Habitat) and runs one bounded meeting (Encounter) with participants, consent, events, interruption and exit.

Why read it: Read this before any VR work, to understand what Spectre owns versus Avatar and the VR runtime.
  1. 1Two operations: admit a VR place, and enter a bounded encounter in it.
  2. 2Outcomes are completed, safely exited, interrupted, refused or unresolved.
  3. 3Spectre does not own the world build, headset, raw tracking data or the avatar.

Designed Contract only; first hardware integration is a hypothesis.

Words on this page, decoded click one for its card

In this section 2 pages

Admitting a VR Habitat Spectre: Admitting a VR place How a VR place is checked and recorded: exact world build, runtime capabilities, seated or room-scale space, comfort, accessibility and a visible exit. open → Entering and leaving an Encounter Spectre: Entering and leaving a meeting How one VR meeting is admitted, how runtime events (focus loss, revoked tracking, disconnects) are recorded, how each participant can leave, and how the meeting is settled. open →
The original text Underlined words open their plain-English card.

A compelling apparition still needs a door through which its visitors can leave. Spectre is the Virtual Reality CompositionApp: it admits a virtual place as VRHabitat@1, then keeps one bounded Encounter—participants, purpose, consent, significant events, interruption, and exit—inside it.

The name follows spectre, an appearance or apparition. The experience can matter without becoming Persona identity, physical truth, or authority. An Avatar may present the LichAssistant there; Avatar retains presentation and binding membership while Spectre keeps the place and meeting.

Contract

Use spectre.admit_habitat@1 to admit the place and spectre.enter_encounter@2 for the bounded meeting; both belong to spectre.virtual_reality revision 2. The result is immutable VRHabitat@1 or settled SpectreEncounter@2, with an outcome of completed, safely exited, interrupted, refused, or unresolved.

These results do not take ownership of world authorship, persistent-world effects, headset/runtime, raw tracking archives, or Persona/Avatar. Generic multiplayer, public release, and claims of physical presence also remain outside the contract.

From place to meeting

You want to understand… Continue with…
what makes this place eligible, and this meeting distinct Habitat binding and Encounter admission
how different people can enter, participate, and leave admitted modalities and each participant's departure
what survives a lost runtime runtime state and experienced events
how a greeting can end or recover settling what happened
where the first experiment begins hardware/runtime hypotheses and contract proof

Composition Portfolio · Avatar · Foundry