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

# Shards

Anything on this page is subject to change throughout the development progress of the game. We will thoroughly test and validate any feature before it goes live.

Social-Fi is a blend of both Social and Decentralized Finance. It isn't just a concept; it's a game-changer for players, guild founders, managers, and speculators. This platform isn't a one-way street—it's where individuals with shared interests can reap the rewards. And that's not all; it opens up the opportunity for individuals to financially speculate on the entities thriving within this dynamic space.

Now, in the realm of multiplayer games like SHODO VEIL, Shards isn't just nice to have; it's the backbone of competition. It enables players to come together, form communities, and collaborate on objectives and goals within their organization.

SHODO VEIL bridges the gap between Social-Fi and Gaming by empowering guilds, players, and speculators to operate in a singular environment ultimately creating a self-motivating and sustaining flywheel. This is a world-first innovation developed by SHODO VEIL.


---

# 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://shodo-veil.gitbook.io/whitepaper/shards.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.
