> For the complete documentation index, see [llms.txt](https://docs.velorarp.dk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.velorarp.dk/documentation/spillerguide/jobs-og-okonomi.md).

# Jobs og økonomi

Kom i gang med arbejde, indkomst og ansvarlig progression.

### Find din vej

Vælg et job, der passer til din karakters historie. Brug samtaler og rollespil til at lære mulighederne at kende.

Spørg en leder eller kollega, når et job har særlige procedurer. Følg altid instruktionerne i den aktuelle scene.

### Økonomi

Tjen og brug penge gennem rolleleg. Hver handel skal have en troværdig IC-begrundelse.

Undgå at overføre værdier mellem egne karakterer eller arrangere kunstige handler. Det svækker den fælles progression.

### Virksomheder og fraktioner

Virksomheder og fraktioner skaber historier for hele serveren. Vis stabilt fremmøde, samarbejd godt og tag ansvar, før du søger større roller.

Kontakt den relevante ledelse, når du vil søge, starte et samarbejde eller foreslå en aktivitet.


---

# 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://docs.velorarp.dk/documentation/spillerguide/jobs-og-okonomi.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.