> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fesutibaru.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Concepts

> How a festival's data fits together in Planner.

## The festival and its editions

Each festival has its own address (`demo.fesutibaru.com`) and its own data; nothing crosses between festivals. A festival runs **editions**, one per year. One edition is **current**: reads default to it, and `?edition=2026` reads another (`GET /editions` lists them).

## What belongs where

| Belongs to the festival | Belongs to one edition |
| - | - |
| People, books, venues, accommodation, equipment | Events, travel, stays, pick-ups, documents, media |

People and books belong to the festival and **take part** in editions: `GET /people` lists the people in the edition you ask for.

## Records and how they link

* An **event** has a venue, and people in roles: authors and speakers, chairs, interviewers, intro / wrap, and staff. Add them with `?include=authors,chairs,venue`.
* A **person** has a `role_type`: `participant` covers authors, chairs and other speakers; there are also publicists, staff roles (operations, front of house, technicians…) and more. `GET /role-labels` gives each festival's own names for them.
* A **book** (`/books`) has authors and publicists.
* **Travel** is a person's journey; a **stay** is a person at an accommodation for some nights; a **pick-up** is a driver's run, which journeys join with `pickup_id`.

## Fields

Field names are Planner's own (`start_time`, `venue_id`), the same when you read and when you propose. A festival's **custom fields** appear as `cf_<field_key>` (`GET /custom-fields` lists them).

**Times** are instants with an offset (`2027-08-21T17:00:00+00:00`). Beside each is the festival's own wall-clock time, `start_time_local` (`2027-08-21T18:00`): use that when talking to people about when something happens.

## What you can see

You see what the person you act for can see in Planner, nothing more. Fields their role can't see are left out of every record. Records in the Recycle Bin are never served.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.