Clear answers. Precise boundaries.

AESORYX is the product ecosystem of Gatai Inc. (g-atai.com), encompassing MediVerse, a persistent medical-world application. The platform is currently in development, with an orthopedic prototype as its initial focus.

MediVerse is the application through which users enter the simulated medical world. Its intended architecture connects patients, intelligent people, facilities, functional devices and clinical workflows.

It is the operational model of the medical world: people, patient locations, resources, permissions, orders and events. It determines what is happening and which actions may change state.

It is a computational representation of a simulated patient’s connected physiological and clinical state. The current prototype uses synthetic orthopedic proxies; multi-system and clinically validated models are future work.

An agent receives role-appropriate context and can explain or propose an action. Authoritative simulation logic validates important actions before they alter patient state. Conversation alone does not commit a clinical intervention.

Mixed human and AI teamwork is part of the design. A synchronized multiplayer experience is planned; the current prototype provides shared-backend foundations rather than a completed multi-user product.

Orthopedics is the initial prototype focus. This site describes the planned scope of 26 Specialty Complexes. A specialty page is a design scope, not a claim that the entire complex is operational.

The prototype includes an installed bHaptics integration and an XR interaction foundation. Physical device output, advanced gloves and force-feedback procedures require integration and validation. Vibration is not force feedback.

Functional medical devices are part of the roadmap. The intended device layer connects controls, alarms and readings to modeled patient state. Existing equipment visuals do not establish device behavior or clinical fidelity.

The design combines identity, history, conditions, risk factors, physiology and communication context. Broad generative patient authoring is planned and should preserve internal clinical consistency.

Persistent case state is present in the development backend. A continuously evolving institution, cross-session social continuity and the complete longitudinal care journey are being developed.

Educator authoring is planned for patients, conditions, objectives, teams, complications and rubrics. It is intended to reduce reliance on Unreal source changes, but a production authoring interface is not yet available.

Local inference is used in the current prototype. Private cloud and on-premises delivery are deployment directions to assess with institutions; a production deployment package has not been established.

No clinical validation, regulatory approval or clinical decision-support status is claimed. The current work is a simulation prototype. Clinical judgment, patient care and regulated device use require separate governance and evidence.