> For the complete documentation index, see [llms.txt](https://gitbook.logos.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.logos.co/logos-operators/backstory.md).
# Backstory
Crypto is under siege. We need your help to save it.
We thought crypto was our EXIT, our cyber-sanctuary detached from a world built on our subservience. It promised to level the playing field, democratise opportunity, and empower the average Joe with tools to control their destiny.
But their game thrives on our subjugation. It demands our silence, compliance, and entrapment. You are forced to play, but never win. The dice are loaded; the cards are stacked. You cannot win.
But we, the Logos Collective, are not afraid; we carry the torch Satoshi rekindled and passed on. We draw on centuries of technological, artistic, and revolutionary movements, from the Enlightenment thinkers of old to those visionaries seeking refuge in cyberspace. We stand for all those downtrodden and trapped in a game that only its rulemakers can thrive in.
We're building a portal to a parallel society – an exit into a new form of social coordination. The frontier Satoshi pioneered lies uncharted, ready for us to explore. The opportunities for its earliest settlers will be profound, and a freedom that today may seem unimaginable awaits.
---
# 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://gitbook.logos.co/logos-operators/backstory.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.
