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

# General

## I found a bug. <a href="#bkmrk-page-title" id="bkmrk-page-title"></a>

Awesome!

Please report the bug here as a ticket.  We would like to reward folks who identify these issues and this will allow us to keep track of them, not to mention document the bug itself for repairing.

## We have a business opportunity, who do we contact? <a href="#bkmrk-page-title" id="bkmrk-page-title"></a>

Please reach out to us on our discord.

## Where is the roadmap? <a href="#bkmrk-page-title" id="bkmrk-page-title"></a>

There is not a roadmap.  Not for this project, and for none of our others either.  Roadmaps are useful, we don't disagree, but they're also setting a precedent for expectations, especially when a token is involved.  We don't want to discourage anybody asking "what's next?" by any means, so if you are curious, by all means ask!  We're happy to let you know what we're working on, it's progress and more.


---

# 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://praxxas.gitbook.io/killswitch/f.a.q/general.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.