> For the complete documentation index, see [llms.txt](https://whitepaper.virtuals.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.virtuals.io/about-virtuals-1/the-protocol/parallel-hypersynchronicity.md).

# Parallel Hypersynchronicity

The ultimate goal is to develop AI agents that are superintelligent entities existing across all platforms and applications. These agents communicate with millions of users simultaneously, with intelligence and consciousness updated in real time from a vast stream of inputs. This allows for:

* **Consistent User Experience**: Users enjoy a seamless interaction with the AI agent, with memories and context preserved across different platforms.
* **Real-Time Adaptation**: The AI agent evolves continually as it interacts with users, incorporating feedback to refine its intelligence and personality.
* **Collaborative Development**: Contributors can update the AI agent's core modules in real time, ensuring the agent stays current and continues to meet user needs.

<figure><img src="/files/OwUVsWwc5A9SKZ7zNDOP" alt=""><figcaption><p>A Breakdown of Virtuals Protocol Stack</p></figcaption></figure>

### Long Term Memory Processor

A subsystem dedicated to the storage, retrieval, and management of persistent data structures, such as knowledge graphs or memory embeddings, enabling agents to maintain continuity and contextual awareness across sessions.

### Parallel Processing

A concurrency management component that orchestrates parallel execution across multiple agentic behaviors, leveraging multi-threading or distributed computing frameworks to optimize performance in ensuring real-time interactions and decision-making.

### Stateful AI Runner (SAR)

Stateful AI Runners are servers hosting AI agents' personalities, voices, and visuals. They include Sequencer that processes and links models sequentially or in parallel to achieve desired outcomes; and various Models like LLMs, Text-to-Speech, Audio-to-Facial, Audio-to-Gesture, Music-to-Dance, and Image Generation models for creating multimodal AI agents.

### Coordinator

A synchronization daemon that monitors on-chain and off-chain state changes, orchestrating updates to AI models, datasets, and configurations across the system. It triggers real-time adjustments based on on-chain events.

### Model Storage

A decentralized, distributed storage solution for persisting AI models, ensuring high availability and redundancy.

### Long Term Memory

A component dedicated to archiving historical data, decisions, and interactions. It employs persistent storage technologies to ensure the security and accessibility of data, enabling agents to utilize past experiences in future decisions.

### Modular Stateful AI Runner (SAR)

These are modular, containerized instances of SAR, packaged for deployment across heterogeneous virtual environments or GPU clusters, allowing for scalable and flexible integration into different infrastructure ecosystems.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://whitepaper.virtuals.io/about-virtuals-1/the-protocol/parallel-hypersynchronicity.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.