> 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/virtuals-protocol-whitepaper-ko/info-hub/virtuals-protocol-1/select-research-work.md).

# 연구 작업 선택

비디오 게임 생성, 자율 가상 세계, 오디오 기반 애니메이션 분야의 AI 프로젝트를 탐색하며 상호작용형 디지털 경험의 미래를 형성해 보세요.

**MarioVGG** - 인터랙티브 비디오 게임 제작을 위한 비디오 생성 모델에 대한 연구.

{% embed url="<https://virtual-protocol.github.io/mario-videogamegen/>" %}

**프로젝트 웨스트월드**: 로블록스에서 처음으로 플레이 가능한 자율 세계

{% embed url="<https://virtual-protocol.github.io/westworld-ai/>" %}

**오디오-투-애니메이션(A2A)**, 또한 오디오 기반 애니메이션이라고도 불림

{% @github-files/github-code-block url="<https://github.com/Virtual-Protocol/tao-vpsubnet/>" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://whitepaper.virtuals.io/virtuals-protocol-whitepaper-ko/info-hub/virtuals-protocol-1/select-research-work.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
