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

# Onym seats

Onym splits the powers a normal service concentrates — naming the user, presenting the interface, carrying the data, validating shared state, judging conduct — into independently ownable **seats**. One rule governs all of them:

> A component may exercise the minimum authority required for its role, and it may earn only when a user or group chooses it for that role.

Every seat is specified twice in [`onym-system`](https://github.com/onymchat/onym-system): an abstract contract (`X.md`) that is technology-free, and one or more implementation profiles (`X-<Technology>.md`) that map it onto a concrete stack.

This book documents the seats that have **running reference code** today. It is not the specification — it is the map from a contract to the repo, the wire surface, and the command that starts it.

## Implemented

| Seat                               | Reference implementation                                                                                                                                   | Live at                                     |
| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------- |
| [Moderation](/seats/moderation.md) | [`onym-moderation`](https://github.com/onymchat/onym-moderation) — `authority/` + `apple/`                                                                 | `authority.onym.app`, `moderation.onym.app` |
| [Notary](/seats/notary.md)         | [`onym-contracts`](https://github.com/onymchat/onym-contracts) (5 Soroban contracts) + [`onym-relayer`](https://github.com/onymchat/onym-relayer)          | Stellar testnet, `relayer.onym.app`         |
| [Courier](/seats/courier.md)       | strfry (Nostr) + blossom-server, wired in [`onym-infra`](https://github.com/onymchat/onym-infra)                                                           | `nostr.onym.app`, `blossom.onym.app`        |
| [Identity](/seats/identity.md)     | [`onym-sdk-swift`](https://github.com/onymchat/onym-sdk-swift) / [`onym-sdk-kotlin`](https://github.com/onymchat/onym-sdk-kotlin), consumed by the clients | on device                                   |
| [Discovery](/seats/discovery.md)   | GitHub release assets across four repos                                                                                                                    | `releases/latest/download/*`                |

[Deployment](/operating/deployment.md) brings the server-side seats up on one box.

## Not implemented

Contract only, no code in any Onym repository: **recovery trustee**, **backup**, **charity**, **audit**, **arbitration**, **lead generation**, **acquisition**, **sponsor**, **recruitment**. The **interface** seat has client scaffolds ([`onym-ios`](https://github.com/onymchat/onym-ios), [`onym-android`](https://github.com/onymchat/onym-android)) but does not yet meet its contract. The **bank** and **association naming** seats are open pull requests against `onym-system`.

Nothing here is production-grade: alpha, unaudited, and several load-bearing pieces are open work.


---

# 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.onym.foundation/onym-seats.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.