> For the complete documentation index, see [llms.txt](https://deadtiles.gitbook.io/deadtiles-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://deadtiles.gitbook.io/deadtiles-docs/the-county/work.md). # Work The opening jobs come from Doctor Clark and Captain Davis. Read a job before you accept it. The Journal tracks what you took and what you still owe. After the tutorial, Davis and Clark post more work on their boards. The Ashen Traders and the Red Order post their own. Pay is in banknotes, and finished work raises your standing with the outfit that gave it. Some jobs send you into a named building in Birchport. Others send you out on the road. The map marks the ones that have a place. Story items stay in your pack until the person who asked for them takes them. They are not for sale. You can work for the Ashen and the Red Order at the same time for now. Later jobs will make you choose. --- # 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://deadtiles.gitbook.io/deadtiles-docs/the-county/work.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.