> For the complete documentation index, see [llms.txt](https://seat-airlines.gitbook.io/seat-airlines-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://seat-airlines.gitbook.io/seat-airlines-docs/section-network/how-far-you-can-see.md).

# Your seat is which room you are in

Each cabin is its own room. You see and reach the people in your section, and nobody else.

The **Section network** is a directory for holders: each can publish a card, introduce themselves, and talk in their cabin's room. What your seat decides is **which cabin you belong to** — and the rule is one line, applied everywhere:

{% hint style="success" %}
**Each cabin sees only itself.** Your seat opens your own section: its cards, its people's inboxes and its room. Every other section — in front of you or behind you — keeps its contact details and its conversations to itself.
{% endhint %}

## Who can read what

|                                                           | Who can read it                                                                    |
| --------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| **A holder's name and role**                              | Every holder signed in to the directory. The roster belongs to the whole aircraft. |
| **A holder's contact details** — email, website, LinkedIn | Their own section, and nobody else.                                                |
| **A conversation between two holders**                    | The two wallets on it, and nobody else.                                            |
| **A cabin's room**                                        | That cabin, and nobody else.                                                       |
| **The PA**                                                | Everyone aboard, the cargo hold included.                                          |

## Writing goes exactly as far as reading

If you can read somebody's card, you can introduce yourself to them — so you can write to anybody in your own section, and to nobody outside it. The **cargo hold** is not a cabin: a wallet without a seat is on no roster, its card is not shown, and it has no room to talk in.

{% hint style="info" %}
These rules are enforced by the server, not just by the page. A card from another cabin arrives without its contact details, and a message to another cabin is refused: *"That holder is in another cabin. Introductions stay within your own."*
{% endhint %}

Next: [Cards and sign-in](/seat-airlines-docs/section-network/cards-and-sign-in.md) · [Introductions, rooms and the PA](/seat-airlines-docs/section-network/introductions-rooms-and-the-pa.md)


---

# 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://seat-airlines.gitbook.io/seat-airlines-docs/section-network/how-far-you-can-see.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.