> For the complete documentation index, see [llms.txt](https://docs.eventication.com/event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventication.com/event/artists/line-up.md).

# Line-up

The line-up is every performance of this edition: which artist plays which [stage](https://docs.eventication.com/event/artists/stages.md) on which [day](https://docs.eventication.com/event/planning/days.md).

**Status**: a performance is *wishlist* (you would like them), *planned*, *confirmed* or *cancelled*. Wishlist acts have their own tab until they are booked.

**Performance groups**: two or more acts playing together show a *B2B* badge and are managed as one group.

**Custom name**: a performance can carry its own name next to the artist's ("Sunset set").

**Moving stages**: a performance can be moved to another stage from its row menu.

The table view filters on artist, day, status and offer status; the grid view shows the line-up as a timetable. A cancelled performance keeps all of its data and stays reachable behind the status filter. Cancelling is a planning fact, not a deletion.

{% hint style="info" %}
Each performance has its own [advancing](https://docs.eventication.com/event/artists/advancing.md) dossier; the line-up is where it is opened from.
{% endhint %}


---

# 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://docs.eventication.com/event/artists/line-up.md?ask=<question>&goal=<user_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.
