> For the complete documentation index, see [llms.txt](https://info.mortisian.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://info.mortisian.com/grandvitamortems-greed/grand-tries-to-take-10-of-all-commissions.md).
# Grand tries to take 10% of all commissions
The original text in question from the Vendor Application Form
Below is a string of replies that happened on Twitter when questioned about it.
It is to mention this was a huge dispute within the staff channels of the Syndicate. It boiled down to the members of staff not believing this was an appropriate measure as we believed the Syndicate did not have a right to take 10%. Grand would in-turn go a bit overboard and say he was laying honeypots within the world for people to trap them in exposing their intentions. The staff within called it mind games and demanded Grand not continue to play mind games. Eventually the conversation in staff chat got out of control as Grand doubled down on his belief to lay traps for people. Towards the end of the conversation Grand had rescinded his decision and removed it from the vendor application.
---
# 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://info.mortisian.com/grandvitamortems-greed/grand-tries-to-take-10-of-all-commissions.md?ask=&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.
