> For the complete documentation index, see [llms.txt](https://plan-a-labs.gitbook.io/metawara/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://plan-a-labs.gitbook.io/metawara/plan-a-labs.md).

# Plan A Labs

### Plan A Labs Overview

Plan A Labs Inc is a legally registered corporation in Panama (Registration No. 155767422), officially established on May 20, 2025. As a fully authorized entity, Plan A Labs Inc functions as the corporate foundation and operating studio behind the Meta WAR project. With a leadership team composed of experienced Web3 professionals, the studio aims to push the boundaries of metaverse-based content and interactive blockchain entertainment.

#### Project Direction (PD)

* **Paul Kim** – PD, Web3.0 Content Planning & System Design

Paul Kim is a seasoned expert with over 20 years of experience in the game business and system design. He leads the creative and strategic direction of Meta WAR, focusing on the planning, development, and architecture of Web3 content. With deep expertise in blockchain-based platform design and immersive user experiences, he plays a central role in shaping the project's narrative framework and interactive economy.


---

# 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://plan-a-labs.gitbook.io/metawara/plan-a-labs.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.