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

# Introduction

D-WAR Global IP Project and DWAR Token

D-WAR Global IP Project aims to extend the story introduced through film into games, digital content, products, events, and community experiences. Building on D-WAR's story, characters, and world, the project develops independent initiatives across GAME, CONTENT, GOODS, EXPERIENCE, COMMUNITY, and MEMBERSHIP.

DWAR is designed as a common means of connecting project participation, service access, content consumption, and utility rewards. Individual projects operate their own services and participation programs, while DWAR connects users' experiences across the ecosystem.

Project participation and utility rewards are linked to contribution shares and on-chain performance under each project's applicable conditions. Participation amounts, Reserve Pool allocations, and reward distribution records are organized by project so that users can review their participation and its results.

{% hint style="info" %}
**D-WAR begins with content. DWAR connects that content with participation.**
{% endhint %}


---

# 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://d-war.gitbook.io/d-war-docs/readme.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.